For local authorities, website accessibility is about much more than meeting a technical standard. Council websites support a wide range of users, from residents and businesses to community groups, professionals, visitors and partner organisations, all accessing information and services for different reasons.
If accessibility barriers prevent someone from finding information, completing a form, making a payment or using an online service, they may have no convenient alternative. That is why web accessibility for local authorities must be considered throughout planning, design, development, content creation and ongoing website maintenance.
In this guide, we look at the Web Content Accessibility Guidelines (WCAG), common accessibility issues on public sector websites, how these affect real users and how local authorities can build, test and maintain more accessible digital services.
At britweb, accessibility forms part of our web design and development process. Explore our web accessibility services, and if you need support improving your current website or planning an accessible website rebuild, please contact us.
What are WAI and WCAG?
What is WAI?
WAI, or the Web Accessibility Initiative, is an initiative from the World Wide Web Consortium (W3C) that develops standards, guidance and resources to help make web technologies more accessible.
What is WCAG?
WCAG, or the Web Content Accessibility Guidelines, is one of the key accessibility standards providing guidance on how to make websites and digital content more accessible.
It covers areas such as how content is presented, how users navigate a website and how content works with assistive technology.
WCAG is built around four core principles:
- Perceivable
- Operable
- Understandable
- Robust
Together, these are often shortened to POUR.
For a broader introduction to the principles behind accessible websites, see our guide to what web accessibility is and why it matters.
Which WCAG standard applies to local authorities?
UK local authority websites that are in scope of the accessibility regulations need to meet WCAG 2.2 Level AA. Level AA means meeting both the basic Level A requirements and the additional Level AA accessibility criteria.
Local authorities must also publish an accessibility statement explaining how accessible the website is and identifying any known accessibility issues.
Why web accessibility matters for local authorities
Good digital accessibility helps people access online services regardless of how they interact with a website.
This can include people with:
- Visual or hearing impairments
- Physical or motor impairments
- Learning disabilities or cognitive impairments
- Temporary impairments or disabilities
Some users may also rely on assistive technology, such as screen readers, screen magnifiers, speech recognition software or alternative input devices.
Accessibility is particularly important within the public sector because people often need to use specific websites and digital services to access information or complete essential tasks. If those services are inaccessible, there may be no straightforward alternative.
What are the most common accessibility problems on local authority websites?
Council websites can include thousands of web pages, forms, documents and third-party systems, so even small accessibility issues can have a wide impact.
Poor colour contrast
Poor colour contrast can make text, buttons and other interface elements difficult to distinguish, particularly for people with impaired vision. Sufficient contrast between text, backgrounds and interactive elements helps make content easier to read and controls easier to identify.
Inaccessible forms
Forms are central to many council services. Common issues include missing labels, unclear instructions and error messages that screen readers do not announce. If users cannot understand what information is required or what has gone wrong, they may be unable to complete the process.
Keyboard navigation problems
Some people use a keyboard instead of a mouse to move around a website and interact with content. Menus, links, buttons and form fields should all be accessible by keyboard. Users should also be able to clearly see which element is currently selected as they move through the page.
Missing or unsuitable alternative text
Alternative text, or alt text, is a short written description that explains an image’s purpose or meaning to people who may not be able to see it. Missing, unclear or unsuitable alt text can make important visual information harder to understand for people using assistive technology.
Unclear headings and link text
Clear headings help people understand how a page is organised and make longer content easier to scan. They are also useful for screen reader users, who may use headings to move quickly between sections.
Link text should clearly indicate where a link leads or what action it will take. Vague wording such as ‘click here’ can make navigation less clear.
Inaccessible PDFs and documents
Local authorities often publish reports, policies, meeting papers and application forms. Inaccessible PDF forms, scanned documents and poorly structured PDFs can make important information difficult or impossible to access. Where practical, publishing the information as an accessible web page may provide a better experience than relying on downloadable documents.
Poor mobile and zoom accessibility
Content should remain usable when someone zooms in, enlarges text or views the website on a smaller screen. Overlapping content, excessive horizontal scrolling and controls disappearing from view can all create accessibility barriers.
Videos without accessible features
Council meetings, consultations and other videos should be made accessible to people who may not be able to hear or see all of the content. Depending on the video, this may include captions, transcripts, audio descriptions or other accessible alternatives.
Accessibility issues with third-party systems
Local authority websites often rely on external systems such as payment platforms, booking tools, planning portals, maps and online forms. These systems can affect the accessibility of the overall user experience, so accessibility should be considered when choosing and managing them.
For more practical examples of issues to look out for, see our top web accessibility tips.
How accessibility barriers affect people using council services
Accessibility issues can make everyday online tasks more difficult or, in some cases, prevent people from completing them altogether.
For example, a user may be unable to submit a form using a keyboard, understand an error message with a screen reader or access information in an unsuitable PDF. Poor zoom behaviour or unclear navigation can also make it harder to find and use important services.
These barriers can lead to:
- Users abandoning online forms or processes
- More calls and offline enquiries
- People needing additional help to access services
- Accessibility complaints or negative feedback
- Reduced trust in the organisation and its digital services
- Potential accessibility compliance issues
For local authorities, accessibility is therefore not just a technical requirement – it can affect the user experience, demand on other service channels and the organisation’s wider reputation.
How to build accessibility into a local authority website
Accessibility is easier to achieve when it is considered throughout the website project, rather than added later in the process.
Include accessibility during discovery and planning
Start by identifying who needs to use the website, user journeys and any potential accessibility barriers. Include accessibility requirements in project briefs, procurement, and discussions with third-party suppliers from the outset.
Make accessibility part of the design
Accessible design should consider:
- Clear colour contrast
- Readable typography
- Logical page layouts
- Visible keyboard focus
- Consistent navigation
- Responsive design
Our web design and development services consider usability, accessibility and visual design together from the outset.
Build accessible functionality
Accessibility also needs to be considered during development. This includes using well-structured HTML, correctly labelled forms, logical headings and interactive elements that can be operated using a keyboard.
Testing throughout development can also help identify problems earlier, when they are often easier to address.
Create accessible content
Content can introduce accessibility barriers even when the website itself has been developed correctly. Use clear headings, meaningful link text, suitable alt text and accessible documents. Giving content editors appropriate guidance or training can help maintain these standards after launch.
Check third-party systems
Payment platforms, booking systems, forms and other integrations should be assessed for accessibility before they are introduced. When selecting suppliers, it can be useful to understand how their systems meet relevant accessibility standards and what accessibility testing has been carried out.
Choose an experienced web development agency
Working with a web development agency that understands web accessibility, relevant WCAG requirements and the needs of public sector websites can help make accessibility part of the project from planning through to design, development and launch.
How should local authorities test and maintain website accessibility?
Accessibility testing should take place throughout development, before launch and once the website is live. A combination of automated checks, manual testing and testing with assistive technology can help identify different types of accessibility issues.
Accessibility can also change over time as new content, documents, plugins and functionality are introduced. Regular monitoring, testing after significant updates and ongoing guidance for content editors can help maintain accessibility as the website evolves.
For an example of accessibility in practice, see our The Capitol Horsham case study.
Summary: building accessible local authority websites
For local authorities, good web accessibility means reducing barriers that can make it harder for people to find information, complete forms or use online services.
Building accessibility into planning, design, development, content and third-party systems helps prevent common accessibility issues from the start, while regular testing and maintenance help keep public sector websites accessible, usable and aligned with WCAG 2.2 AA.
Build an accessible local authority website with britweb
Whether you’re planning a new local authority website or looking to improve the accessibility of your current site, britweb can help.
We build accessible websites around real users, clear journeys and relevant WCAG requirements, while also helping organisations identify and address accessibility issues. Contact us to discuss your project.
Frequently Asked Questions
What are the accessibility regulations for public sector websites?
The Public Sector Bodies Accessibility Regulations 2018 set accessibility requirements for in-scope public sector websites and mobile apps. They sit alongside wider legal duties to protect disabled people from discrimination.
What WCAG standard do local authority websites need to meet?
For UK public sector bodies in scope of the accessibility regulations, websites and relevant mobile apps need to meet WCAG 2.2 AA, subject to applicable exemptions and other provisions. They must also publish an accessibility statement.
How often should a local authority website be tested for accessibility?
Accessibility should be tested throughout design and development, before launch, following significant changes and periodically after launch. Regular checks help identify new issues introduced through content, functionality or third-party systems.
