Accessibility

Where we are

Our target is WCAG 2.1 Level AA. We have not yet been audited against it, and we are not claiming conformance. Publishing a conformance statement we have not tested would be worse than publishing nothing.

What is in place

• Interactive components — menus, dialogs, tabs, toggles, tooltips — are built on Radix UI primitives, which provide keyboard operation and ARIA semantics.
• Every page is reachable and operable with a keyboard.
• Semantic HTML with real headings, labels and landmarks.
• Colour is never the only way information is conveyed; statuses carry text.
• Responsive layouts that work when text is enlarged.

What we know is not done

We would rather list these than let you discover them.

• No third-party accessibility audit has been carried out.
• No automated accessibility checks run in our build yet.
• The interactive community map is visual. There is no non-visual equivalent of the map itself, though the same lot and home records are available as ordinary lists and tables.
• Screen-reader testing has been informal rather than systematic.
• Colour contrast has not been verified across every component.
• PDFs uploaded by an association are the association's documents and may not be tagged for accessibility. We cannot fix a document we did not author.

What we are doing about it

• Adding automated accessibility checks to our build pipeline.
• Commissioning an audit before general availability.
• Treating a reported barrier as a defect, on the same track as any other bug.

Tell us about a barrier

If something stops you using CommunityPilot, please write to accessibility@communitypilot.net with the page and what happened. We aim to acknowledge within two business days and to tell you what we can do and by when.

If you need information from CommunityPilot in another format, ask us and we will provide it.