Accessibility statementThis website is run by Citizens Advice. We want as many people as possible to be able to use this website. You should be able to:
How accessible this website isWe know parts of this website aren’t fully accessible, for example:
Feedback and contact informationEnforcement procedureThe Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).Contacting us by phone or visiting us in personWe provide a textphone service for people who can’t hear or speak on the phone. You can find out more about textphone on the Relay UK website. You can check if we can arrange a British Sign Language (BSL) interpreter before your visit. Technical information about this website’s accessibilityCitizens Advice is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. Compliance statusThis website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below. Non-accessible contentThe content listed in this section is non-accessible for the following reasons. Non-compliance with the accessibility regulationsColourWe fail guideline ‘1.4 Distinguishable’ of the WCAG 2.1 AA standard because:
We’re redesigning our website and will be utilizing these in the new design FormsWe fail guidelines ‘1.3 Adaptable’, ‘2.1 Keyboard accessible’, ‘2.4 Navigable’ and ‘3.3 Input assistance’ of the WCAG 2.1 AA standards because:
In 2022, we’ll start to review how all forms and interactive elements are implemented. We’re redesigning our website and will start to use these designs in early 2022 NavigationWe fail guideline ‘1.4 Distinguishable’ of the WCAG 2.1 AA standards because:
We’ll use new navigation by mid 2022 Keyboard accessWe fail guidelines ‘2.1 Keyboard accessible’ and ‘2.4 Navigable’ of the WCAG 2.1 AA standards because:
We’ll make the navigation and buttons accessible by mid 2022 1. Accessibility checks for all development releasesWe’ll check all new content, designs and development meets accessibility standards. 2. Regular quality assurance (QA) testing with an accessibility focusAs we design, build and update the site, we will regularly do audits and QA testing to make sure we don’t add new barriers. 3. Including disabled people and people with long term health conditions in every round of researchDuring the early stages of development, we’ll make sure people with access needs are included in the research. We’ll run usability testing with advisers and volunteers who work for Citizens Advice and we’ll use our Disability Network Group to recruit participants. When we recruit external participants for usability testing, we’ll make sure people with access needs are included in this. |