Accessibility statement

Last updated: 18 May 2026

What we aim for

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We test on real assistive technology (VoiceOver on macOS/iOS, TalkBack on Android, NVDA on Windows) and we implement WCAG 2.2 success criteria as part of every release.

What we've built in

• Skip link to main content on every page
• Semantic HTML throughout (heading hierarchy, landmark roles, proper button vs link semantics)
• Body text at 16px minimum, headings scaled with rem so they respect browser zoom and user font-size preferences
• Colour contrast: navy (#0A284E) on cream (#FAF7F2) exceeds 13:1 (WCAG AAA). Amber CTAs on navy exceed 7:1 (AAA).
• All interactive controls at least 44×44 px (WCAG 2.5.5 target size)
• Visible focus rings (amber outline, 2px, 3px offset) on every interactive control
• Form labels are programmatically associated with inputs. Required fields are marked both visually and via aria-required
• Motion (entrance fades, hover lifts) is automatically disabled when prefers-reduced-motion: reduce is set
• lang="en-GB" on every page; lang="cy" on Welsh-language /cymru/* routes
• Country code on phone-input fields locked to +44, no 250-row global dropdown
• No autoplay video. No auto-advancing carousels. No content that flashes more than 3 times per second.
• Calculator, eligibility quiz, letter builder all work with keyboard only and with screen readers

Known limitations

Things we're aware of and working on:

• Zoho-embedded forms (on /start-claim, /refer, and the form host pages) are third-party iframes, their accessibility is governed by Zoho. We've raised specific issues with them; in the meantime, you can complete the same actions by calling 0800 030 4669 or emailing help@supportfortenants.co.uk.
• Markdown-rendered tables on a few law-topic and news pages don't have proper <caption> elements. We're adding them in the next release.
• OG images are rendered server-side as PNGs and include text. They're for social sharing only, never the primary route to information, which is always available in HTML text on the page itself.
• PDF letter output from the letter builder is not yet a tagged PDF. We provide the same content as accessible HTML in the "Preview letter" button.

How to reach us if a page is inaccessible

If something on this site is preventing you from getting the information or service you need:

• Phone (24/7 voicemail outside hours): 0800 030 4669
• WhatsApp: wa.me/448000304669
• Email: help@supportfortenants.co.uk , please include "accessibility" in the subject so it's routed straight to the team who can fix it

We aim to respond to accessibility queries within one working day.

If we can't resolve it

You can escalate to the Equality and Human Rights Commission (EHRC) who enforce the public-sector and private-sector accessibility duties under the Equality Act 2010.

About this statement

This statement was prepared on 18 May 2026 and is reviewed every 6 months. The site was last tested against WCAG 2.2 AA in May 2026.

We use a combination of automated testing (axe-core in CI), manual keyboard-only testing, and screen-reader testing (VoiceOver/NVDA/TalkBack) before every release.

See also our our promise page for the full list of things we commit to.