Automated evaluation
axe-core run against every page at 1280, 768 and 320 pixels wide, covering the WCAG 2.0 A and AA, WCAG 2.1 A and AA, and best practice rule sets. Zero violations at the time of writing.
axe-core, all pages, three breakpoints
Home / Accessibility statement
Accessibility statement
A practice that evaluates other organizations should be willing to publish the same account of itself, including the parts that are not finished. This statement is written to the level of detail the practice asks of clients.
Partially conformant means parts of the content do not fully conform, or conformance has not yet been established by full manual evaluation. The practice states this rather than claiming full conformance, because an automated pass covers only a portion of the applicable success criteria and a claim beyond the evidence would be the same overstatement this practice warns clients about.
Stated in enough detail that a reader can reproduce it.
axe-core run against every page at 1280, 768 and 320 pixels wide, covering the WCAG 2.0 A and AA, WCAG 2.1 A and AA, and best practice rule sets. Zero violations at the time of writing.
axe-core, all pages, three breakpoints
Tab order verified on every interactive element. Skip link, disclosure controls, the self-assessment checkboxes, the scrollable calendar region and all form fields confirmed operable by keyboard with a visible focus indicator.
2.1.1, 2.4.3, 2.4.7
Every text and background pair computed. Text over the hero photographs measured against the composited image with the text hidden, giving 6.68:1 at desktop and 12.06:1 at mobile in the worst case.
1.4.3, 1.4.11
Verified at 320 pixels with no horizontal scrolling of the page, and at the 200 percent zoom equivalent with no loss of content or function.
1.4.4, 1.4.10
Heading order checked for skipped levels on every page. Landmarks, list semantics, table header scope, form labelling and accessible names verified programmatically.
1.3.1, 2.4.6, 4.1.2
Both published PDFs confirmed tagged, with document language and document title set, and configured to display the title rather than the filename.
1.3.1, 2.4.2, 3.1.1
Listed because a statement without limitations is usually a statement that was not tested.
If any part of this site prevented you from doing what you came to do, the practice wants to know, including the parts already listed above.
Email info@adaaccessforall.com. Describing the page and what you were trying to do helps, but no particular format is required and no technical detail is expected.
No form required
Acknowledgement within two business days, with an assessment and either a fix or a target date. Reports that identify a genuine barrier are added to the limitations above until resolved.
Two business days
Any document or page content on this site is available in an alternative format on request, at no charge and with no explanation required.
On request