Legal
Accessibility statement
How well LetCompliance works for disabled people: how it was tested, what was fixed, what still needs work and how to report a problem.
- Standard
- WCAG 2.1 AA
- Status
- Partially meets
- Last reviewed
- 15 September 2026
Summary
LetCompliance partially meets the Web Content Accessibility Guidelines version 2.1 at level AA. Most of what was tested meets the standard; the known issues below do not yet.
If anything gets in your way, email LetCompliance; the aim is to reply within 5 working days.
How it was tested
On 15 September 2026 LetCompliance tested 29 pages of its website and app against WCAG 2.1 levels A and AA.
Website
- Home
- Pricing
- Features
- Making Tax Digital guide
- Contact
- Accessibility statement
Sign in and sign up
- Log in
- Sign up
- Forgot password
App
- Dashboard
- Properties
- Add a property
- Tenants
- Tenant inbox
- Rent
- Finance
- Bank statements
- Compliance
- Documents
- PRS Database
- Insights
- Tax
- Making Tax Digital
- Quarterly export
- Mileage log
- Tax pack
- Section 24 calculator
- Billing
- Settings
LetCompliance ran axe-core, an automated accessibility checker, on each page, and on 13 of the app pages again in the dark theme. By hand, on a sample of those pages, it checked that keyboard focus is visible, that the skip link works, that pages fit a screen 320 pixels wide, that nothing is lost when text spacing is increased and that animations follow the reduce motion setting.
Automated checks find only some accessibility problems. LetCompliance has not yet been tested with screen readers, or with disabled people using it for real tasks.
What was fixed
These problems were found in that testing and fixed on 15 September 2026:
- Buttons and small text without enough colour contrast, including the green buttons across the website and the grey text in the footer.
- Status labels, badges and buttons in the app without enough colour contrast, in both the light and dark themes.
- Dark theme colours that followed the computer’s setting instead of the app’s, which put pale text on white cards.
- Form field outlines too faint to see against a white background.
- Form fields and filters that a screen reader could not name.
- No way to skip past the menu: every page now starts with a “Skip to main content” link.
- A single-key shortcut that could be set off by accident. Search now opens with Ctrl+K, or Cmd+K on a Mac.
- Controls that showed no sign of keyboard focus, and a scrolling table that could not be reached with the keyboard.
- Menu names that were cut short when text spacing was increased.
- Pulsing status dots that never stopped, and a rotating review that kept moving after you chose one.
- Floating buttons that could still be reached with the Tab key while they were hidden.
- Animations on the website that played even with the reduce motion setting switched on.
- Links inside paragraphs that stood out by colour alone.
- Dashboard content that ran off the edge of narrow phone screens.
- Labels in the app that were faded until they were hard to read.
Known issues
These parts of LetCompliance may not yet meet WCAG 2.1 AA, or have not been checked:
Pages not yet tested
Other pages, including lettings and agency features, older guides, blog posts and free tools, may still have low-contrast text or other problems. They are being checked in turn.
Screen readers
LetCompliance has not yet been tested with screen readers such as NVDA, JAWS or VoiceOver, so some controls may not be announced clearly.
PDF documents
The PDFs LetCompliance creates, such as tenancy agreements, notices and compliance packs, are not tagged for screen readers. If you need a document in another format, ask for one.
Videos
The LetCompliance product videos are hosted on YouTube, and their captions have not been checked.
Services run by others
Pages provided by other organisations, such as Stripe for payments and the HMRC sign-in for Making Tax Digital, are outside the control of LetCompliance.
Compatibility
Report a barrier or ask for another format
If something on LetCompliance is hard or impossible for you to use, or you need information in a different format, get in touch. Say which page it was and what went wrong.
If you email, put ACCESSIBILITY in the subject line. Your message will be acknowledged, and the aim is to reply within 5 working days.