Skip to content

Standards

EN 301 549 in the UK: what applies to websites and apps

UK law presumes a public-sector site conforms when it meets WCAG A and AA, not EN 301 549. Where EN 301 549 still matters: EU sales, tenders, software.

Your UX Agent teamProduct
8 min read

In the UK, EN 301 549 no longer gives a public-sector website its presumption of conformity. Since 26 October 2022, the UK’s public-sector accessibility regulations presume that a public body’s website or app conforms when it meets the WCAG success criteria at Level A and AA, and GOV.UK’s guidance names WCAG 2.2 AA.

EN 301 549 still reaches UK organisations in three ways:

  • through the European Accessibility Act, when they offer services it covers to consumers in the EU, where EN 301 549 is the standard expected to give a presumption of conformity once cited;
  • through contracts and tenders that name it;
  • for products beyond the web, such as software and support services, which WCAG alone does not cover.

EN 301 549 and WCAG

WCAG covers web content. EN 301 549 is a European standard, published jointly by ETSI, CEN and CENELEC, for ICT products and services as a whole, and its clauses follow the kinds of technology it covers:

ClauseCoversWhere WCAG comes in
5Generic requirements, including products whose functionality is closed to assistive technologyNot at all
6 and 7Two-way voice, and videoNot at all
8HardwareNot at all
9Web pagesThe WCAG 2.1 Level A and AA success criteria, one row each, plus 9.6, WCAG’s conformance requirements
10Documents that are not web pages, such as a PDFWCAG’s criteria, adapted to documents, and two requirements of its own
11Software, including mobile appsWCAG’s criteria, adapted to software, and requirements of its own
12Documentation and support servicesNot at all
13ICT that provides relay or emergency service accessNot at all
The technical clauses of EN 301 549 V3.2.1, and where WCAG comes in

For a web page, the two mostly agree: clause 9 takes WCAG’s Level A and AA criteria, WCAG 2.1 in V3.2.1 and WCAG 2.2 in V4.1.1. The difference is everything around the page. A site that passes WCAG can still miss EN 301 549’s rows on support services, documentation and, in V4.1.1, user preferences. The EN 301 549 rows that apply to a website lists them; what V4.1.1 changes covers the newer version.

UK public sector: WCAG, not EN 301 549

The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 require most public bodies to make their websites and apps accessible. Public service broadcasters and some non-governmental organisations are exempt, schools and nurseries are partly exempt, some content is exempt, and a body may claim a disproportionate burden after assessing it and explaining it in its accessibility statement (regulations 4 and 7).

As made in 2018, regulation 9 presumed that a website conformed when it met harmonised standards whose references had been published in the Official Journal of the European Union or, where none had been, “the European standard on the accessibility requirements suitable for public procurement of ICT products and services in Europe”, which a footnote identified as EN 301 549 V1.1.2 (2015-04). From December 2018 the cited harmonised standard was itself EN 301 549 V2.1.2.

The Public Sector Bodies (Websites and Mobile Applications) Accessibility (Amendment) (EU Exit) Regulations 2022 replaced that. Its explanatory note says it “substitutes for the European accessibility standard (EN 301 549) the international web accessibility standard” as the standard a public body’s website or app must meet to be presumed to conform. Since 26 October 2022, regulation 9 presumes conformity to the extent that the site or app meets the Level A and AA success criteria of WCAG, “as amended from time to time”.

That last phrase means the WCAG version follows WCAG itself. GOV.UK’s guidance for public bodies names WCAG 2.2 AA. It also says the Government Digital Service monitors compliance, and the Equality and Human Rights Commission enforces it in England, Scotland and Wales, and the Equality Commission for Northern Ireland in Northern Ireland. Public bodies must publish an accessibility statement too.

UK businesses: the Equality Act names no standard

A UK business serving UK customers falls under the Equality Act 2010 in England, Wales and Scotland, and the Disability Discrimination Act 1995 in Northern Ireland. The Equality Act requires anyone providing a service to the public to make reasonable adjustments for disabled people (section 20, applied to services by section 29 and Schedule 2). It names no technical standard, neither EN 301 549 nor WCAG.

WCAG gives you a published, testable measure to work to, and it is the one the public-sector regulations use. EN 301 549 adds little for a UK website on its own, except where the service goes beyond the web page.

Selling into the EU: where EN 301 549 comes back

The European Accessibility Act covers the listed services a UK company offers to consumers in the EU, unless it is a micro-enterprise providing services, under the national law of each member state where it sells. It also covers listed products, such as computers and e-readers, placed on the EU market. Whether the Act applies to a UK company works through the scope step by step, and what the Act requires of a website covers the rest.

Under the Act, a product or service that meets a harmonised standard cited in the Official Journal is presumed to meet the Act’s requirements that the standard covers. None is cited yet; EN 301 549 V4.1.1 awaits its citation. EN 301 549 is the standard expected to fill that role, so test the web pages against both versions’ web rows: the last section shows how one set of tests covers them.

Contracts, tenders and products beyond the web

EN 301 549 began as a standard for public procurement: the 2018 regulations called it “the European standard on the accessibility requirements suitable for public procurement of ICT products and services in Europe”. A buyer anywhere can still name it in a tender or a contract, and then it is what you are measured against, in the version the contract names. BSI publishes it in the UK as BS EN 301 549.

If you supply software, hardware or a support service rather than a website, EN 301 549 is the standard that covers it: WCAG alone leaves clauses such as 5, 8 and 12 untested.

Which standard applies, case by case

Where a law names a standard, the law sets the requirements and meeting the standard gives a presumption that you meet them. A contract that names a standard makes the standard itself the requirement.

Your caseStandardLaw or source
A UK public body’s website or appWCAG Level A and AA; GOV.UK names WCAG 2.2 AAThe 2018 regulations, regulation 9 as substituted in 2022
A UK business serving UK customersNone namedThe Equality Act 2010; in Northern Ireland, the Disability Discrimination Act 1995
EU sales the European Accessibility Act coversA harmonised standard once one is cited; none is yet, and EN 301 549 V4.1.1 awaits citationNational law in each member state where you sell
A tender or contract that names EN 301 549The version the contract namesThe contract
Which standard a UK organisation is measured against

One set of tests for both

For web pages, one set of tests serves the UK and the EU: WCAG 2.2 Level A and AA, plus 4.1.1 Parsing, covers the WCAG criteria that both EN 301 549 V3.2.1 and V4.1.1 use for web pages, and 2.2 AA is what GOV.UK names. Work through them with our WCAG 2.2 checklist of every A and AA criterion, then check the EN 301 549 rows outside WCAG, such as support and documentation, by hand.

This is general information, not legal advice: check the regulations, your contracts and the law of each member state where you sell.

Frequently asked questions

Is EN 301 549 a legal requirement in the UK?

Not for websites. Since 26 October 2022, UK law presumes that a public sector website or app conforms when it meets WCAG at Level A and AA, and the Equality Act 2010 names no standard. EN 301 549 matters when you offer services the European Accessibility Act covers to consumers in the EU, or when a contract names it.

What is the difference between EN 301 549 and WCAG?

WCAG covers web content. EN 301 549 covers ICT products and services, including hardware, software, documents and support services, and for web pages takes WCAG’s Level A and AA criteria: WCAG 2.1 in V3.2.1, WCAG 2.2 in V4.1.1.

Which WCAG version must UK public sector websites meet?

GOV.UK’s guidance names WCAG 2.2 AA. The regulations point to WCAG’s Level A and AA success criteria as amended from time to time, so the version follows WCAG.