Accessibility

We aim for WCAG 2.2 AA-level practice across PracticalBench: semantic heading structure, keyboard-navigable interactive elements, visible focus states, labelled form fields, sufficient colour contrast, and layouts that reflow on mobile without loss of function.

Search and navigation are built to remain usable if JavaScript fails to load — core links are plain, crawlable HTML, not JavaScript-dependent.

If you find an accessibility barrier on any page, please tell us — use our contact form with topic "General question" and mention "accessibility" so we can prioritise it.