惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

大猫的无限游戏
大猫的无限游戏
K
Kaspersky official blog
Apple Machine Learning Research
Apple Machine Learning Research
B
Blog
aimingoo的专栏
aimingoo的专栏
M
MIT News - Artificial intelligence
小众软件
小众软件
云风的 BLOG
云风的 BLOG
腾讯CDC
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
Hugging Face - Blog
Hugging Face - Blog
S
SegmentFault 最新的问题
Stack Overflow Blog
Stack Overflow Blog
量子位
S
Secure Thoughts
G
GRAHAM CLULEY
C
CXSECURITY Database RSS Feed - CXSecurity.com
人人都是产品经理
人人都是产品经理
雷峰网
雷峰网
T
Threat Research - Cisco Blogs
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Cisco Talos Blog
Cisco Talos Blog
G
Google Developers Blog
爱范儿
爱范儿
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
有赞技术团队
有赞技术团队
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Martin Fowler
Martin Fowler
The GitHub Blog
The GitHub Blog
Google DeepMind News
Google DeepMind News
C
Cisco Blogs
D
Darknet – Hacking Tools, Hacker News & Cyber Security
博客园 - 聂微东
宝玉的分享
宝玉的分享
H
Hackread – Cybersecurity News, Data Breaches, AI and More
N
Netflix TechBlog - Medium
Forbes - Security
Forbes - Security
Engineering at Meta
Engineering at Meta
S
Security Affairs
Help Net Security
Help Net Security
博客园 - 三生石上(FineUI控件)
AWS News Blog
AWS News Blog
博客园 - 叶小钗
Recent Commits to openclaw:main
Recent Commits to openclaw:main
V2EX - 技术
V2EX - 技术
Hacker News: Ask HN
Hacker News: Ask HN
Project Zero
Project Zero
H
Heimdal Security Blog
W
WeLiveSecurity
C
Check Point Blog

TetraLogical Blog

Designing for people with reading disabilities - TetraLogical Designing for people who are D/deaf - TetraLogical Designing accessible documents - TetraLogical Introduction to creating accessible documents - TetraLogical Inclusive user research: vulnerable people - TetraLogical Designing for people who are blind - TetraLogical Designing for people with low vision - TetraLogical Meet the team: Niamh Madden - TetraLogical Designing for people with anxiety - TetraLogical Designing for people with disabilities - TetraLogical Accessible building blocks for the web videos - TetraLogical Common accessibility misconceptions - TetraLogical Common misconceptions about testing accessibility - TetraLogical Common misconceptions about implementing accessibility - TetraLogical Common misconceptions about WCAG - TetraLogical Common misconceptions about disability - TetraLogical Meet the team: Grace Snow - TetraLogical Sustainable accessibility in complex organisations: strategic foundations - TetraLogical Sustainable accessibility in complex organisations: organisational realities - TetraLogical Sustainable accessibility in complex organisations: external factors - TetraLogical Common misconceptions about screen readers - TetraLogical Guide to the Inclusive Design Principles - TetraLogical Meet the team: Ian Lloyd - TetraLogical Annotating designs using common language - TetraLogical Meet the team: Catriona Morrison - TetraLogical Championing inclusive language - TetraLogical Press release: TetraLogical launches accessible self-led training courses to help digital teams build confidence in accessibility - TetraLogical Why inclusive products are green products - TetraLogical Accessible Recruitment - TetraLogical Accessibility and the agentic web - TetraLogical Meet the team: Craig Abbott - TetraLogical Foundations: types of assistive technology and adaptive strategies - TetraLogical European Accessibility Act (EAA) FAQ - TetraLogical Screen reader HTML support tables - TetraLogical Interview with Lola Odelola - TetraLogical Understanding EN 17161 Design for All - TetraLogical Inclusive user research: building rapport - TetraLogical Foundations: Keyboard accessibility - TetraLogical Can generative AI write contextual text descriptions? - TetraLogical Understanding the European Accessibility Act (EAA) - TetraLogical Meet Josh: a sportsman who has spinal muscular atrophy - TetraLogical Meet Jonathan: a photographer who has ADHD - TetraLogical Foundations: grouping forms with `<fieldset>` and `<legend>` - TetraLogical XR Accessibility: for people with moving disabilities - TetraLogical Meet Andre: a music producer and blind screen reader user - TetraLogical Foundations: types of disability - TetraLogical Meet Lauren: a film editor who has ADHD - TetraLogical Meet Steve: a photographer who is deaf and low vision - TetraLogical Foundations: form validation and error messages - TetraLogical Meet Hasmukh: a blind cricketer and screen reader user - TetraLogical XR Accessibility: for people with hearing disabilities - TetraLogical XR Accessibility: for people with thinking disabilities - TetraLogical XR Accessibility: for people with seeing disabilities - TetraLogical Introduction to XR Accessibility - TetraLogical Foundations: labelling text fields with input and label - TetraLogical Design patterns and WCAG - TetraLogical Does WCAG 2.2 apply to native apps - TetraLogical Why are my live regions not working? - TetraLogical Building a culture of accessibility - TetraLogical When to use tabindex= Accessibility foundations - TetraLogical Meet the team: Demelza Feltham - TetraLogical Can generative AI help write accessible code? - TetraLogical Meet the team: Steve Faulkner - TetraLogical Meet the team: Gez Lemon - TetraLogical Keyboard accessibility myths and WCAG - TetraLogical Amendment to the Public Sector Accessibility Regulations - TetraLogical What Considerations for TV user interface accessibility - TetraLogical Meet the team: Alistair Duggin - TetraLogical Sticky content: focus in view - TetraLogical The only accessibility specialist in the room - TetraLogical Meet the team: Ian Pouncey - TetraLogical Meet the team: Dean Holden - TetraLogical Meeting WCAG Level AAA - TetraLogical Foundations: accessible names and descriptions - TetraLogical Inclusive XR: accessible augmented reality experiences - TetraLogical Foundations: pointer gestures - TetraLogical Meet the team: Graeme Coleman - TetraLogical Adding sign language to videos - TetraLogical Foundations: introduction to WAI-ARIA - TetraLogical Meet the team: Joe Lamyman - TetraLogical Inclusive XR: accessible 3D experiences - TetraLogical Foundations: visible focus styles - TetraLogical Foundations: target sizes - TetraLogical Meet the team: Henny Swan - TetraLogical Meet the team: Ela Gorla - TetraLogical Foundations: native versus custom components - TetraLogical Foundations: HTML semantics - TetraLogical Accessibility and supporting Internet Explorer - TetraLogical Meet the team: Felicity Miners-Jones - TetraLogical Accessibility and QR codes - TetraLogical Inclusive user research: recruiting participants - TetraLogical Research insight: accessibility of images - TetraLogical Meet the team: Léonie Watson - TetraLogical Android accessibility: roles and TalkBack - TetraLogical Accessible design systems - TetraLogical Meet the team: Patrick H. Lauke - TetraLogical Inclusive user research: analysing findings - TetraLogical How to write user stories for accessibility - TetraLogical
Public sector accessibility regulations - TetraLogical
2019-07-26 · via TetraLogical Blog

Posted on by Léonie Watson in Standards

Tags: WCAG

A new law concerning the accessibility of public sector websites and mobile apps came into effect in 2018. This article explains what the Public Sector Accessibility Regulations mean, what’s included and what isn’t, and the deadlines by which all public sector websites and mobile apps must comply.

A European Union (EU) Directive on the accessibility of public sector websites and apps was approved in October 2016 and has since been incorporated into the national laws of all EU member states. In the UK it’s known as the Public Sector Bodies (Websites and Mobile Apps) Accessibility Regulations 2018.

Definition of public sector

The Public Sector Accessibility Regulations consider national, regional, and local authorities to be public sector bodies, as well as any organisation that receives public funding. Associations formed between one or more authorities or organisations that receive public funding are also counted as public sector bodies, providing they’re formed to serve the general interest and are not industrial or commercial.

Non-Governmental Organisations (NGO) like charities are not counted as public sector bodies by the Public Sector Accessibility Regulations, unless they:

  • Are mostly funded by public money
  • Provide services that are essential to the public or that are aimed at disabled people

Schools and nurseries are excluded, except for any websites or apps needed to use their services (like choosing school meal preferences or signing up to an activity club). Public sector broadcasters and their subsidiaries are also excluded.

It is important to realise that organisations not covered by the Public Sector Accessibility Regulations may still be covered by other legislation. In the UK for example, the Equality Act 2010 requires that all services (including websites and apps) are accessible to disabled people, no matter which sector the organisation operates in.

Definition of websites and apps

The Public Sector Accessibility Regulations apply to all (internal and external) websites and apps that belong to a public sector organisation, except:

  • Extranets or intranets published before 23 September 2019, unless they have undergone a major revision since 23 September 2018
  • Websites and apps that are only for archival purposes, and that will not be updated after 23 September 2019

Certain types of content are also excluded under the Public Sector Accessibility Regulations:

  • Office file formats published before 23 September 2018, unless the documents are needed for administrative activities relating to the public sector organisation
  • Pre-recorded time-based media (audio or video) published before 23 September 2020
  • Live time-based media
  • Maps and mapping services, as long as maps intended for navigational purposes provide the essential information in an accessible format
  • Third party content that is not funded, created, or controlled by the public sector organisation
  • Reproductions of documents in heritage collections that cannot be made accessible without damaging the authenticity or preservation of the original, or that cannot be made accessible using automated or cost-efficient techniques

Requirements

The requirements for the Public Sector Accessibility Regulations are set out in clauses 9, 10, and 11 of European Standard EN 301 549. EN 301 549 defines Level AA of the Web Content Accessibility Guidelines (WCAG) 2.1 as the required standard.

In addition to meeting WCAG 2.1 Level AA, the Public Sector Accessibility Regulations also say that an accessibility statement must be published for each website and app.

There are three deadlines for meeting the Public Sector Accessibility Regulations:

  • Websites published after 23 September 2018 must conform to WCAG 2.1 Level A by 23rd September 2019
  • Websites published before 23 September 2018 must conform to WCAG 2.1 Level AA by 23 September 2020
  • Apps must conform to WCAG 2.1 Level AA by 21 June 2021

Disproportionate burden

It may not be necessary for a website or app to conform to the Public Sector Accessibility Regulations if it can be proved it would be a “disproportionate burden” to do so.

To claim disproportionate burden, public sector organisations need to assess the website or app and weigh the burden of making it accessible against the benefit to disabled people. The assessment should consider:

  • The size of the organisation and the resources it has available
  • The purpose of the organisation and the services it provides
  • The cost of making the website or app accessible, and the impact the cost will have on the organisation
  • The benefit to people with disabilities, and the impact making the website or app accessible will have on their ability to participate in society

A lack of time or accessibility knowledge are not reasons for claiming disproportionate burden. Not making accessibility a priority within an organisation is also not considered a good reason.

If a public sector organisation claims that making a website or app accessible would be a disproportionate burden, it must explain why in the accessibility statement for the website or app.

Accessibility statements

The Public Sector Accessibility Regulations say that every website and mobile app must have an accessibility statement, and that the statement must be regularly reviewed and updated.

The accessibility statement for a website must:

  • Be in accessible format
  • Be available on the website itself

The accessibility statement for a mobile app must:

  • Be in accessible format
  • Be available at the point the app is downloaded, or available on the website of the public sector organisation

The accessibility statement must conform to the model accessibility statement. The model statement says that websites and apps should be monitored at least once a year for conformance with the Public Sector Accessibility Regulations.

Monitoring and reporting

Monitoring is carried out by each EU member state, and a regular report is filed with the EU. In the UK the Cabinet Office is responsible for monitoring UK conformance with the Public Sector Accessibility Regulations, and the first report will be submitted between 1 January 2020 and 31 December 2021, then every 12 months after that.

To make monitoring and reporting consistent across the EU, a monitoring and reporting methodology has been agreed. The methodology is intended for use by EU member states, but it also provides a useful framework for use by public sector organisations to monitor the conformance of websites and mobile apps.

The methodology describes two monitoring methods:

  • Simplified monitoring designed to detect non-conformance
  • Thorough monitoring designed to assess the extent of conformance

In other words, each public sector organisation must monitor its websites and apps for conformance with the Public Sector Accessibility Regulations and use the information to update its accessibility statements, and each EU member state must monitor national conformance and use that information to report to the EU.

PSAR amendment 2022

In 2022, an amendment to the Public Sector Accessibility Regulations was released to address changes brought about by the UK's departure from the EU in 2020.

Updated 6 November 2023.

Next steps

Find out more about the Web Content Accessibility Guidelines in our WCAG primer and how assessments can help you identify issues in your websites, mobile applications, design systems, and other products and services.