Accessibility and Standards
OPERATOR targets WCAG 2.2 AA. Automated checks and the verification workbench support evaluation; they do not establish application conformance. No issued ACR, completed VPAT® or independent certification is claimed.
Environment coverage
The automated browser matrix targets desktop Chromium, Firefox and WebKit plus an iPhone WebKit viewport on the test host. The workbench includes the core controls, all six recipes, advanced forms, bundled font specimens and a 10,000-record table. Engine emulation does not establish native Windows, Linux or iOS qualification.
Keyboard paths, current font loading, 320 CSS-pixel containment, text spacing, large-table windowing and Chromium forced colors have dedicated regression checks. Human screen-reader announcements, native font installation/raster behavior and deployed hardware still need separate evaluation. Designer handoff is deferred while the system is being polished.
Accessibility targets
| Area | Target |
|---|---|
| Text contrast | 4.5:1 for normal text; 3:1 for large text. Check actual color pairs. |
| Non-text contrast | 3:1 for required component and graphical information, with applicable exceptions. |
| Keyboard focus | Visible, logically ordered and not entirely obscured by authored content. |
| Pointer targets | Prefer 24×24 CSS pixels; assess applicable spacing and other exceptions. |
| Status and errors | Text or other non-color cues, accessible names and appropriate announcements. |
See WCAG 2.2, Focus and the W3C target-size guidance. Focus Not Obscured (2.4.11) is AA; Focus Appearance (2.4.13) is AAA. A focus token alone proves neither.
Evidence and remaining evaluation
Component tests cover selected semantics, keyboard interactions and axe rules. Token checks assess defined color pairs. Browser tests cover styled controls and the six recipe previews, with interaction checks and review screenshots. The workbench scans its current preview.
Human evaluation still needs to cover screen readers, complete workflows, zoom,
text spacing, overlays, forced colors and real content. Screenshots are review
evidence, not automated pixel comparisons. Maintainers track scope in
docs/compliance/accessibility-assessment.md and commands in docs/release.md.
Standards scope
Section 508 and procurement
An ACR covers a defined product and version. Revised Section 508 includes WCAG 2.0 A/AA and other applicable ICT provisions; OPERATOR's WCAG 2.2 target does not replace that assessment. Consult Section508.gov and the ITI VPAT® templates. The internal worksheet is preparation material, not an issued report.
Human engineering and operational symbology
MIL-STD-1472 informs the design goals. Readability depends on the display, viewing distance, ambient conditions and users. Alert recognition, workload and update latency require system measurements and user evaluation; this library establishes no fixed recognition-time, latency or category-count claim.
Affiliation tokens and C2 icons support interface composition. They are not a
MIL-STD-2525 map renderer. Symbol identification, frames, modifiers, placement and
program-specific validation remain application responsibilities. See
docs/compliance/standards-alignment.md for assessment boundaries.