Iron Evaluation complete. No unresolved WCAG 2.2 Level A or AA barriers were identified within the covered public web properties as of July 28, 2026.
Scope
Methods
- Standards-based code and content review across every owned public page template.
- Automated WCAG 2.2 Level A and AA checks in Chromium, Firefox, and WebKit.
- Keyboard-only review of navigation, dialogs, forms, search, pagination, and documentation controls.
- Responsive reflow, browser zoom, text-spacing, contrast, forced-colors, and reduced-motion checks.
- Assistive-technology review with VoiceOver on macOS and browser accessibility-tree inspection.
Assistive-technology matrix
- Current Chromium, Firefox, and WebKit browser engines at desktop and mobile viewport sizes: completed
- Safari with VoiceOver on macOS: completed
- Keyboard-only operation and browser accessibility APIs: completed
Results
| Assessment area | Result | Evidence |
|---|---|---|
| WCAG 2.2 Level A and AA | Supports | All scoped public routes passed standards review and automated accessibility checks. |
| Keyboard and focus | Supports | Navigation, dialogs, drawers, search, forms, pagination, and documentation controls are keyboard operable. |
| Responsive presentation | Supports | Pages support 320 CSS pixel reflow, text spacing, zoom, forced colors, and reduced motion. |
| Assistive technology | Supports | Headings, landmarks, names, roles, states, reading order, errors, and status messages were reviewed. |
| Revised Section 508 | Supports | Applicable functional-performance, web-software, and support-documentation provisions were evaluated. |
Accessibility features
- Skip links and semantic landmarks support efficient navigation.
- Visible focus indicators and keyboard-operable controls support non-pointer use.
- Responsive layouts support reflow, zoom, text spacing, forced colors, and reduced motion.
- Forms provide programmatic labels, instructions, error identification, and status announcements.
- Dialogs expose names, roles, states, focus containment, Escape dismissal, and focus return.
- Documentation controls, code samples, and API reference content use accessible semantic structures.
Known limitations
No unresolved accessibility limitations were identified in the assessed scope.
Maintenance
Accessibility requirements are included in design, engineering, content, and quality reviews. The covered properties are reassessed after material interface changes and when accessibility feedback identifies a potential barrier.
Last reviewed: July 28, 2026