Accessibility Statement

Hayashi Technology Solutions is committed to making this website usable by the widest possible audience, regardless of ability or technology. Here is what we do, how to report a barrier, and how we plan to keep improving.

Effective date: June 23, 2026  ·  Last updated: June 23, 2026

1. Our Commitment

We design and build this website with accessibility in mind so that visitors with vision, hearing, mobility, or cognitive differences can find the information they need and contact us without barriers. Accessibility is treated as part of the build, not as something we layer on afterward.

2. Standard We Target

This website aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.1 AA is the standard most commonly referenced by United States federal and state accessibility guidance and is widely accepted as a practical baseline.

This statement reflects our current good-faith status. We have not yet completed a formal third-party WCAG audit; conformance claims should be read as “aiming for” rather than “certified at” Level AA until that audit is complete.

3. What We Do Today

Specific accessibility features built into this site:

  • Skip-to-content link at the top of every page so keyboard and screen-reader users can bypass the navigation
  • Semantic landmarks (<header>, <nav>, <main>, <footer>) so assistive technology can navigate page regions
  • Single H1 per page and a logical heading hierarchy (H2 → H3) to support screen-reader outlines
  • Descriptive alt text on photographic and informational images; decorative images are marked as such
  • Visible focus indicators on links, buttons, and form fields for keyboard navigation
  • Labeled form fields with explicit <label> elements, required-field markers, and inline error messages associated with the field that failed
  • Reduced-motion respect: when a visitor sets prefers-reduced-motion in their operating system, our scroll-driven animations and image transitions are disabled
  • Color and contrast chosen to meet WCAG AA contrast ratios for body text against background
  • Responsive layout that adapts cleanly to mobile, tablet, and desktop viewports and supports browser zoom up to 200% without horizontal scrolling
  • Accordions and disclosures implemented with the native HTML <details>/<summary> element, which is keyboard-accessible and screen-reader-aware by default
  • External links indicated and opened with rel="noopener" for security

4. Known Limitations

We are honest about what is not yet perfect:

  • A formal third-party WCAG 2.1 AA audit has not yet been performed. Automated accessibility scanners do not catch every issue, and we want a human pass before claiming certified conformance.
  • Downloadable documents (PDF service overview, etc.) may not yet meet all accessibility tagging requirements. Please contact us for an accessible alternative if you need one.
  • Third-party embedded content (such as Google Fonts, the website firewall’s challenge pages, or future video embeds) is not under our direct control and may have its own accessibility characteristics.

5. Assistive Technology Compatibility

This site is built with semantic HTML and standard browser features and is intended to work with current versions of major screen readers (NVDA, JAWS, VoiceOver, TalkBack), voice-control software, and keyboard-only navigation. It is designed and tested against current versions of Chrome, Edge, Firefox, and Safari on desktop and mobile.

6. Reporting an Accessibility Barrier

If you encounter a page, feature, or document on this site that is difficult or impossible to use because of a disability, we want to hear about it. Please contact us with as much detail as you are comfortable sharing—the page URL, what you were trying to do, the assistive technology and browser you were using, and what happened—so we can reproduce and fix the issue.

Email: info@hts-i.com  ·  Phone: (916) 672-8299  ·  Mail: 2821 Isle St, Rocklin, CA 95765

We aim to acknowledge accessibility reports within five business days and to provide an alternative way to access the requested content while a fix is in progress.

7. How We Plan to Improve

  • Commission a formal third-party WCAG 2.1 AA audit and remediate findings
  • Add accessibility tagging to downloadable PDFs as part of any future revision
  • Include accessibility checks in our routine content-update workflow so new pages start accessible rather than needing remediation later

8. Changes to This Statement

We will update this Accessibility Statement as our practices and the site evolve. The “Last updated” date at the top of this page reflects the most recent revision.