Last reviewed: September 5, 2026
What we aim for
This site is built toward the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. In practice that means a clear heading structure on every page, text that meets contrast requirements against its background, controls that can be reached and operated with a keyboard alone, links whose purpose is clear from their own wording, form fields with real labels, meaningful alternative text on images that carry information, and respect for a reduced-motion preference set in your operating system.
These are commitments about how the site is built. They are not a legal guarantee that every page meets every criterion at every moment. Where the site falls short, we would rather hear about it and fix it.
Using this site
The main navigation, the inspection-request form, the guides and the expandable questions are designed for keyboard and screen-reader use. Browser zoom and text resizing up to 200% should not hide content or cut off controls. Each page uses one main heading with nested subheadings, so a screen reader can be used to skim a page rather than read it end to end.
The site sets no advertising cookies, plays no media automatically, and uses no pop-up that traps keyboard focus.
No accessibility overlay
This site does not use an accessibility overlay, toolbar or widget. Overlays are marketed as an instant fix and are widely reported by disabled users and by assistive-technology vendors to interfere with the screen readers, magnifiers and browser settings people have already configured. Building the underlying pages correctly is the approach taken here instead.
If you use a screen reader, magnifier, voice control or any other assistive technology, this site is intended to work with the tools you already have set up.
Known limitations
Where a page embeds a third-party service or a document produced by someone else, we cannot guarantee that content meets the same standard as the pages around it. If you reach one of these and need the information another way, ask and it will be provided directly.
Automated checks find common problems but cannot judge whether a page is genuinely usable. Feedback from real use is the part that cannot be generated automatically.
Telling us about a barrier
If any page, control, form or document on this site is difficult or impossible to use, please tell us. Use the request form and begin the details field with the word “Accessibility”. Include the page address and what happened — what you were trying to do, what your assistive technology did, and what you expected instead. That detail is what makes a report actionable.
We aim to acknowledge accessibility reports within five business days and to give you either a timeframe for a fix or another way to get the information in the same reply. Please do not include sensitive personal information in an accessibility report.
How this statement is maintained
Accessibility is reviewed whenever the site’s shared templates or primary interactions change, rather than on a fixed calendar, because a template change is what actually moves accessibility across many pages at once.
This statement will be revised when the site’s structure changes materially, or when a reported barrier changes what can honestly be claimed here.