accessibility
AMC should be usable without relying on color or pointer-only interaction.
Last reviewed: 2026-06-16. This statement covers the public website, browser playground, generated dashboard, local Studio, and CLI output conventions.
Standards Target
- Website and generated dashboard: WCAG 2.2 AA-aligned checks for contrast, focus visibility, skip navigation, and chart names.
- Generated dashboard: Settings includes a high-contrast theme, and the onboarding dialog traps keyboard focus while open.
- Generated dashboard heatmaps expose score, target, gap, and confidence as text plus ARIA grid, gridcell, selected-state, and meter values.
- CLI: color is supplemental. Use
NO_COLOR=1or--no-colorfor plain output where supported. - Evidence: accessibility claims should be backed by tests, not only screenshots.
Current Support
- Static pages include skip links and keyboard focus-visible styling.
- Decorative canvases are hidden from assistive technology.
- Playground and generated console chart canvases expose descriptive accessible names.
- The generated dashboard secondary-text token was raised from the low-contrast value flagged in the audit.
- The generated dashboard can switch to a high-contrast theme for low-vision review.
- The generated dashboard question heatmap includes visible maturity, gap, and confidence labels so color is supplemental.
Known Limitations
- Interactive terminal prompts depend on terminal and screen-reader support.
- Dense generated reports still need manual screen-reader review with representative data.
- Automated axe checks do not replace manual keyboard and assistive-technology testing.
Feedback
Open an issue with the affected page, command, or artifact path; assistive technology and browser or terminal used; expected result; actual result; and any screenshot, terminal output, or axe report.