Jetstream2 Docs Acessibility FAQ¶

What steps have been taken thus far to bring the Jetstream2 Docs into accessibility compliance?¶

Ran automated WCAG 2.1 AA checks using Pa11y CI (npx pa11y-ci) against the built/static site. (26-March)

Ensured comprehensive coverage by generating the test URL list from site/**/index.html. (26-March)

Enabled MkDocs theme template overrides using theme.custom_dir: overrides in mkdocs.yml to allow accessible markup adjustments. (26-March)

Improved navigation accessibility by adding an accessible label for the Table of Contents toggle (id="__toc") so it is announced appropriately by screen readers. (26-March)

Improved semantic structure by replacing non-submitting theme
wrappers (palette/search UI containers) with non-form containers to avoid incorrect form semantics. (26-March)

Added or corrected alternative text for meaningful images, including linked images where the image was the only content. (26-March)

Replaced deprecated presentational HTML attributes (e.g., align="right") with CSS styling (style="float: right;") to separate presentation from structure (26 March update).

Addressed color contrast issues identified in evaluation (e.g., footer copyright text, blockquote text) via custom.css. (26-March)

Reviewed embedded content for accessibility and ensured embedded frames have accessible identification (e.g., descriptive labeling). (26-March)

Updated site navigation (mkdocs.yml nav:) to include the Accessibility FAQ for easier discovery. (26-March)

Progress of Work¶

More accessibility checks will be run.

Each change or check was made close to the Month and Year, eg: (26-March), listed.

February 25, 2026 February 25, 2026