Accessibility statement for the documentation site

Documentation accessibility approach

The documentation site uses semantic HTML, one h1 per page, landmarks, skip links, visible focus styles, responsive tables, meaningful link text, and text-first workflow diagrams.

Supported interaction expectations

• Keyboard users should be able to reach navigation, content, tables, callouts, details sections, and related-page links.
• Screen-reader users should encounter logical headings, landmarks, table headers, and descriptive link text.
• Responsive layouts should preserve readable line length and table access.
• Motion is minimal and respects reduced-motion preferences where transitions are present.

Known documentation limitations

The docs do not claim formal accessibility certification. Screenshots, where present, are supplementary and should have surrounding text explaining the workflow. If a screenshot is unclear or decorative, the text guide remains the primary source.

Product accessibility boundary

A11Y Cat itself is an accessibility inspection tool, but that does not automatically make every extension UI state or documentation page perfect. UI accessibility should continue to be tested with keyboard-only operation, zoom/reflow, reduced motion, and assistive technology review.