Accessibility statement for the search for planning applications website
This accessibility statement applies to: planning.walsall.gov.uk/swift/apas/run/wchvarylogin.display
This website is run by APAS. 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 using browser or device settings
- zoom in up to 400% without the text spilling off the screen
- navigate most of the website using a keyboard or speech recognition software
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand. 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 custom controls do not have their roles, names, or states properly defined
- the focus order is not always logical
- some of the keyboard focus indicators may not have suitable contrast
- some buttons and links are too small to select
- some content does not have sufficient colour contrast
- colour is used solely to visual displaying content
- some links have been written out of context
- you cannot skip over repeated content
- page titles not reflecting content
- the language of some pages has not been identified
- when using browser zoom, some content may not display as expected
- some input fields do not have autocomplete options
- users cannot navigate to certain pages through multiple ways
- some users may have to rely of sensory cues
Feedback and contact information
Tell us if you need information on this website in a different format. In your message, include:
- the web address (URL) of the content
- your name and email address
- the format you need (for example, BSL, large print, accessible PDF, audio recording, easy read or braille)
We'll consider your request and get back to you as soon as possible.
Reporting accessibility problems with this website
We're always looking to improve the accessibility of this website. We are working on our content and will continue to make this more readable. All of our pages let you provide feedback to us and we encourage you to tell us what you think.
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, let us know via:
- email webproject@walsall.gov.uk
- phone: +44 1922 650000
- visitor address: Walsall Council, The Civic Centre, Walsall, WS1 1TP
We will respond to feedback within 5 working days.
Enforcement procedure
If you contact us with a complaint and you’re not happy with how we respond, contact the Equality Advisory and Support Service (EASS).
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’).
Technical information about this website's accessibility
Walsall Council 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 listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons:
- Non-compliance with the accessibility regulations
Webpages
- On some pages instructions rely on sensory characteristics. This fails WCAG 2.2 success criterion 1.3.3 Sensory characteristics. We plan to amend this by November 2025.
- Some form field inputs do not have an auto-complete feature. This makes it harder for users to fill out the field, especially for users with cognitive impairments. This fails WCAG 2.2 success criterion 1.3.5 Identify Input Purpose. We plan to amend this by November 2025.
- Some instructions use colour as the only visual means of conveying information. This fails WCAG 2.2 success criterion 1.4.1 (Use of colour) We plan to amend this by November 2025.
- Some parts of the website do not have sufficient contrast between the text and background colours. This fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum). We plan to amend this by November 2025.
- Some content does not reflow when viewed at high browser magnification, which means people with visual impairments may be unable to access some content. This fails WCAG 2.2 success criterion 1.4.10 Reflow. We plan to amend this by November 2025.
- There is no “Skip to Content link” present. This may affect blind users or have low vision. This fails WCAG 2.2 success criterion 2.4.1 Bypass Blocks. We plan to amend this by November 2025.
- Some pages do not have a unique page title. The page title should describe the topic of the page, purpose of the page or the subject of the page. This doesn’t meet WCAG 2.2 success criterion 2.4.2 Page titled. We plan to amend this by November 2025.
- Some of the purpose/destination of a link cannot be determined from the link text. This fails WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context). We plan to amend this by November 2025.
- Some pages cannot be found through more than one type of navigation. This fails WCAG 2.2 success criterion 2.4.5 Multiple ways We plan to amend this by November 2025.
- Some elements on the page keyboard focus is unclear. This would affect users with low vision and cognitive impairments. This doesn’t meet WCAG 2.2 Success criterion 2.4.7 Focus visible. We plan to amend this by November 2025.
- Some of the targets that can be chosen are too small for the minimum target size requirements. Some people with physical impairments cannot click small buttons that are close together. This fails WCAG 2.2 success criterion 2.5.8 Target size. We plan to amend this by November 2025.
- The Language of the Page is not detectable on some pages. This would make it difficult for screen reader users to access the content. This does not meet WCAG 2.2 success criterion 3.1.1 Language of the page We plan to amend this by November 2025.
- Some pages have different navigation from others. This would affect users with cognitive or visual disabilities. This fails WCAG 2.2 success criterion 3.2.3 Consistent navigation. We plan to amend this by November 2025.
- Some forms controls do not have correct labels. This fails WCAG 2.2 success criterion 4.1.2 Name role and value. We plan to amend this by November 2025.
PDF documents
Some of our PDFs are not formatted so they’re accessible to a screen reader. Some errors may include, missing:
- Non-text content. All non-text content presented to the user should have a text alternative that serves the equivalent purpose. If these are missing this doesn’t meet WCAG 2.2 success criterion 1.1.1 Non text content
- Colour contrast. Some parts of PDF’s do not have sufficient contrast between the text and background colours. This doesn’t meet WCAG 2.2 success criterion 1.4.3 Contrast minimum
- Page titles. PDF documents should have titles that describe the topic or purpose of the page. If these are missing this doesn't meet WCAG success criteria 2.4.2. Page Titled
- Headings and labels. Headings and labels describe topic or purpose. If these are missing this doesn't meet WCAG 2.2 success criteria 2.4.6 Headings and Labels
- Name, role, value. For all user interface components, some of which are essential to providing our services (for example, forms published as Word documents). If these are missing this doesn’t meet WCAG 2.2 success criterion 4.1.2 Name, role, value
What we’re doing to improve accessibility
We are in the process of launching a redesigned website, planned for early 2025, with the goal of making it fully compliant with WCAG 2.2 guidelines.
Preparation of this accessibility statement
This statement was prepared on 3 October 2024. It was last reviewed on 3 October 2024.
This website was last tested on 13 March 2024. The test was carried out by the accessibility team in Walsall Council. The tests included:
- a mixture of simple manual checks and automated tests to find only the most common barriers to users with accessibility needs
- manual checks using each page without a mouse, viewing the page at different zoom settings, and simulating viewing the page on a small screen
The automated tests were completed using the latest version of Axe and WAVE.
Tests were completed using different settings in the Internet Explorer browser on Lenovo ThinkPad with a 13-inch screen.
