Last updated August 2, 2026. This statement covers forefrontindustries.io and describes the standard we hold our own site and our client builds to.
Forefront Industries is committed to making this website usable by as many people as possible, including people who browse with a screen reader, navigate by keyboard only, use voice control, rely on high contrast or magnification, or have limited motor control.
Accessibility is not a compliance checkbox for us. It is part of how a site is engineered. A page that a screen reader cannot parse is usually also a page that a search engine cannot parse well and that converts worse for everyone.
We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. In practice that means:
Accessibility checks happen during development, not as a pass at the end. Our process includes automated auditing with Lighthouse and axe, manual keyboard-only walkthroughs of every template, contrast verification against the design system tokens, and screen reader spot checks using VoiceOver on macOS and iOS.
Automated tools catch roughly a third of real issues. The manual pass is where the rest are found, which is why we do not rely on an overlay widget or a plugin. Accessibility overlays frequently make the experience worse for the assistive technology users they claim to help, and we do not install them on client sites.
We are transparent about the areas where this site does not yet fully meet our own bar:
If you find something not listed here, we want to know. Reports get fixed, they do not get filed.
This site is designed to work with current versions of Chrome, Edge, Firefox, and Safari on desktop and mobile, paired with current versions of VoiceOver, NVDA, JAWS, and TalkBack. It may not perform correctly on browsers older than three years, which no longer receive security updates.
JavaScript is required for full interactivity, but every page is server rendered so the core content and navigation are present in the initial HTML.
If any part of this site prevents you from doing what you came to do, contact us and describe what happened, the page you were on, and the browser or assistive technology you were using. We aim to acknowledge every report within two business days and to resolve confirmed issues in the next release cycle.
If you need information from this site in an alternative format, ask and we will provide it.
Every custom build we ship is delivered against the same WCAG 2.1 AA target described above, and accessibility criteria are written into the project acceptance criteria rather than treated as an optional add-on. Where a client operates under a stricter obligation, such as Section 508 or a specific state procurement standard, we scope and test to that standard instead.
We do not offer legal advice or certify legal compliance. We engineer to the published technical standard and document what was tested.
Tell us the standard you are held to and we will scope the build against it from day one.
We use cookies to analyze traffic and improve your experience. Tracking stays off until you accept. Cookie Policy.