LEGAL
Accessibility Statement
Our commitment, where this website currently stands, and how to tell us if something does not work for you.
Effective 28 July 2026 · Last updated 28 July 2026
1. Our commitment
Forge AI Deployment is committed to making this website usable by as many people as possible, regardless of ability or the technology they browse with. We treat accessibility as part of building the site properly, not as a remediation exercise afterwards.
2. Standard we apply
We work to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. WCAG is the standard referenced in practice by the Americans with Disabilities Act, by Section 508 of the Rehabilitation Act for United States federal procurement, and by EN 301 549 in the European Union.
3. Conformance status
Partially conformant. We use that term in its WCAG sense: most of the standard is met, and some parts have not yet been verified to the depth required to claim full conformance.
We publish a detailed, criterion-by-criterion report rather than asking you to take a summary on trust:
Read the Accessibility Conformance Report (VPAT® 2.5)
4. What we have done
Each of the following was verified on this site, not assumed:
- Colour contrast. Every text and background pair in the stylesheet was measured against WCAG 2.2 AA thresholds. All pass; the lowest ratio in use is 4.58:1 against a 4.5:1 requirement. Two colours that fell short at 3.35:1 were corrected before launch.
- Keyboard access. Every interactive element is reachable and operable by keyboard, with a visible focus indicator. A skip link is the first focusable element on every page.
- Semantic structure. Every page has exactly one
h1, no skipped heading levels, and correct banner, navigation, main, and contentinfo landmarks. - Forms. Every control has a programmatically associated label. Required fields are marked. Errors are announced through a live region rather than by colour alone. Inputs use a 16px minimum, which prevents involuntary zoom on iOS.
- Content without scripting. Every page renders completely with JavaScript disabled, and the consultation form still submits.
- Motion. Reveal animations and the parallax effect are disabled for visitors who set a reduced-motion preference.
- Reflow. Pages were checked from 1920px down to 320px with no horizontal scrolling. The one wide element, a comparison table, scrolls within its own labelled, focusable region.
- Images. The decorative hero image carries an empty
altattribute so screen readers skip it. This site uses no images that convey information. - Third-party content. There is none. Every resource is served from our own domain, so no external widget can introduce a barrier we do not control.
5. Known limitations
Being specific about gaps is more useful than a general assurance.
- No testing with assistive technology. Our verification was structural, programmatic, and manual by keyboard. This site has not yet been tested with VoiceOver, NVDA, or JAWS, or by a screen reader user. Automated and structural checking reliably catches only a portion of real barriers.
- No independent audit. No third-party accessibility evaluation has been carried out.
- Comparison table on the Why Forge page. Below 960px it scrolls horizontally within its container. It is a focusable, labelled region and reachable by keyboard, but a wide table remains harder to navigate on a small screen than a linear layout.
- Display typography. Large headings use tight letter-spacing as part of the visual design. This is within our control and we keep it under review.
We are working to close the first two. This statement will be updated when we do.
6. How we assessed this site
Self-evaluation carried out by the development team in July 2026, combining:
- Programmatic contrast measurement across every colour pair defined in the stylesheet
- Automated structural checks of heading order, landmarks, labels, and alternative text across all pages
- Manual keyboard navigation of every page and interactive control
- Layout inspection at 1920, 1440, 1080, 834, 720, and 390 pixel widths
- Rendering verification with JavaScript disabled
These checks run automatically on every change through our continuous integration pipeline, so a regression fails the build rather than reaching this site.
7. Section 508 and procurement
United States federal buyers commonly request an Accessibility Conformance Report as part of procurement. Ours is published in full at /accessibility-report, using the ITI Voluntary Product Accessibility Template (VPAT®) 2.5 Revised Section 508 Edition.
If you need the report in a different format, or need it to cover a system we would deploy in your environment rather than this website, contact us and we will provide it.
8. Reporting a barrier
If any part of this site prevents you from doing what you came to do, please tell us. A short description of what you were trying to do, which page, and what technology you were using is enough — you do not need to identify the technical cause.
Email: development@forgeprivate.ai
We aim to acknowledge accessibility reports within two business days and to respond substantively within ten business days. If a fix will take longer, we will tell you what we are doing and when to expect it.
If you need information from this site in an alternative format, ask and we will provide it.