Accessibility statement
A statement is worth something only if it names what fails. Ours does.
Conformance
revrepute.com is intended to conform to WCAG 2.2 Level AA. We believe it does, with the exceptions listed further down.
"Intended to conform" is the honest phrasing. Automated tooling covers perhaps a third of the criteria; the rest is judgement, and judgement can be wrong. Where we have tested and passed, we say so. Where we have not tested, we say that too.
What was tested, and how
| Area | Method | Result |
|---|---|---|
| Colour contrast (1.4.3) | Every text node on every page measured programmatically against its computed background, at the size and weight it renders | Passes AA on all pages. Two palette tokens were darkened from the design reference to achieve it |
| Keyboard operation (2.1.1, 2.1.2) | Full tab traversal of navigation, menu, FAQ disclosures, forms and the consent dialog | All controls reachable and operable. The consent panel traps focus while open and releases it on close |
| Focus visibility (2.4.7, 2.4.11, 2.4.13) | Visual check of every focusable control, including behind the sticky header | Two-pixel focus ring on all controls. Scroll padding keeps focused elements clear of the sticky navigation |
| Target size (2.5.8) | Minimum dimension check on links, buttons and toggles | All interactive targets clear 24 by 24 CSS pixels |
| Structure and landmarks (1.3.1, 2.4.6) | Heading order and landmark audit per page | One h1 per page, no skipped heading levels, single main landmark, labelled navigation regions |
| Non-text content (1.1.1) | Every illustration reviewed for whether it carries meaning | Illustrations are inline SVG with a title element and an accessible role; decorative shapes are hidden from assistive technology |
| Forms (3.3.1, 3.3.2, 3.3.3) | Submission with empty and invalid values, with and without JavaScript | Errors are announced, associated with their field, described in text, and focus moves to the first problem |
| Motion (2.3.3) | Rendering under prefers-reduced-motion | The single page-load animation and all transitions are suppressed |
| Reflow and zoom (1.4.4, 1.4.10) | 320 pixel viewport and 200 per cent text zoom | No horizontal scrolling and no clipped content. Wide tables scroll inside their own container |
| Text direction | Full page rendered with dir="rtl" | Layout mirrors correctly. The stylesheet uses logical properties throughout, so a right-to-left language would not need a separate sheet if one is added later |
Known gaps
These are open, not disputed. Each has an owner.
- No screen reader testing on real assistive technology yet. The markup was built to standard and checked in the accessibility tree, but nobody has driven this site with VoiceOver, NVDA or JAWS. Until that happens, treat the conformance claim as provisional.
- No testing with disabled users. An audit is not the same as watching someone try to get a proposal. We intend to arrange this before launch.
- No independent audit. Everything above was tested by the team that built the site, which is the weakest form of evidence.
- Only English is published. Spanish-language pages have not been produced, and no right-to-left content has been reviewed by a native speaker for line breaking, numerals or typography.
- Downloadable resources are not yet accessible. The files on the resources page do not exist. When they do, each needs a tagged, reflowable PDF or an HTML equivalent.
Found a barrier? Tell us.
Write to accessibility@revrepute.com with the page, what you were trying to do, and what stopped you. Your browser and assistive technology help but are not required.
- We acknowledge within 2 working days.
- We give you an assessment and a fix date within 10 working days.
- If we cannot fix it quickly, we will offer the information or service another way while we work on it.
Statement prepared using the W3C accessibility statement generator format. Last reviewed: 6 September 2026