ACCESSIBILITY CONFORMANCE REPORT
Accessibility Conformance Report (VPAT® 2.5)
Revised Section 508 Edition. Criterion-by-criterion conformance for the Forge AI Deployment website.
Report date: July 2026
1. Report information
| Organization | Forge AI Deployment |
|---|---|
| Product name | Forge AI Deployment website (forgeprivate.ai) |
| Product version | 1.0 |
| Report date | July 2026 |
| Product description | A public marketing and informational website describing Forge AI Deployment’s sovereign AI deployment services. Ten static pages plus one contact form. No authentication, no transactions, no audio or video content. |
| Contact | info@forgeprivate.ai |
| Report author | Forge AI Deployment development team (self-evaluation) |
| Evaluation methods |
Combined manual and automated testing performed in July 2026 against the production build:
Limitation of this evaluation: testing did not include screen readers or other assistive technology (VoiceOver, NVDA, JAWS), speech input, or screen magnification, and no independent third-party audit was performed. Conformance claims below therefore rest on structural, programmatic, and keyboard evidence. Criteria whose verification depends materially on assistive-technology behaviour are identified in the Remarks. |
| Notes | This report covers the public website only. It does not cover AI systems that Forge AI Deployment deploys inside a customer environment; a separate report can be provided for a specific deployment on request. |
2. Applicable standards
| Standard | Included in report |
|---|---|
| Web Content Accessibility Guidelines 2.2, Level A | Yes |
| Web Content Accessibility Guidelines 2.2, Level AA | Yes |
| Web Content Accessibility Guidelines 2.2, Level AAA | No — not required for Section 508 procurement |
| Revised Section 508 standards (36 CFR Part 1194, Appendix A, C and D) | Yes |
| EN 301 549 (European accessibility requirements) | Not separately assessed; the WCAG 2.2 A/AA tables address the majority of its web requirements |
Note: WCAG success criterion 4.1.1 Parsing was removed in WCAG 2.2 and is therefore not reported.
3. Conformance terms
| Term | Definition |
|---|---|
| Supports | The functionality of the product has at least one method that meets the criterion without known defects, or meets it with equivalent facilitation. |
| Partially Supports | Some functionality of the product does not meet the criterion. |
| Does Not Support | The majority of product functionality does not meet the criterion. |
| Not Applicable | The criterion is not relevant to the product. |
4. WCAG 2.2 Level A
| Criterion | Level | Conformance | Remarks and explanations |
|---|---|---|---|
| 1.1.1 Non-text Content | A | Supports | The single hero image is decorative and carries an empty alt attribute. All inline SVG icons are marked aria-hidden="true" and sit alongside visible text. The site uses no images that convey information, and no CAPTCHA. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Not Applicable | The product contains no audio or video content. |
| 1.2.2 Captions (Prerecorded) | A | Not Applicable | The product contains no synchronised media. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | The product contains no synchronised media. |
| 1.3.1 Info and Relationships | A | Supports | Structure is conveyed in markup: sectioning elements with banner, navigation, main and contentinfo landmarks; ordered and unordered lists for list content; data tables using thead, th and scope; and form controls with associated label elements. |
| 1.3.2 Meaningful Sequence | A | Supports | Reading order follows DOM order on every page. No CSS positioning reorders content in a way that changes meaning; grid and flex layouts preserve source order. |
| 1.3.3 Sensory Characteristics | A | Supports | No instruction depends solely on shape, size, visual location, or sound. The one directional hint (table scrolling) supplements a control that is also keyboard-reachable and labelled. |
| 1.4.1 Use of Color | A | Supports | Colour is not the sole means of conveying information. Form validation results are conveyed as text in a live region. The current navigation item is indicated by both colour and a persistent underline, and by aria-current="page". Links within body prose are underlined. |
| 1.4.2 Audio Control | A | Not Applicable | The product plays no audio. |
| 2.1.1 Keyboard | A | Supports | All functionality is operable by keyboard, including the mobile navigation drawer and form submission. Verified by manual keyboard traversal of every page. |
| 2.1.2 No Keyboard Trap | A | Supports | No component traps focus. The navigation drawer can be exited by continued tabbing and closes on Escape. The product contains no modal dialogs. |
| 2.1.4 Character Key Shortcuts | A | Not Applicable | The product implements no single-character key shortcuts. |
| 2.2.1 Timing Adjustable | A | Not Applicable | The product imposes no time limits on any activity. |
| 2.2.2 Pause, Stop, Hide | A | Supports | The only motion is a one-time reveal transition as sections enter the viewport, and a pointer-following highlight in the hero. Neither auto-updates, blinks, nor persists beyond five seconds, and both are disabled entirely when the user sets a reduced-motion preference. |
| 2.3.1 Three Flashes or Below Threshold | A | Supports | No content flashes. All transitions are single, gradual opacity and transform changes. |
| 2.4.1 Bypass Blocks | A | Supports | A “Skip to main content” link is the first focusable element on every page and becomes visible on focus. It targets an anchor placed immediately after the primary navigation, so activating it moves focus past the repeated navigation rather than to the start of the page. Landmark regions provide a second bypass mechanism. |
| 2.4.2 Page Titled | A | Supports | Every page has a unique, descriptive title identifying both the page topic and the organization. Verified programmatically across all ten pages. |
| 2.4.3 Focus Order | A | Supports | Focus order follows DOM order, which matches the visual order. The only element with a modified tab index is the honeypot spam-trap field, which is removed from the tab order with tabindex="-1" and hidden from assistive technology. |
| 2.4.4 Link Purpose (In Context) | A | Supports | Link text describes its destination. There are no “click here” or bare-URL links. Icon-only controls carry aria-label. |
| 2.5.1 Pointer Gestures | A | Supports | No functionality requires a multipoint or path-based gesture. The scrollable table responds to standard scrolling and to keyboard arrow keys when focused. |
| 2.5.2 Pointer Cancellation | A | Supports | All controls are native button and a elements activated on the up-event, with default browser behaviour preserved. No functionality is triggered on the down-event. |
| 2.5.3 Label in Name | A | Supports | Accessible names contain the visible label text. Buttons and links contain their visible text directly rather than overriding it with a differing aria-label. |
| 2.5.4 Motion Actuation | A | Not Applicable | No functionality is operated by device or user motion. |
| 3.1.1 Language of Page | A | Supports | Every page declares lang="en" on the html element. |
| 3.2.1 On Focus | A | Supports | Receiving focus does not initiate a change of context anywhere in the product. |
| 3.2.2 On Input | A | Supports | Changing a form control does not automatically submit the form or change context. Submission requires explicit activation of the submit button. |
| 3.2.6 Consistent Help | A | Supports | Contact details and the contact page link appear in the same relative order in the header navigation and site footer on every page. |
| 3.3.1 Error Identification | A | Supports | Validation errors are described in text and announced through a live region (role="status", aria-live="polite"). Errors identify the specific problem, for example a missing required field or a malformed email address. |
| 3.3.2 Labels or Instructions | A | Supports | Every form control has a persistent visible label programmatically associated with it. Required fields are marked. Additional guidance is provided for the free-text field. |
| 3.3.7 Redundant Entry | A | Supports | The contact form is a single step. No information is requested more than once within a process. |
| 4.1.2 Name, Role, Value | A | Supports | Native HTML elements provide name, role and value. State is exposed where it changes: aria-expanded on the navigation toggle, aria-current="page" on the active navigation item, and role="region" with an accessible name on the scrollable table. Verified structurally; not verified with a screen reader — see Evaluation methods. |
5. WCAG 2.2 Level AA
| Criterion | Level | Conformance | Remarks and explanations |
|---|---|---|---|
| 1.2.4 Captions (Live) | AA | Not Applicable | The product contains no live media. |
| 1.2.5 Audio Description (Prerecorded) | AA | Not Applicable | The product contains no synchronised media. |
| 1.3.4 Orientation | AA | Supports | Content is not restricted to a single display orientation. The layout is responsive in both portrait and landscape. |
| 1.3.5 Identify Input Purpose | AA | Supports | Form fields collecting information about the user carry appropriate autocomplete values: name, email, organization, and organization-title. |
| 1.4.3 Contrast (Minimum) | AA | Supports | Every colour declared in the stylesheet is measured programmatically against every surface token it can appear on, including composited values behind translucent layers, by an automated check that reads the stylesheet directly rather than a maintained list. All 45 text colours clear 4.5:1 on their worst-case surface. One colour is held to the 3:1 large-text threshold and is documented in the check as being used only at 38px and above. Four colours that fell short — at 3.35:1, 4.18:1, 4.22:1 and 4.43:1 — were corrected prior to this report. |
| 1.4.4 Resize Text | AA | Partially Supports | Content reflows without loss of information or functionality under browser zoom to 200% and beyond; this was verified indirectly through reflow testing down to 320 CSS pixels. However, font sizes are declared in absolute pixel units, so a user’s browser text-size preference alone may not resize text independently of full-page zoom. Planned remediation: migrate type scale to relative units. |
| 1.4.5 Images of Text | AA | Supports | All text is rendered as live text. No image of text is used for page content. The social sharing card contains text but is metadata, not page content. |
| 1.4.10 Reflow | AA | Supports | Verified at 320 CSS pixels with no loss of content or functionality and no two-dimensional scrolling of the page. The one wide element, a seven-row comparison table, scrolls horizontally within its own container, which is permitted for tabular data; that container is a labelled, keyboard-focusable region. |
| 1.4.11 Non-text Contrast | AA | Supports | Form control boundaries measure 3.17:1 against their own fill. Primary buttons measure between 3.56:1 and 4.17:1 against adjacent backgrounds. The focus indicator measures 8.07:1. All exceed the 3:1 requirement. Purely decorative borders are exempt. |
| 1.4.12 Text Spacing | AA | Supports | No text container declares a fixed height. Containers use min-height and content-driven sizing, so increased line height, paragraph spacing, letter spacing, and word spacing expand the container rather than clipping or overlapping text. |
| 1.4.13 Content on Hover or Focus | AA | Not Applicable | No additional content becomes visible on hover or focus. The product contains no tooltips, popovers, or hover-revealed menus. |
| 2.4.5 Multiple Ways | AA | Supports | More than one way is available to reach each page: a primary navigation menu present on every page, a footer navigation grouped differently by topic, and contextual cross-links within page content. A machine-readable sitemap is also published at /sitemap.xml. |
| 2.4.6 Headings and Labels | AA | Supports | Headings describe the section they introduce, and labels describe the control. Heading levels were verified programmatically across all pages with no skipped levels and exactly one h1 per page. |
| 2.4.7 Focus Visible | AA | Supports | A custom focus indicator replaces the browser default site-wide: a 2px solid outline with a 4px offset on links, buttons and form controls. Form controls additionally change border colour to 8.07:1 and gain a surrounding ring. All focus indicators exceed the 3:1 non-text contrast requirement against their adjacent surfaces. |
| 2.4.11 Focus Not Obscured (Minimum) | AA | Supports | The header scrolls with the page; no sticky or overlaying element covers content. The only fixed-position element is the skip link, which is itself the focused element when visible and is positioned clear of other content, so it cannot obscure a different focused item. |
| 2.5.7 Dragging Movements | AA | Not Applicable | No functionality requires a dragging movement. |
| 2.5.8 Target Size (Minimum) | AA | Partially Supports | Buttons and form controls exceed 24 by 24 CSS pixels; the primary action buttons are 48 to 50 pixels tall. Text links in the primary navigation and footer are smaller than 24 by 24 pixels and rely on the spacing exception, which the layout gaps appear to satisfy. That exception has not been exhaustively measured at every breakpoint, so this criterion is reported as partially supporting rather than assumed to pass. Planned remediation: increase the hit area of text navigation links with padding. |
| 3.1.2 Language of Parts | AA | Not Applicable | All content is in a single language. No passage differs from the page language. |
| 3.2.3 Consistent Navigation | AA | Supports | Navigation is identical in content and relative order on every page, in both the header and the footer. |
| 3.2.4 Consistent Identification | AA | Supports | Components with the same function are identified consistently. The primary call to action uses the same label, styling and icon throughout; recurring icons carry consistent meaning. |
| 3.3.3 Error Suggestion | AA | Supports | Error messages state what is wrong and what to do, for example identifying a missing required field or a malformed email address. Where a submission fails for a server-side reason, the message offers a direct email address as an alternative route. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Not Applicable | The product creates no legal commitment or financial transaction, and modifies or deletes no user-controllable data. The contact form initiates a business enquiry only. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Not Applicable | The product has no authentication process. |
| 4.1.3 Status Messages | AA | Supports | Form submission status — pending, success, and failure — is conveyed through an output element with role="status" and aria-live="polite", so it is announced without moving focus. Verified structurally; not verified with a screen reader — see Evaluation methods. |
6. Section 508 Chapter 3: Functional Performance Criteria
| Criterion | Conformance | Remarks and explanations |
|---|---|---|
| 302.1 Without Vision | Partially Supports | The product is built from semantic HTML with landmarks, headings, labelled controls, and text alternatives, and contains no information conveyed only visually. However, operation without vision has not been verified with a screen reader — see Evaluation methods. |
| 302.2 With Limited Vision | Partially Supports | All text meets or exceeds WCAG AA contrast, and content reflows to 320 CSS pixels without loss. Absolute pixel type sizing may limit text-only resizing (see 1.4.4). Not verified with screen magnification software. |
| 302.3 Without Perception of Color | Supports | No information is conveyed by colour alone. Status, validation, and current-page indication each use text or a non-colour visual cue in addition to colour. |
| 302.4 Without Hearing | Supports | The product conveys no information by sound. |
| 302.5 With Limited Hearing | Supports | The product conveys no information by sound. |
| 302.6 Without Speech | Supports | No functionality requires speech input. |
| 302.7 With Limited Manipulation | Partially Supports | All functionality is operable by keyboard alone and requires no simultaneous actions, dragging, or path-based gestures. Some text navigation links fall below the 24 by 24 pixel target size and rely on the spacing exception (see 2.5.8). |
| 302.8 With Limited Reach and Strength | Supports | No functionality requires sustained physical effort, simultaneous actions, or fine positioning beyond ordinary pointer or keyboard use. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | Navigation is consistent across pages, headings are descriptive, content is organised into short labelled sections, error messages are written in plain language, and motion is reduced automatically when the user requests it. No time limits are imposed. |
7. Section 508 Chapter 4: Hardware
Not Applicable. The product is a website. It includes no hardware component.
8. Section 508 Chapter 5: Software
Not Applicable. The product is web content as defined by Section 508 E205, and is evaluated against WCAG 2.2 in sections 4 and 5 of this report. It is not authoring software, and it is not software with a user interface outside a web browser. It provides no platform accessibility services of its own and does not disrupt those of the browser or operating system.
9. Section 508 Chapter 6: Support Documentation and Services
| Criterion | Conformance | Remarks and explanations |
|---|---|---|
| 602.2 Accessibility and Compatibility Features | Supports | Accessibility features, conformance status, and known limitations are documented publicly in the Accessibility Statement and in this report, both available without charge and without registration. |
| 602.3 Electronic Support Documentation | Supports | All support documentation is published as web pages on this site and is subject to the same WCAG 2.2 Level AA conformance reported in sections 4 and 5. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | No non-electronic support documentation is provided. |
| 603.2 Information on Accessibility and Compatibility Features | Supports | Support is provided by email at info@forgeprivate.ai, and can answer questions about the accessibility and compatibility features described here. |
| 603.3 Accommodation of Communication Needs | Supports | Enquiries are accepted by email, and content is offered in alternative formats on request. The Accessibility Statement publishes a response commitment of two business days to acknowledge and ten business days to respond substantively. |
10. Legal disclaimer
This report is provided by Forge AI Deployment for informational purposes and represents a good-faith self-evaluation of the product identified above, as of the report date, using the methods described in section 1. It is not a certification, and it is not a warranty or guarantee of conformance.
Conformance is assessed against the state of the product on the report date and may change as the product changes. This report does not cover third-party content, nor any AI system deployed by Forge AI Deployment inside a customer environment.
“VPAT” and “Voluntary Product Accessibility Template” are registered service marks of the Information Technology Industry Council (ITI).
Questions about this report: info@forgeprivate.ai