Our commitment
We build machines meant to work alongside people. A website that excluded some of those people would be an odd way to introduce them. This statement explains what we have done, what we know is imperfect, and how to tell us when we have got it wrong.
We aim to meet WCAG 2.2 Level AA across gen3order-optim.us.
Conformance status
Partially conformant with WCAG 2.2 Level AA. "Partially conformant" means most of the site meets the standard and some content does not yet. The known exceptions are listed below rather than buried.
Assessment method: self-evaluation, carried out in September 2026 using automated testing, manual keyboard-only traversal, and screen reader spot checks with VoiceOver on macOS and NVDA on Windows.
What we have implemented
- A skip link to the main content as the first focusable element on every page.
- Text contrast of at least 4.5:1 for body copy and 3:1 for interface boundaries, verified in both the light and dark sections of the design.
- Visible focus indicators on every interactive element, never removed and never obscured by the fixed header.
- Full keyboard operability, including the interactive systems diagram, whose markers are real buttons with arrow-key traversal across the subsystem list.
- Form fields with persistent visible labels, helper text, inline errors placed next to the field, and a focusable error summary that links to each invalid field after a failed submission.
- Semantic headings in sequence, landmark regions, and descriptive alternative text on every meaningful image. Decorative images carry an empty
alt. - A long text description for the technical systems drawing, so its content is available without seeing it.
- Touch targets of at least 44×44 CSS pixels with adequate spacing.
- Full support for
prefers-reduced-motion: the scrolling ticker, reveal animations, counters and parallax all stand still, and the page renders in its final state. - Layout that reflows to 320 CSS pixels without horizontal scrolling, and that tolerates 200% text zoom.
- No time limits, no auto-playing audio or video, and no content that flashes.
Known limitations
We would rather publish these than let you discover them:
- Systems diagram on small screens. The marker targets sit close together below 400 px width. The subsystem buttons beneath the drawing provide the same content and the same selection, and are the recommended route on a phone.
- Scrolling specification ticker. It pauses on hover and on focus and is hidden from assistive technology as decoration, but it has no explicit pause button. It carries no information that is not stated elsewhere on the page. A control is planned.
- Third-party web fonts. If the font service is slow, text may briefly render in a fallback face. Text remains readable throughout; no invisible-text period occurs.
- Long specification tables. On narrow screens these require some vertical scrolling that a wider layout would not. Content and reading order are unaffected.
Compatibility
The site is tested against the current and previous major versions of Chrome, Edge, Firefox and Safari on desktop, and Safari on iOS and Chrome on Android. It is designed to work with screen readers, screen magnification, speech input and switch access.
It does not depend on JavaScript for its content: with scripts blocked, every section remains readable, every link works, and the specification table falls back to its default configuration. Interactive enhancements — the diagram selection, the accordion and client-side form validation — are progressive additions.
Feedback and alternative formats
If you meet a barrier on this site, or need any of this content in another format — plain text, large print, or a structured document — write to [email protected].
- We acknowledge within 2 business days.
- We aim to provide requested alternative formats within 10 business days.
- We will tell you what we intend to do about a reported barrier and when, or explain honestly why we cannot fix it.
You can also reserve a unit by writing to [email protected] instead of using the form, with no disadvantage in queue position.
Enforcement
If you are not satisfied with our response, you may contact the accessibility enforcement body in your jurisdiction — for example the Equality Advisory and Support Service in the United Kingdom, or the relevant national authority implementing the European Accessibility Act. In the United States, complaints may be directed to the appropriate federal or state agency.
We would like the chance to resolve it directly first, and we treat accessibility reports as defects rather than as requests.