---
title: "WCAG 2.2 For University Websites: The Accessibility Work That Also Makes You Readable To AI"
url: https://www.axelerant.com/blog/wcag-2-2-university-websites
published: 2026-09-12T09:30:00.000Z
author: "Brahmpreet Singh, Senior Marketing Manager" (brahmpreet.singh@axelerant.com)
industries: Education
lenses: Experience, Data, Activation, Optimization
source: Axelerant Thinking
---

# WCAG 2.2 For University Websites: The Accessibility Work That Also Makes You Readable To AI

> What WCAG 2.2 added, the UK legal position for universities, and why the same defects that fail a screen reader also hide course fees from answer engines.

Accessibility and AI readability are the same job, done for two different readers. A fee table that a screen reader cannot announce is a fee table an answer engine cannot quote. A course finder that only works with a mouse is a course finder with no crawlable path to any course page. Grade requirements set as an image are invisible to both.

This is the most useful thing WCAG 2.2 does for a university web team in 2026: it turns a compliance obligation the institution already has into the substrate that decides whether the estate is readable by machines at all. Two budgets, one piece of work.

The percentages below come from our audit of [64 UK higher education websites](/uk-highered-ai-discoverability), run in August 2026. It measured machine readability rather than conformance, and the overlap is the point.

## Where the two audiences fail on the same defect

![Table mapping five common university page patterns to the WCAG 2.2 criterion each one fails and the fact an answer engine loses as a result](/images/insights/wcag-shared-defects.png)

Forty five percent of these institutions kept course fees out of the server rendered response, and thirty four percent did the same with entry requirements. Those are AI discoverability findings. They are also, in most cases, 1.3.1 and 1.4.5 findings sitting in an accessibility backlog somewhere in the same institution, filed against a different team, prioritized on a different scale.

The practical consequence: if you are already funding accessibility remediation, you are already funding a large part of the readability work. Sequence them together and the second one costs a fraction of what it costs as a separate program.

## What WCAG 2.2 actually added

WCAG 2.2 became a W3C Recommendation in October 2023. It adds nine success criteria and does not remove any 2.1 obligation, so a 2.1 AA estate is not automatically a 2.2 AA estate. It also formally retires 4.1.1 Parsing, which browsers now handle, so anything your tooling still reports against it can be closed.

![Three grouped cards listing the nine success criteria added in WCAG 2.2 by conformance level, grouped by navigating an estate, operating a control, and completing an application](/images/insights/wcag-new-criteria.png)

Read that list against an applicant journey rather than against a checklist and three of them stand out for higher education.

- 2.5.8 Target Size (Minimum) hits course finders hardest. Filter chips, pagination, and compare toggles are routinely under twenty four by twenty four CSS pixels, and they are the controls a prospective student uses most on a phone.

- 2.4.11 Focus Not Obscured hits every estate running a consent banner, a chat widget, and a sticky header at once, which is nearly all of them. The keyboard user tabs to a control they cannot see.

- 3.3.7 Redundant Entry and 3.3.8 Accessible Authentication hit the application and clearing journeys, where the same details get requested twice across two systems and a code has to be recalled from memory.

The rest are real, but those four are where a large institution finds its first hundred defects, and all four live in components rather than in content.

## The legal position, stated plainly

UK public sector bodies, which includes most universities, sit under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. The regulations reference WCAG 2.1 AA and require a published accessibility statement that is accurate and kept up to date. WCAG 2.2 is not what the regulations name today, and it is the version the tooling, the auditors, and the procurement questionnaires have moved to.

Institutions recruiting into the EU should also check the European Accessibility Act position with their own legal team, since it reaches services offered to consumers in the EU rather than only public bodies at home. That is a question for counsel, not for a web team, and it is worth asking before a procurement cycle rather than after.

Our reading for planning purposes: build to 2.2 AA, keep the statement honest about known issues, and treat 2.1 as the floor rather than the target. An accurate statement listing twelve known defects with owners and dates is a stronger position than a clean statement nobody has tested.

## Where a defect is actually fixed

The reason accessibility programs stall in higher education is almost never technical knowledge. It is that the defect is found on a page and fixed on a page, one at a time, across an estate of tens of thousands of URLs and a dozen publishing teams.

![Four ownership layers where an accessibility defect can be fixed: design system and component library, page templates, editor workflow, and the accessibility statement and governance, each with cadence and owner](/images/insights/wcag-ownership-layers.png)

Fix target size in the component library and it lands on every course finder in the estate at once. Fix it on a page and you have fixed one page. The same is true of focus appearance, label patterns, and table headers. Roughly the whole of WCAG 2.2's new operable criteria belongs in the component layer, which is why it is a design system conversation before it is a remediation one.

The template layer decides whether facts render on the server or after hydration, and that single decision is where accessibility and AI readability become literally the same change. It is the decision described in [publishing fees, entry requirements and accommodation costs](/blog/publish-course-facts-answer-engines).

The editor layer is where regression comes from. Alt text, meaningful link text, real table headers, and not pasting a fee table as a screenshot. Training decays. Guard rails in the authoring interface do not, which is why validation at publish time beats another workshop.

## A thirteen site estate makes this harder than it sounds

Thirteen percent of the institutions we audited split the course estate across more than one domain, and the platform mix behind those estates ranged from TerminalFour and Contensis to WordPress, Sitecore, Drupal, and Craft. An accessibility statement covering the main domain says nothing about the microsite where the fee table lives. A component library fix in the main platform does not reach the department site built separately in 2019. This is the same fragmentation that breaks [structured data](/blog/structured-data-university-course-pages) and [llms.txt](/blog/llms-txt-for-universities) curation, showing up in a different audit.

So the estate inventory is prerequisite work, not administrative overhead. You cannot state conformance for sites you have not enumerated, and you cannot enumerate them from inside one CMS.

## How to run this in one program

- Enumerate the estate: every domain and subdomain, its platform, its publishing team, and whether it is covered by an accessibility statement.

- Test one journey end to end rather than a sample of pages. Search a course, read the fees, read the entry requirements, start an enquiry, with a keyboard and a screen reader.

- Sort the findings by layer, not by severity, and fix everything that belongs in the component library first.

- Move fees, entry requirements, and accommodation costs into server rendered HTML while the templates are open, since that is one change serving both audiences.

- Publish the statement with real known issues, named owners, and a review date, then hold the review date.

- Add automated checks at publish time so the estate does not drift back between audits.

Steps one and three are the ones that need a mandate rather than a tool. That is the same operating model gap described in [composable DXP programs](/blog/composable-dxp-content-operations), which is why we run [accessibility and inclusive design](/what-we-do/design/accessibility-and-inclusive-design) alongside [platform engineering](/what-we-do/engineering/platform) rather than as a testing exercise at the end.

## What this looked like at the University of East London

The University of East London moved off Sitecore onto Drupal on Acquia with us, and rebuilt the estate as one platform rather than a set of pages. It is the closest reference point we have for this problem at full institutional scale, 125 years of content, students from 156 countries, and five distinct audiences reading the same site for different reasons.

Accessibility was a stated inclusivity commitment there, and the engagement had to turn it into something measurable. The estate was audited against WCAG 2.1 AA, reached 90 percent compliance across the measured set, exceeded AA in the redesigned experience and went to AAA in the sections that carry the most weight for applicants.

Three practices did the work, and all three transfer to 2.2:

- Fix at the component layer. A design system the in house team owns means a focus, contrast or target size correction lands once and applies everywhere.

- Structure content for progressive disclosure, so pages stay usable at 200 percent zoom and with a screen reader instead of collapsing into a wall of text.

- Measure continuously rather than at launch, with accessibility on the same dashboard as performance and conversion.

The overlap with machine readability was not incidental. Semantic headings, real text instead of images of text, and labelled form fields are the same substrate an answer engine parses. See the [University of East London case study](/case/dxp-for-university-of-east-london).

## Frequently asked questions

### Does WCAG 2.2 replace WCAG 2.1?

It extends it. All the 2.1 success criteria remain, nine are added, and 4.1.1 Parsing is retired as obsolete. A 2.1 AA estate has real work to do before it can claim 2.2 AA, mostly in the operable and input criteria.

### Are UK universities legally required to meet WCAG 2.2?

The 2018 regulations reference WCAG 2.1 AA, so 2.2 is not the named standard today. Auditors, procurement questionnaires, and testing tools have largely moved to 2.2, and building to it now avoids a second remediation cycle. Confirm your own position with your legal team, particularly if you recruit into the EU.

### Does accessibility work improve AI visibility?

The part of it that puts information into semantic, server rendered HTML does, directly, because that is the same substrate an answer engine reads. The part that improves focus indicators or pointer alternatives does not affect machine readability at all, and still matters for the applicant who arrives from an AI answer.

### What belongs in an accessibility statement?

What the site conforms to, which parts do not conform and why, known issues with dates, how to report a problem, when it was last reviewed, and who owns it. A statement that claims full conformance without evidence is a liability. One that lists twelve honest defects with owners is a credible position.

### Where do most university estates fail first?

Course finders, on target size and keyboard operation, and fee or entry requirement content delivered as an image, a PDF, or a client side render. All four are template and component defects rather than content defects, which is why they are worth fixing centrally.

## Where to start

Take one course journey, run it with a keyboard, and note where a fact you needed was not in the page source. That single test usually produces both the accessibility backlog and the AI readability backlog in one pass. The [full 64 institution report](/uk-highered-ai-discoverability) has the comparative picture, [AI crawler policy for higher education](/blog/ai-crawler-policy-higher-education) covers whether machines can reach the page in the first place, and we work with [higher education institutions](/industries/higher-ed) across that chain. [Talk to us](/contact) about your own estate.

## Read next

Before readability comes reachability: [AI crawler policy for higher education](/blog/ai-crawler-policy-higher-education) covers the four layers that can refuse a fetch, and the 11 percent of audited institutions blocking answer engines without deciding to.

Then the substrate itself: [publishing fees, entry requirements and accommodation costs](/blog/publish-course-facts-answer-engines), [structured data for university course pages](/blog/structured-data-university-course-pages), and [llms.txt for universities](/blog/llms-txt-for-universities).

The public record of all of it is the statement itself. [Accessibility statements in higher education](/blog/accessibility-statements-universities) covers the six required sections, how the estate drifts away from them, and how much of a split estate one statement silently misses.

Both readers are served by the same templates. [University website design](/blog/university-website-design) covers the six audiences a course page has to satisfy, and [SEO for universities](/blog/seo-for-universities) covers what happens in search when those templates withhold a fact.

Three companion pieces take the same evidence into planning: [higher education digital strategy](/blog/higher-education-digital-strategy), [choosing a CMS for a university estate](/blog/university-cms-estate) and [student recruitment marketing](/blog/student-recruitment-marketing).

Working on a university estate rather than a single page? Our [higher education practice page](/industries/higher-ed) sets out how the strategy, design, engineering and marketing work runs as one team, and the [UK higher education AI discoverability report](/uk-highered-ai-discoverability) holds the audit data behind this series.

For the same audit read as a marketing diagnosis, see [higher education marketing: what an audit of 64 UK university websites reveals](/blog/higher-education-marketing).

---

Read on the web: https://www.axelerant.com/blog/wcag-2-2-university-websites