Building an accessible school website in 2026 is not just about ticking boxes on a compliance checklist. It is about ensuring that every pupil, parent, and staff member can find the information they need, regardless of how they interact with your site. For UK schools, accessibility is a legal duty under the Equality Act 2010 and the Public Sector Bodies Accessibility Regulations 2018 (PSBAR). This guide explains the practical steps your school can take to create a website that serves everyone, while staying on the right side of the law.
Why accessibility matters for UK Schools
Schools have a moral and legal responsibility to make their digital content accessible. The Equality Act 2010 places a duty on schools not to discriminate against disabled individuals, and this extends to the school’s digital presence. The PSBAR 2018 requires public sector websites to meet accessibility standards, with WCAG 2.2 AA as the benchmark for compliance.
Many primary and secondary schools in England, Scotland, Wales, and Northern Ireland are partially exempt from full compliance, but this is not a blanket opt-out. Essential content – such as online forms for school meal preferences, admissions applications, and contact details – must still meet WCAG AA standards. Schools can claim a “disproportionate burden” exemption, but they must formally assess and document that decision. In other words, partial exemption requires justification, not assumption.
Failure to comply can invite scrutiny from the Equality and Human Rights Commission (EHRC) and the Government Digital Service (GDS). It also creates reputational risk during Ofsted inspections. Building an accessible school website is the safest and most inclusive path forward.
Key principles of accessible school website design
1. Understand WCAG 2.2 AA requirements
WCAG 2.2 AA is the current standard referred to in UK guidance. The guidelines are organised around four principles: perceivable, operable, understandable, and robust. For a school website, this means ensuring text can be resized, navigation works by keyboard, content is easy to read, and the site works with assistive technologies such as screen readers.
You do not need to become a technical expert. The important thing is to work with a web design partner who understands these criteria. A reputable provider will build your site to meet WCAG 2.2 AA from the start, rather than trying to retrofit compliance later.
2. Use clear and readable typography
A minimum body text size of 16px is recommended for readability on school websites. Avoid using very light font colours on white backgrounds, and keep line spacing generous. The goal is to reduce visual strain for all users, including parents reading on mobile devices and students with visual impairments.
Do not rely on custom fonts that are hard to decode. Stick to standard sans-serif or serif typefaces that come with the operating system. If you use a specialist font, ensure it passes the WCAG contrast requirements.
3. Add descriptive alt text to images
Every image that conveys information must have descriptive alternative text. This allows screen reader users to understand what the image shows. The alt text should be concise but meaningful – for example, “Year 6 pupils planting sunflower seeds in the school garden” rather than just “image” or “gardening”.
Essential information must never be conveyed through images alone. If you use an infographic to explain the school admissions process, the same information should be available as text on the page. Similarly, PDFs of school policies should be made accessible, or a text version provided.
4. Keep navigation consistent and predictable
All pages should follow the same navigation structure. A consistent menu, logical heading hierarchy (h1, h2, h3), and clear link labels help users move around the site quickly. Provide a site search function, and ensure that interactive elements – such as menus and forms – can be operated using a keyboard alone.
When users arrive on your site looking for term dates, lunch menus, or Ofsted reports, they should find those items within two or three clicks. Unnecessary complexity frustrates everyone, especially parents who may be using assistive technology.
Compliance checklist for 2026 – How to achieve an accessible school website
Here is a practical summary of what your school website needs to include to meet the PSBAR requirements in 2026.
| Requirement | What to do |
|---|---|
| Accessibility statement | Publish a statement on your website explaining your commitment to accessibility, which parts of the site are not yet fully accessible, and how users can contact you to report problems. This is mandatory for all state-funded schools. |
| WCAG 2.2 AA standard | Ensure all essential content and interactive features meet the success criteria. This includes forms, payment pages, and core information about the school. |
| Keyboard navigation | Users must be able to tab through all menus, links, and forms without a mouse. |
| Colour contrast | Text must have sufficient contrast against its background. Use a contrast checker tool to verify ratios. |
| Resizable text | Users must be able to increase text size up to 200% without losing content or function. |
| Descriptive link text | Do not use “click here” or “read more”. Links should clearly describe their destination, e.g. “Term dates 2025-26”. |
Tools and quick wins for an accessible school website
If you are looking for a simple starting point, consider adding an accessibility widget to your existing site. UserWay, for example, offers a free widget that can be installed on school websites. It provides users with options to change font size, adjust contrast, and switch to a screen-reader friendly view.
However, a widget alone does not make a site fully compliant. It is a helpful tool for users, but the underlying content – text, images, navigation, and forms – must still meet WCAG 2.2 AA standards. Think of the widget as a supplement, not a substitute, for proper accessible design.
For schools that want more bespoke control, some agencies offer websites where the school owns the intellectual property and has no long-term contract. This can be beneficial if you plan to change providers or manage the site internally later.
Accessibility is an ongoing process
Accessibility is not a one-time project. It requires regular audits and monitoring to ensure that new content – such as updated policies, event pages, and newsletters – continues to meet the standards. Every time a staff member uploads a PDF or adds an image without alt text, the website’s accessibility slips.
Schools should assign someone to be responsible for digital accessibility, even if that role is shared across the office team. Provide training on writing accessible content, using heading structures, and checking contrast. Many user guides are freely available from organisations such as the government’s GDS team and accessibility charities.
If your school already has a website, the first step is to run an audit using free tools like the WAVE Web Accessibility Evaluation Tool or the axe browser extension. Identify the most critical issues – lack of alt text, poor colour contrast, inaccessible forms – and fix them in order of priority. Document your progress in your accessibility statement, and update it at least once a year.
Building an accessible school website in 2026 is achievable for every school, regardless of budget or technical experience. The key is to start with a clear understanding of the regulations, partner with a design team that values accessibility, and commit to continuous improvement. Your pupils, parents, and community deserve a website that works for everyone.
Frequently Asked Questions
Are UK schools completely exempt from the accessibility regulations?
No. UK primary and secondary schools are partially exempt from the Public Sector Bodies Accessibility Regulations 2018, but essential content such as forms for school meal preferences must still meet WCAG AA standards. Schools must also publish an accessibility statement. Exemptions must be formally justified as a “disproportionate burden”.
What WCAG version should school websites follow?
The current benchmark for school website compliance is WCAG 2.2 AA. This is the version referenced by leading guidance sources for UK schools. Your website should be designed and tested against these success criteria to meet the spirit of the PSBAR regulations.
Will a free accessibility widget make my school website compliant?
Not on its own. A tool such as UserWay offers helpful user-facing features like font resizing and contrast adjustments, but the underlying content – text, images, navigation, forms – must still meet WCAG 2.2 AA standards. The widget is a supplement, not a replacement for proper accessible design.
How often should we review our school’s accessibility?
Accessibility is an ongoing process. You should review your website at least once a year, and after every major content update. Regular monitoring using automated tools and manual checks helps ensure new content remains accessible and that your accessibility statement stays accurate.
What happens if our school website is not compliant?
Non-compliance can lead to formal action from the Equality and Human Rights Commission or the Government Digital Service. It also creates reputational risk during Ofsted inspections and could expose the school to legal challenges under the Equality Act 2010. Proactively addressing accessibility is the safest approach.