The directory’s accessibility approach, supported interactions, known content dependencies, and a practical route for reporting barriers.
Our approach
The theme and plugin are designed for semantic headings and landmarks, keyboard operation, visible focus, labelled forms, status announcements, responsive reflow, reduced motion, high contrast, and accessible comparison tables. The target is WCAG 2.2 Level AA for the components supplied with this package.
Content outside the package
Site owners control uploaded documents, images, logos, authored pages, third-party embeds, menus, plugins, and imported descriptions. Those items can introduce barriers even when the directory interface is accessible. Linked regulator and provider sites follow their own accessibility practices.
Report a barrier
Tell the site owner which page and control caused difficulty, what device, browser, and assistive technology you used, and what format or outcome you need. Do not include medical or other sensitive information. The site owner should acknowledge the report, offer a reasonable alternative, and track remediation.
Ongoing checks
Review keyboard navigation, zoom and reflow, form errors, screen-reader names, contrast, forced-colors mode, print output, and imported content after material changes. Automated tests help find problems but do not replace testing with disabled people and relevant assistive technologies.