Read clear page content
Pages use headings, short sections, tables, lists and summaries so users can scan guides and find the route they need.
Accessibility statement
Making renting information easier to access and use
This is the accessibility statement for Renters Rights Toolkit. It explains how we aim to make our England private renting tools, guides, templates, forms and evidence prompts accessible, what is not yet fully accessible, and how users can report problems.
Current status:
Renters Rights Toolkit is not a public authority, but we use WCAG 2.2 Level AA as our practical benchmark. We describe the website as partially conformant because some custom tools, dynamic grids and older page components still need further manual testing and improvement.
1. What this accessibility statement covers
This statement covers the Renters Rights Toolkit website at rentersrightstoolkit.co.uk, including the homepage, tools, blog posts, supporting pages, contact form, evidence prompts, checker results, templates, navigation, source sections and FAQs.
It is written for all users, including private renters, landlords, agents, advisers, support workers and people using assistive technology to access housing information.
Because renting information can affect someone’s home, money, safety and legal position, we aim to make the website practical, readable and usable even when a user is under stress or using a mobile device.
2. Standard we aim for
We aim to follow the Web Content Accessibility Guidelines version 2.2 at Level AA where practical. WCAG is organised around four principles: content should be perceivable, operable, understandable and robust.
WCAG 2.2 includes testable success criteria at A, AA and AAA levels. Our practical target is Level AA because it is the recognised benchmark used by UK government digital accessibility guidance.
We do not claim that every page or tool is fully compliant. We are using this statement to explain the current status honestly and to prioritise improvements.
3. Preparation, review and testing status
This statement has been prepared for the current Renters Rights Toolkit structure: a static HTML website with shared CSS, reusable header/footer scripts, dynamic tools and posts data files, contact form handling, long-form guides and interactive renting checkers.
| Statement prepared | 5 May. |
|---|---|
| Last reviewed | 5 May. |
| Next planned review | After major CSS, header, navigation, form, tool or checker updates. High-risk pages and core tools are reviewed first. |
| Conformance status | Partially conformant with WCAG 2.2 Level AA as a practical benchmark. Full independent audit not yet completed. |
| Testing approach | Editorial and technical review using semantic HTML checks, keyboard navigation checks, focus visibility checks, mobile layout checks, form label review, heading structure review, contrast review and targeted manual inspection of priority pages. |
| Independent audit | No full independent WCAG audit has yet been completed. If one is carried out later, this page should be updated with the audit scope and key findings. |
4. What users should be able to do
The website is designed so users can reach important renting information without relying on complex interactions or visual-only cues.
Navigate without a mouse
Links, buttons, details panels, menus and form controls should be reachable by keyboard, with visible focus indicators.
Use zoom and responsive layouts
Pages are designed to reflow on smaller screens and remain readable on mobile, tablet and desktop layouts.
Understand form fields
Contact and tool forms should use labels, hints, required-field markers and clear error or warning messages.
Use semantic structure
Pages use semantic HTML, heading order, labelled controls and meaningful link text where possible.
Avoid decoration-only meaning
Decorative images or icons should not be required to understand the content. Important warnings are also provided as text.
5. Accessibility approach by feature
Renters Rights Toolkit includes static pages, dynamic tool cards, post grids, contact forms, checkers, letters and evidence prompts. Each feature has different accessibility risks.
| Navigation | Header, footer, skip link, page headings, internal links and clear button text should help users move through the site quickly. |
|---|---|
| Guides and posts | Long-form content should use clear headings, tables, lists, FAQs, source sections and related links so users can scan by topic. |
| Tools and checkers | Tool questions should use labels, hints and grouped controls. Result sections should explain risks, missing evidence and next steps in text. |
| Forms | Form fields should have visible labels, required indicators, input types, hints and validation messages that do not rely only on colour. |
| Tables | Tables should be used for comparison data, not page layout. On small screens, tables should remain readable or stack clearly. |
| Images | Decorative images should have empty alt text where appropriate. Meaningful images should have descriptive alt text where used. |
| Interactive details | FAQ dropdowns use native <details> and <summary> elements so they remain keyboard-accessible in modern browsers. |
| Scripts | JavaScript should enhance the page where possible. Important content should not depend only on scripts where a non-script fallback is needed. |
6. Users we consider
Accessibility is not only about screen readers. Renting information may be needed by users with many different access needs, including temporary or situational needs.
- screen reader users;
- keyboard-only users;
- users with low vision or magnification needs;
- users with colour vision differences;
- users with dyslexia, ADHD, memory or cognitive processing needs;
- users with limited dexterity or motor control;
- users using mobile phones under stress;
- users with limited English or unfamiliarity with legal terms;
- users dealing with urgent housing risk or emotional pressure.
7. Content accessibility
The site aims to present private renting information in plain, direct UK English without assuming users already understand legal terminology.
Where a legal term is necessary, pages should explain it in context. Longer guides should include definitions, quick answers, tables, examples, FAQs and source links so users can understand both the issue and the next step.
We avoid hiding critical warnings inside images, icons, decorative graphics or colour alone. Important warnings should be available as text.
8. Known accessibility issues by website area
These are the areas we know may need further testing or improvement. This section is intentionally specific so users and search engines can see the real current status.
Mega menu and header behaviour
The header and menu should be keyboard-accessible, but the full mega-menu behaviour needs further testing with screen readers, mobile keyboard navigation and zoom.
Latest posts and tools
Cards generated from tools-data.js and posts-data.js should remain readable and keyboard accessible. We need continued checks that generated cards have meaningful link text and stable layouts.
Complex checker forms
Long forms may need additional review for field grouping, progress indication, error recovery, result announcement and screen reader output.
Large comparison tables
Some long legal comparison tables may be difficult on small screens or when zoomed. We aim to keep them readable and structured.
Form handling and external content
Contact form handling, external images, analytics, advertising, embedded media or other third-party services may have accessibility limitations outside our full control.
Legacy class conflicts
Some older pages may need CSS and heading-structure review as the toolkit grows. We prioritise pages used for urgent or high-risk issues.
Decorative images and card media
Some guide cards use decorative images. Important meaning should not depend on those images, and decorative images should not create unnecessary screen reader noise.
Future PDFs or downloads
If downloadable PDFs or generated documents are added later, they may require separate accessibility checks for headings, reading order, tags, tables and form fields.
Sticky or dynamic result areas
Some checker result panels may update dynamically. We need continued checks that updated results are understandable and do not trap focus or hide content.
9. Accessibility checklist used when updating pages
This checklist explains the practical rules we aim to apply when publishing or updating pages.
| Page structure | One clear H1, logical H2/H3 structure, descriptive section headings and no heading levels used only for visual styling. |
|---|---|
| Keyboard access | Links, buttons, form fields, menus and dropdowns should be reachable and usable with a keyboard. |
| Focus visibility | Interactive elements should show a clear visible focus indicator and should not be obscured by sticky headers where practical. |
| Colour contrast | Text and controls should have sufficient contrast. Warnings should not rely only on colour. |
| Target size | Important links, buttons and controls should be large enough to activate comfortably, especially on mobile screens. |
| Forms | Labels should be programmatically associated with inputs. Required fields and hints should be visible and understandable. |
| Link text | Links should explain their destination or action. Repeated “click here” wording should be avoided. |
| Images | Decorative images should have empty alt text where appropriate. Meaningful images should have descriptive alt text. |
| Mobile and zoom | Layouts should work on small screens and avoid fixed-width content that causes horizontal scrolling. |
| Plain language | Content should explain legal routes in direct language and avoid unnecessary jargon. |
| Error handling | Form errors should clearly explain what needs fixing and should not rely only on colour or vague warnings. |
| Consistent help | Help routes, contact information and urgent advice warnings should be consistently available on key support pages. |
10. Testing method
Accessibility testing is currently a mix of editorial, technical and manual checks. The site has not yet had a full independent WCAG audit, so testing is being improved over time.
- keyboard-only tab and shift-tab checks on priority pages;
- visible focus checks for links, buttons, forms, menus and details panels;
- mobile layout checks at narrow viewport widths;
- zoom and reflow checks where layout problems are likely;
- heading order and landmark review;
- form label, hint and required-field review;
- contrast checks on text, buttons and warning panels;
- spot checks of screen reader readability where available;
- review of dynamic cards and JavaScript-generated content;
- review of table readability on smaller screens.
11. What we are doing next
Accessibility improvements are prioritised according to user impact, especially where an issue affects urgent housing content, forms, checkers or evidence tools.
- continue reviewing older page templates for class conflicts and heading consistency;
- improve screen reader testing for long checkers and dynamic results;
- review the mega menu and mobile navigation with keyboard and assistive technology;
- improve fallback content where dynamic cards depend on JavaScript;
- review large tables in posts and tools for small-screen readability;
- check that warning boxes and result cards do not rely only on colour;
- test contact and feedback forms for clearer error handling;
- add further notes if third-party tools or embeds create access barriers.
12. Report an accessibility problem
If you find an accessibility problem, contact us so we can review it. The more specific your report is, the easier it is to reproduce and fix.
Email: contact@rentersrightstoolkit.co.uk
You can also use the contact page.
Helpful details to include
- the page URL;
- the tool, form or section name;
- what you were trying to do;
- what went wrong;
- your device and browser;
- screen reader, magnifier, speech recognition or other assistive technology used;
- whether the issue blocks access or makes the page difficult to use;
- a screenshot if useful, but only if it does not show private or sensitive information.
13. How we handle accessibility reports
We review accessibility reports alongside editorial corrections and technical issues. We prioritise problems that prevent users from accessing core renting information, contact forms, urgent warnings, checkers or evidence tools.
Where possible, we aim to review accessibility reports within 10 working days. Complex issues, third-party problems or larger tool changes may take longer to investigate and fix.
Not an advice route:
Accessibility contact is for website access problems. It is not legal advice, court advice, homelessness advice or emergency support.
14. If you are not happy with our response
Contact us first so we can understand the problem and try to fix it. If the issue relates to disability access to a service and you need wider equality support, the Equality Advisory and Support Service may be able to provide information about equality and human rights issues in England, Scotland and Wales.
If your concern is about how personal data has been handled, read our Privacy Policy and contact us using the privacy contact route. For data protection complaints, the UK Information Commissioner’s Office may be the relevant authority.
This website is not a public authority, so public-sector accessibility enforcement routes may not apply in the same way. We still use recognised accessibility standards because they are good practice and reduce barriers.
15. Third-party services and external links
Some parts of the website may rely on third-party services, such as form handling, analytics, hosting, external images, scripts or linked official sources. These services may have their own accessibility features and limitations.
External links are provided to help users verify information or find advice. We cannot control the accessibility, availability or design of external websites.
If a third-party feature blocks access to core site content, report the issue and we will consider a workaround or replacement where practical.
16. If you need information in another format
We cannot guarantee every format request, but you can contact us if a page is difficult to use in its current form.
Simpler wording
Tell us which page or section is difficult. We may be able to improve the wording or add a clearer summary.
Tool or form problem
Report if a checker, contact form, menu, FAQ dropdown or result panel is difficult to use with your setup.
Urgent housing need
If you need urgent housing advice, use Shelter, Citizens Advice, your council, a law centre or a solicitor instead of waiting for website changes.
17. Relationship with legal and housing advice
Accessibility helps people use the website, but it does not change the legal status of the content. Renters Rights Toolkit provides general information, not legal advice or regulated legal services.
If your housing issue is urgent, disputed or high-risk, use the toolkit as a starting point only and get advice from a qualified housing adviser, solicitor, Shelter, Citizens Advice, council homelessness team, court duty adviser or another appropriate support route.
This is especially important for court papers, possession hearings, bailiff notices, serious disrepair, harassment, illegal eviction, homelessness risk, discrimination, tribunal deadlines, deposit disputes or threats to your safety.
18. Official accessibility and support sources
These sources support the accessibility approach used on this page.
W3C: Web Content Accessibility Guidelines 2.2
International accessibility standard for making web content more accessible.
W3C WAI: WCAG overview
Explains WCAG principles, guidelines, success criteria and conformance levels.
GOV.UK Service Manual: Understanding WCAG 2.2
Government service guidance explaining WCAG 2.2 Level AA and accessibility principles.
GOV.UK: Accessibility requirements
Official guidance explaining accessibility requirements and reasonable adjustments context.
GOV.UK: Equality Advisory and Support Service
Information about the EASS, which provides information about discrimination and rights.
Equality Advisory and Support Service
Support route for equality and human rights issues in England, Scotland and Wales.
GOV.UK: Private renting
Official private renting guidance for users who need source verification.
Shelter England: Private renting advice
Specialist housing advice for users who need practical support beyond this website.
Help us improve access
Report any barrier that stops you reading a guide, using a tool, completing a form, opening a menu, reading a table or understanding an important warning.
Accessibility FAQs
Quick answers about using and reporting accessibility issues on the website.
What accessibility standard does the website aim to follow?
Renters Rights Toolkit aims to follow WCAG 2.2 Level AA where practical for pages, tools, forms, navigation and templates. The website has not yet had a full independent WCAG audit.
Is the website fully WCAG compliant?
Not yet. The site is best described as partially conformant with WCAG 2.2 Level AA as a practical benchmark because some custom tools, dynamic areas and older page components still need further testing.
Can I report an accessibility problem?
Yes. Email contact@rentersrightstoolkit.co.uk or use the contact page. Include the page URL, device, browser, assistive technology used and what went wrong.
Does the website work without a mouse?
The site is designed so links, buttons, details panels and form controls should be reachable by keyboard. If a part is not usable by keyboard, report it.
Can I use browser zoom?
The layout is designed to be responsive and work on smaller screens. If any page creates unreadable or overlapping content at zoom, report the page URL.
What if a tool is hard to use with a screen reader?
Report the tool name, page URL, what happened and the screen reader/browser combination. Tool accessibility issues that block core information are treated as high priority.
Can you provide legal advice for disabled renters?
No. The site provides general information and website accessibility support. Disabled renters with legal, housing or discrimination issues should contact a qualified adviser, solicitor, council, Shelter or Citizens Advice.
Do images contain important information?
Important warnings and guidance should be available as text. Decorative images should not be required to understand the page.
How often is accessibility reviewed?
Accessibility is reviewed as pages and tools are updated. High-risk pages, contact forms and core tools are prioritised for fixes.
What if I am not happy with the response?
Contact us first so we can try to fix the issue. If the matter involves wider equality or disability rights, you may consider the Equality Advisory and Support Service. For data protection concerns, the Information Commissioner’s Office may be relevant.