Accessibility Statements In Higher Education: The Document That Stopped Being True

Most UK universities published an accessibility statement between 2019 and 2021, when the regulations required one. Most have not rewritten it since. In the meantime the estate has been rebuilt at least once: a new course finder, a new consent banner, two departmental sites, a clearing microsite, a supplier booking system for accommodation.

That is the actual compliance problem in higher education. Not the absence of a statement, the presence of one that stopped being true. The regulations do not ask for a document. They ask for an accurate description of the estate, kept up to date, with known issues and a route to report a problem. A statement that no longer matches the estate is a worse position than no statement at all, because it is a published claim you cannot support.

This is the last piece in a series built on our audit of 64 UK higher education websites, run in August 2026. The audit measured machine readability, not conformance, so it cannot tell you how many statements are stale. It can tell you exactly how much of the estate a single statement is likely to miss.

What the statement has to contain

The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 set the required sections, and the Government Digital Service publishes a model statement that most institutions started from. The sections are not arbitrary. Each one exists because a different reader needs an answer.

Two of these are where institutions lose credibility rather than points. An empty non accessible content section reads as untested, not as compliant, to anyone who has audited a large estate. And a known issues list with target dates that have passed is a documented record of missed commitments, which is exactly what a monitoring body or a procurement panel looks for.

The honest version is stronger. A statement listing twelve defects with named owners and dated remediation targets tells a reader that the institution tested its estate and manages the findings. A clean statement with no evidence tells them nobody looked.

How a true statement becomes a false one

Nothing dramatic happens. The statement is accurate on publication day and nothing ever forces it to change, while the thing it describes changes constantly.

The fix is not a bigger annual review. It is a set of triggers wired into the work that changes the estate. When a new subdomain goes live, the statement's scope section is part of the launch checklist. When a course finder or fee table is rebuilt, the known issues list is revisited in the same ticket. When a third party widget is added, someone records whether it was tested. When a defect is fixed, the entry is closed with a date.

None of that is an accessibility skill. It is release governance, and it is the same gap that leaves structured data and llms.txt files unmaintained after a launch. The document decays for the same reason the markup does: no owner, no trigger, no place in the release process.

The scope problem nobody wants to open

Thirteen percent of the institutions we audited split the course estate across more than one domain, and the platform mix behind those estates ran from TerminalFour and Contensis to WordPress, Sitecore, Drupal, and Craft. A statement written for the main domain says nothing about where the applicant actually reads the fees.

This is uncomfortable because widening the scope widens the obligation. The alternative is worse: a statement whose scope section is silently narrower than the journey it is supposed to describe. An applicant who cannot read a fee table on a microsite is not reassured that the main domain conforms.

So the estate inventory comes first: every domain and subdomain, its platform, its publishing team, whether it has been tested, and whether it is in scope. That inventory is the same artifact a platform consolidation starts from, which is why the accessibility conversation and the estate consolidation conversation tend to arrive together.

Campaign microsites deserve a policy of their own. A clearing site stood up in August and retired in October is often the highest pressure journey of the year, and it is almost never covered. Either it inherits the tested component library and falls inside scope, or the statement says plainly that it does not.

Why this matters beyond compliance

An accessibility statement is one of the few pages on a university estate that is a public, dated, first person claim about the quality of the institution's own digital services. It gets read by applicants, by disability services, by auditors, and increasingly by systems summarizing the institution on someone else's behalf.

That is the thread through this whole series. The work that makes a page announceable to a screen reader is the work that makes it quotable by an answer engine, as covered in WCAG 2.2 for university websites. The work that puts fees and entry requirements into server rendered HTML serves both, as covered in publishing course facts. The statement is where the institution says out loud how far along that work it is.

Treated as a legal artifact, it is a page nobody reads. Treated as the public record of a maintained estate, it is the one place a university can demonstrate that it tests what it publishes.

How to make the statement true again

• Enumerate the estate. Every domain, subdomain, campaign site, and supplier hosted service in the applicant journey, with its platform and its publishing team.
• Decide scope explicitly. Each site is in scope and tested, or named as out of scope with a reason. Silence is not an option the regulations allow.
• Test one journey rather than a sample of pages. Search a course, read the fees, read the entry requirements, start an enquiry, with a keyboard and with a screen reader.
• Rewrite the statement from the findings. Real conformance claim, real non accessible content, real known issues with owners and dates.
• Wire the triggers into release. New domain, rebuilt template, new third party widget, closed defect: each one touches the statement.
• Set and hold a review date, and name the role that owns it rather than the person who happens to hold it.

Steps one and five need a mandate rather than a tool, which is the operating model gap described in composable DXP programs. We run this as one program across accessibility and inclusive design and platform engineering, because a defect fixed in the component library lands estate wide and a defect fixed on a page lands nowhere else.

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.

The reason statements go stale is that nobody owns the number in them. At UEL accessibility was given a measured position instead: an audit against WCAG 2.1 AA, 90 percent compliance across the measured estate, AA exceeded in the redesigned experience and AAA in critical sections. A figure like that can be published honestly, and corrected when it moves.

Two structural conditions made it maintainable. The design system sits with the in house team, so component level fixes land across every template rather than page by page. And accessibility is reported on the same continuous dashboard as performance and conversion, so a regression is a known state rather than a discovery made by a complainant.

That is the whole argument for treating the statement as an output of a live process. A statement backed by a current measure and a named owner is a compliance asset. One backed by a two year old audit is a liability. The engagement is documented in the University of East London case study.

Frequently asked questions

How often does an accessibility statement need reviewing?

The regulations require it to be accurate and kept up to date rather than reviewed on a fixed cycle. In practice an annual review plus event based triggers is the only pattern that holds, because a large estate changes far faster than once a year.

Does the statement have to cover subdomains and microsites?

It has to be clear about what it covers. If a course finder, business school, or clearing site sits on its own domain and serves the applicant journey, either bring it into scope and test it or say explicitly that it is not covered and why.

Is it safer to claim full conformance?

No. A full conformance claim you cannot evidence is a published statement that fails on first inspection. A partial conformance claim with a dated known issues list is defensible and shows an active program.

Who should own the statement?

A named accountable role rather than a team inbox, usually in digital or web services, with a route into legal and disability services. Ownership by committee is how the review date gets missed.

Does a stale statement affect search or AI visibility?

The statement itself does not. The underlying defects do, because facts that are unreachable by a screen reader are usually unreachable by a crawler too. The statement is the signal that the institution knows which defects it has.

Where to start

Open your own statement and check three things: the list of sites it names, the date it was last reviewed, and whether any known issue has a target date in the past. If any of the three surprises you, the estate inventory is the next piece of work, not the rewrite.

If you want the audit view of your own estate first, the UK higher education AI discoverability report shows what 64 institutions publish in machine readable form, and where the same defects reach both audiences.

Read next

The substrate underneath the statement: WCAG 2.2 for university websites maps the common page patterns to the criterion each one fails and the fact an answer engine loses. On the fetch side, AI crawler policy for higher education covers what institutions state in robots.txt versus what they enforce at the edge.

A statement describes an estate someone designed. University website design covers how those decisions are made at scale, and SEO for universities covers what the same estate costs in search.

Review triggers belong in the governance layer of a plan: higher education digital strategy.

Working on a university estate rather than a single page? Our higher education practice page sets out how the strategy, design, engineering and marketing work runs as one team, and the UK higher education AI discoverability report holds the audit data behind this series. Also worth reading: Student recruitment marketing, Choosing a CMS for a university estate.

For the same audit read as a marketing diagnosis, see higher education marketing: what an audit of 64 UK university websites reveals.