Accessibility statement
Draft — under review
This statement reflects our July 2026 automated accessibility testing (axe-core and Playwright, checked against WCAG 2.2 A/AA). It is not a substitute for a full manual audit or testing with real assistive-technology users, has not been checked by an accessibility specialist or solicitor, and will be completed and reviewed by Pete before launch.
How we're working to make this site usable by everyone, what we know still needs work, and how to tell us if something isn't working for you.
Our commitment
directory.lgbt is committed to making this website usable by as many people as possible, including people using a screen reader, screen magnification, speech recognition, or keyboard-only navigation. This statement covers directory.lgbt (every page on this site) — what we already meet, what we know still needs work, and how to report a problem.
How accessible this website is
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA — the internationally recognised accessibility standard. We test key pages and flows using automated tools (axe-core and Playwright) that check against these guidelines. Automated testing alone can't catch everything a full manual audit or testing with real assistive-technology users would — see "What we're still working on" below for the specific gaps our testing has already found.
What we're still working on
Our own automated testing has found some specific things that don't yet fully work, listed here honestly rather than left for you to discover:
On mobile, opening the "Filters" panel doesn't automatically move your keyboard focus into it — once it's open, you may need to press Tab once or twice to reach the filter controls. Once your focus is inside the panel it's trapped correctly, and it returns to the "Filters" button when you close it.
Applying filters updates the results and the on-screen count, but doesn't yet announce the new count to screen readers — if you use one, move to the results heading after applying filters to hear the updated total.
The interactive map's location markers currently don't render in some environments, due to a third-party map-tile hosting issue we're aware of and working to fix. Every listing is always also available as a plain, fully accessible list — the map is never the only way to reach a listing.
If JavaScript is switched off or fails to load, the search page's heading and search box still appear, but the result listings themselves currently need JavaScript to display. We're working on making the first page of results available without JavaScript too.
Reporting an accessibility problem
We're still testing this site, so you may find other problems we haven't listed above. If you have trouble using any part of this website, email [email protected] describing the page and what happened — we'll get back to you as soon as we can.
If you're not happy with our response
directory.lgbt is an independent service, not a public sector body, so the accessibility regulations that apply to government and public-sector websites don't apply to us directly — but we still aim to meet the same WCAG 2.2 AA standard those regulations require. If you're not satisfied with how we've responded to an accessibility problem, the UK's Equality Advisory and Support Service (EASS) can advise on accessibility and equality rights across England, Scotland and Wales.
How we test, and when this statement was last reviewed
This statement was prepared in July 2026, based on automated accessibility testing (axe-core and Playwright, checked against WCAG 2.2 Level A and AA) completed that month. We intend to review this statement again before this website's public launch, and at least once a year after that.