Digital Accessibility for School Websites: UK & EU Obligations 2026

What schools must do under the Equality Act and European Accessibility Act

UK public sector institutions — including state schools, further education colleges, and most universities — have been legally required to meet WCAG 2.1 Level AA since September 2018 under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. Since June 2025, the European Accessibility Act (EAA, Directive 2019/882) extended equivalent obligations to private sector providers — including independent schools, private universities, and international education groups operating within the EU.

The Equality Act 2010 has applied to all schools and independent higher education providers since its enactment: they must make "reasonable adjustments" to ensure disabled users are not placed at a substantial disadvantage. An inaccessible website is a prima facie failure of this duty, regardless of institutional size.

The business case is as direct as the legal one. According to Skolbot's mystery shopping audit (2025, 80 institutions), schools without an AI chatbot record an average bounce rate of 68%. An inaccessible website compounds this: approximately 15% of visitors with disabilities cannot navigate a non-compliant site effectively, abandoning before submitting an enquiry. At typical post-secondary conversion rates, that translates to dozens — sometimes hundreds — of lost applications per year.

The technical standard underpinning all of this is WCAG 2.1 AA, with WCAG 2.2 (published October 2023) now increasingly expected by regulators and cited in OfS monitoring frameworks. EN 301 549 is the European technical standard that formally references WCAG 2.1 and is what regulators use when auditing against the EAA.

The legal exposure for non-compliant institutions

The ICO can issue enforcement notices requiring an institution to bring its website into compliance within a specified timeframe; failure to comply can result in civil monetary penalties. Under the Equality Act 2010, a disabled prospective student who cannot access application information may bring a discrimination claim at an Employment Tribunal or County Court — compensation is uncapped, and reputational damage from a successful claim typically far exceeds any legal costs.

For institutions with EU-based students, campuses, or commercial operations, the EAA carries member-state-level sanctions that vary by jurisdiction but include significant fines — Ireland and Germany have both introduced penalties equivalent to 4–5% of annual turnover for persistent non-compliance. Institutions registered with the Quality Assurance Agency (QAA) or regulated by the Office for Students (OfS) face an additional risk: accessibility non-compliance can trigger conditions on registration or feature in regulatory correspondence.

UCAS-listed institutions in particular should note that accessibility failures increasingly appear in student satisfaction surveys and Discover Uni data, influencing prospective applicants' choices before they even reach your website.

The four WCAG principles — what they mean for a school website

WCAG 2.1 is organised around four principles, abbreviated as POUR: Perceivable, Operable, Understandable, and Robust. Each maps to concrete failures that appear repeatedly in higher education audits.

At Level AA, WCAG 2.1 adds requirements that are particularly relevant for schools: minimum colour contrast ratios (4.5:1 for standard text, 3:1 for large text), no loss of functionality on 400% zoom, and captions for all pre-recorded video. WCAG 2.2 adds nine new success criteria, including more stringent focus appearance requirements and a ban on dragging movements as the only means of interaction — both areas where existing school websites commonly fail.

Publishing your accessibility statement

Every public sector institution must publish an accessibility statement on its website. This is a legal document, not a PR exercise, and it must follow the format specified by the Cabinet Office. The GOV.UK template covers the mandatory elements: a list of known non-compliances, the reasons for any exemptions claimed, and a contact mechanism for users to report problems or request accessible alternatives.

The statement must be published on a dedicated page linked prominently from the footer of every page on the site. It should be updated whenever a new audit is conducted or a known issue is resolved. Statements that are out of date — listing issues already fixed, or omitting newly discovered ones — themselves constitute a compliance failure.

For private institutions subject to the EAA rather than the Public Sector Regulations, the requirement is functionally equivalent: a published, accurate declaration of conformance with EN 301 549, kept current, and accessible from every page.

Institutions that use third-party platforms — a common scenario in admissions, where UCAS Apply or bespoke application portals sit on separate domains — must assess those tools separately. If the portal is procured by the institution and presented to users as part of the application process, the institution bears responsibility for its accessibility under both the Equality Act and the EAA.

10 priority checks for your school's website

If your institution has not undergone a formal accessibility audit, these ten checks address the most frequently cited failures in the higher education sector.

1. Colour contrast — Test all text against its background using a tool such as WebAIM's Contrast Checker. Standard body text must achieve a ratio of at least 4.5:1; headings above 18pt require 3:1.
2. Image alt text — Every informative image must have a descriptive alt attribute. Decorative images should have an empty alt (alt="") so screen readers skip them.
3. Form labels — Each form field must have a programmatically associated <label> element. Placeholder text alone does not meet WCAG 2.1 Success Criterion 1.3.1.
4. Video captions — All pre-recorded video (Open Day recordings, programme teasers, testimonials) must have accurate captions. Auto-generated captions from YouTube or Teams require review and correction.
5. Keyboard navigation — Navigate your entire site using only the Tab, Enter, and arrow keys. Every interactive element must be reachable and operable without a mouse.
6. Skip navigation link — A "Skip to main content" link should appear as the first focusable element on every page, allowing keyboard and screen reader users to bypass repeated navigation.
7. PDF accessibility — Course brochures, prospectuses, and policy documents published as PDFs must be tagged, have a logical reading order, and include alt text for any images. Adobe Acrobat's accessibility checker is a reasonable starting point.
8. Focus indicators — The keyboard focus state must be clearly visible at all times. CSS that removes the default browser outline without providing a high-contrast replacement is a common, easily fixed failure.
9. Error identification — When a form is submitted with errors, each problem must be identified by name and described in text. Relying solely on colour to indicate an error fails WCAG 2.1 Success Criterion 1.4.1.
10. Responsive and zoom behaviour — At 400% zoom, all content and functionality must remain available without horizontal scrolling (except for data tables, which are exempt). Test on both desktop and mobile.

These checks are achievable without specialist tools. For a more thorough audit, institutions should engage an accessibility consultant certified to ISO 17065 or use a WCAG conformance evaluation methodology (WCAG-EM) that covers representative pages from each template type in use.

For further context on how data collected through accessible web forms must be handled, see the GDPR Guide for Student Data and Protecting Prospect Data Under GDPR. If your institution is also evaluating AI tools for admissions, EU AI Act and Higher Education covers the risk classification obligations that apply to automated chatbots and screening systems.

FAQ

Are private schools and independent universities covered by these regulations?

Yes. Private schools and independent universities have been subject to the Equality Act 2010 since its enactment, which requires reasonable adjustments for disabled users — an inaccessible website can constitute a failure of this duty. Since June 2025, the European Accessibility Act has extended explicit digital accessibility obligations to private sector providers, including independent higher education institutions operating in or serving users from EU member states. Private institutions are not required to publish an accessibility statement under the Public Sector Regulations, but EAA compliance documentation serves an equivalent purpose and is strongly recommended.

What is an accessibility statement and where should it appear?

An accessibility statement is a published page on your website that lists the known accessibility issues on the site, explains what users can do if they encounter a problem, and names a contact for accessibility-related requests. It must use the Cabinet Office template for UK public sector institutions and must be linked from the footer of every page. It should be reviewed and updated whenever your site changes significantly or a new audit is completed. A statement that lists no issues is almost always inaccurate and may itself attract regulatory scrutiny.

Does WCAG apply to third-party tools like our admissions portal?

Under both the Public Sector Regulations and the Equality Act, institutions cannot simply disclaim responsibility for inaccessible third-party tools they have procured and present to users as part of their service. If a prospective student encounters an inaccessible UCAS-integrated portal, a CRM-powered contact form, or a virtual open day platform that your institution has embedded or linked to, you should assess whether reasonable adjustments are possible or whether an accessible alternative exists. When procuring new platforms, accessibility conformance should be a contractual requirement — ask vendors for a Voluntary Product Accessibility Template (VPAT) or a WCAG 2.1 AA audit report.

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.1 (published June 2018) added 17 success criteria to WCAG 2.0, with a focus on mobile accessibility and users with cognitive or low-vision disabilities. It remains the standard referenced in the UK Public Sector Regulations and the EAA. WCAG 2.2 (published October 2023) adds 9 further criteria, including clearer requirements around focus appearance, target size for interactive elements, and authentication that does not require cognitive tests. WCAG 2.2 is backwards-compatible — a site conforming to 2.2 AA also conforms to 2.1 AA. While 2.1 remains the enforceable baseline for most institutions, regulators and accessibility auditors increasingly benchmark against 2.2, and the W3C has deprecated 2.0's Success Criterion 4.1.1 in the 2.2 version.

Where should we start if our website has never had an accessibility audit?

Begin with a baseline automated scan using a tool such as axe DevTools or WAVE — these identify roughly 30–40% of WCAG failures without any specialist knowledge. Review your most visited page templates: homepage, course pages, contact and application forms, and any video content. Run through the 10 priority checks listed above. Then commission a manual audit from a certified accessibility specialist covering a representative sample of pages, including those with interactive elements. Use the audit findings to populate your accessibility statement, prioritise fixes in your next development sprint, and establish a quarterly review cycle. Institutions regulated by the OfS should document this process as part of their access and participation planning.