- Home
- Accessibility Statement
Accessibility Statement
Accessibility statement for Anchor
This accessibility statement applies to the public pages on www.anchor.org.uk.
This website is run by Anchor. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- Change colours, contrast levels and fonts.
- Adapt the font size or zoom settings to read the content.
- Navigate most of the website using a keyboard.
- Navigate most of the website using speech recognition software.
- Listen to most of the website using a screen reader.
- View the content on a range of devices.
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible this website is
We know some parts of this website are not fully accessible:
- Some page elements including links, buttons and text inputs have poor colour contrast. You can apply custom stylesheets and ease of access adaptations to override these styles.
- Some content is hidden to assistive technologies but receives keyboard focus. The hidden carousel slides contain links that will not be announced to screen readers even when they receive focus. Toggling/swiping onto the active/visible state will allow the content to be announced.
- The navigation menus become cut off with increased font sizing or zoom adaptations. You can use the search or follow the page content links to navigate and explore the website.
- Videos do not have captions and text alternatives, but key content is available in surrounding content.
- Many PDF documents including property brochures are not tagged and may not be read correctly by screen readers. Key information about our properties can be found in the HTML page content.
Feedback and contact information
If you need information on this website in a different format, please contact us:
- email us at [email protected]
We’ll consider your request and aim to respond to your query within 48 hours, Monday to Friday.
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact us by emailing [email protected].
Enforcement procedure
The 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).
Technical information about this website’s accessibility
Anchor is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons. The items below will be addressed in the coming 25/26 financial year and as part of a planned site migration.
Non-compliance with the accessibility regulations
Not all content is accessible with only a keyboard. This fails 2.1.1 Keyboard (Level A).
Modal content doesn't receive keyboard focus in a logical order. This fails 2.4.3 Focus Order (Level A) and 4.1.2 Name, Role, Value (Level A).
Some expanding content regions are difficult to perceive and navigate with keyboard and screen readers as focus order isn't logical. This fails 1.3.1 Info and Relationships (Level A), 4.1.2 Name, Role, Value (Level A) and 2.4.3 Focus Order (Level A).
Components with ARIA properties, roles and states are not always implemented according to specification. This fails 1.3.1 Info and Relationships (Level A) and 4.1.2 Name, Role, Value (Level A).
Scripted form components don't support all native keyboard interactions or screen reader commands. This fails 1.3.1 Info and Relationships (Level A), 1.3.2 Meaningful Sequence (Level A), 2.4.3 Focus Order (Level A) and 4.1.2 Name, Role, Value (Level A).
Some content regions are hidden to assistive technologies with aria-hidden but still receive keyboard focus. This fails 4.1.2 Name, Role, Value (Level A) and 2.1.1 Keyboard (Level A).
Status messages are not announced to screen readers. This fails 4.1.3 Status Messages (Level AA).
Some brand colour combinations do not meet colour contrast requirements. This fails 1.4.3 Contrast (Minimum) (Level AA) and 1.4.11 Non-text Contrast (Level AA).
Most focusable elements do not have a keyboard focus visible style. This fails 2.4.7 Focus Visible (Level AA).
The navigation menus are partially cut off with text resize and zoom adaptations. This fails 1.4.4 Resize text (Level AA) and 1.4.10 Reflow (Level AA).
Some Error messages aren’t available in text or announced to screen readers. This fails 3.3.1 Error Identification (Level A) and 3.3.2 Labels or Instructions (Level A).
Search buttons submit when they receive keyboard focus. This affects forms where suggestions are displayed. This fails 3.2.1 On Focus (Level A).
Screen reader users are not made aware of the dynamic loading search suggestions. This fails 1.3.1 Info and Relationships (Level A) and 4.1.2 Name, Role, Value (Level A).
Form labels that are visually hidden may not always match the visible placeholder text. This fails 2.5.3 Label in Name (Level A).
Some required fields are not communicated to users in text. This fails 2.4.6 Headings and Labels (Level AA) and 3.3.2 Labels or Instructions (Level A).
Some form inputs gathering data about the user do not use autocomplete attributes. This fails 1.3.5 Identify Input Purpose (Level AA).
Some form elements have missing or incorrectly associated labels. This fails 1.3.1 Info and Relationships (Level A) and 3.3.2 Labels or Instructions (Level A).
Some form elements have the same ID value and are associated with more than one form label. This fails 1.3.1 Info and Relationships (Level A) and 4.1.1 Parsing (Level A).
Some radio button and checkbox form components are not grouped and labelled. This fails 1.3.1 Info and Relationships (Level A), 2.4.6 Headings and Labels (Level AA) and 3.3.2 Labels or Instructions (Level A).
Not all landmark regions are labelled and skip links to main content are not provided. This fails 2.4.1 Bypass Blocks (Level A).
Some content elements are not coded with semantic or appropriate HTML. This fails 1.3.1 Info and Relationships (Level A).
Video content doesn’t have equivalent text alternatives. This fails 1.2.2 Captions (Prerecorded) (Level A), 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) and1.2.5 Audio Description (Prerecorded) (Level AA).
Some content images and infographics have missing or inappropriate text alternatives. This fails 1.1.1 Non-text Content (Level A).
Floating bookmark links don't focus onto the link target when operated with a keyboard. This fails 2.4.3 Focus Order (Level A) and 2.1.1 Keyboard (Level A).
Some content links do not contain meaningful link text. This fails 2.4.4 Link Purpose (In Context) (Level A).
Some buttons do not have descriptive labels. This fails 1.3.1 Info and Relationships (Level A) and 2.4.6 Headings and Labels (Level AA).
Some buttons are coded as links. This fails 1.3.1 Info and Relationships (Level A).
Some frames do not have a title. This fails 2.4.1 Bypass Blocks (Level A).
Some PDF documents are not tagged or not tagged correctly. Some PDFs do not have bookmarks, headings and page titles. This fails 1.3.1 Info and Relationships (Level A), 2.4.2 Page Titled (Level A), 2.4.5 Multiple Ways (Level AA) and 2.4.6 Headings and Labels (Level AA).
Navigation and footer items:
Text contrast (WCAG 2.1 AA 1.4.3)
Forn control contrast (WCAG 2.1 AA 1.4.11)
Programmatic field purpose (WCAG 2.0 A 2.4.4)
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
What we're doing to improve accessibility
A budget request has been made specifically for accessibility improvements in the 25/26 financial year. In addition, we are in the process of migrating the website’s database, which will enable more significant changes to the design and layout of pages with a view to improving accessibility. There is a planned site-wide migration scheduled to begin in late 2025 which will enable greater compliance with Web Content Accessibility Guidelines version 2.2 AA standards. In addition, we are assessing third-party accessibility plug-ins which will further support users of assistive technology and neurodiverse users.
Preparation of this accessibility statement
This statement was prepared on 29/10/2024. It was last reviewed on 29/10/2024.
This website was last tested on [18/10/2024] against the WCAG 2.2 AA standard.
The test was carried out by MadeByPi. Automated and manual testing across a range of mobile and desktop experiences of representative page types, the main navigation and footer was conducted.
Related information
-
![Resident communication options]()
Resident communication options
Find out about the different options we have available to help make it easier for residents to access communications from us and how to let Anchor know your communication preference.
-
![Anchor feed image]()
Anchor's Privacy Policies and Notices
Information about Anchor's privacy policies for residents, employees, visitors to our locations and visitors to our website.
This website uses cookies which track activity so that you get the best possible experience. By continuing to use this website we will assume you are happy and cookies will be set. You can change your cookie settings at any time.