Who the new accessibility regulations apply to and why accessibility is important.
Making a website or mobile app accessible means making sure it can be used by as many people as possible.
This includes those with:
- impaired vision
- motor difficulties
- cognitive impairments or learning disabilities
- deafness or impaired hearing
At least 1 in 5 people in the UK have a long term illness, impairment or disability. Many more have a temporary disability.
Accessibility means more than putting things online. It means making your content and design clear and simple enough so that most people can use it without needing to adapt it, while supporting those who do need to adapt things.
For example, someone with impaired vision might use a screen reader (software that lets a user navigate a website and ‘read out’ the content), braille display or screen magnifier. Or someone with motor difficulties might use a special mouse, speech recognition software or on-screen keyboard emulator.
Why making your public sector website or app accessible is important
People may not have a choice when using a public sector website or app, so it’s important they work for everyone. The people who need them the most are often the people who find them hardest to use.
Accessible websites also tend to work better for everyone. For example, they are often faster and easier to use and tend to appear higher in search engine rankings.
Most public sector websites and apps do not currently meet accessibility requirements. For example, a recent study found that 4 in 10 local council homepages failed basic tests for accessibility.
Common problems include websites that cannot be navigated using a keyboard, inaccessible PDF forms that cannot be read out on screen readers, and poor colour contrast that makes text difficult to read - especially for visually impaired people.
You may be breaking the law if your public sector website or app does not meet accessibility requirements.
Meeting accessibility requirements
New regulations came into force for public sector bodies on 23 September 2018. They say you must make your website or mobile app more accessible by making it ‘perceivable, operable, understandable and robust’. The full name of the regulations is the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
The 2018 regulations build on your existing obligations to people who have a disability under the Equality Act 2010 (or the Disability Discrimination Act 1995 in Northern Ireland). These say that all UK service providers must consider ‘reasonable adjustments’ for disabled people.
For example, somebody might ask for information in an alternative, accessible format, like large print or an audio recording. There are a number of factors that determine what makes something a ‘reasonable’ adjustment.
Your website or app will meet the newer legal requirements if you:
- meet the international WCAG 2.1 AA accessibility standard - although there are valid legal reasons for not meeting accessibility standards
- publish an accessibility statement that explains how accessible your website or app is
The best way of doing this is firstly to check how far your website or app currently meets WCAG 2.1, and where there are problems. Then, make a plan to fix the problems you’ve found. Your web team should use the detailed guide to making your website accessible and publishing an accessibility statement.
The deadline for meeting the new requirements and the steps you need to take depend on whether you have:
- a new website (published on or after 23 September 2018)
- an existing website
- a mobile app
Who has to meet the 2018 accessibility regulations
All public sector bodies have to meet the 2018 requirements, unless they are exempt.
Some organisations might not have to fully meet the requirements if doing so would be a ‘disproportionate burden’. Depending on their resources, these organisations may take some steps towards meeting the requirements now, and make further improvements later on.
Public sector bodies include:
- central government and local government organisations
- some charities and other non-government organisations
When you may be exempt from accessibility regulations
All UK service providers have a legal obligation to make reasonable adjustments under the Equality Act 2010 or the Disability Discrimination Act 1995 (in Northern Ireland).
But the following organisations are exempt from the 2018 regulations:
- non-government organisations like charities - unless they are mostly financed by public funding, provide services that are essential to the public or aimed at people with a disability
- schools or nurseries - except for the content people need in order to use their services, for example a form that lets you outline school meal preferences
- public sector broadcasters and their subsidiaries
Check with your legal adviser (if you have one) if you’re not sure whether the new accessibility rules apply to you.
When complying with accessibility regulations might be a ‘disproportionate burden’
Some organisations are not on the exempt list but still do not need to fully meet accessibility standards. This is the case if the impact of fully meeting the requirements is too much for an organisation to reasonably cope with. The 2018 regulations call this a ‘disproportionate burden’.
You need to think about disproportionate burden in the context of what’s reasonable to do right now. If your circumstances change, you’ll need to review whether something’s still a disproportionate burden.
If you want to declare that making particular things accessible is a disproportionate burden, you’re legally required to carry out an assessment. In your assessment you weigh up, roughly speaking:
- the burden that making those things accessible places on your organisation
- the benefits of making those things accessible
When making your assessment, you need to think about:
- your organisation’s size and resources
- the nature of your organisation (for example, do you have services aimed at people who are likely to have a disability?)
- how much making things accessible would cost and the impact that would have on your organisation
- how much users with a disability would benefit from you making things accessible
You might judge that the benefits of making some things accessible would not justify the impact on your organisation. In that case, you can claim it would not be reasonable for you to make those things accessible because it’s a disproportionate burden.
You should not take things like lack of time or knowledge into account in your assessment - or argue that making things accessible is a disproportionate burden because you’ve not given it priority.
You might be able to argue it’s a disproportionate burden to meet all the requirements if doing so would use up most of your organisation’s budget for the year and leave you unable to do any of your other work - and would not vastly improve things for users with a disability.
A simple code change that improves your website or app’s colour contrast is relatively low cost and would improve things for a lot of people with sight impairments. You might not be able to argue that changing this is a disproportionate burden.
You’re less likely to be able to claim disproportionate burden for services that:
- are specifically aimed at disabled people, for example ‘apply for a blue badge’
- enable people to participate in society, like ‘register to vote’ or ‘find a job’
In many cases you’ll need to work out what it is reasonable for you to fix now, and what you’ll be able to fix in the future.
If you decide that fixing something would be a disproportionate burden, you’ll need to say so in the accessibility statement you publish on your website or mobile app.
Even if you’re exempt from the 2018 regulations, or judge that meeting them would be a disproportionate burden, under the Equality Act 2010 or the Disability Discrimination Act 1995 (in Northern Ireland) you’re still legally required to make reasonable adjustments for people with disabilities when they’re needed - for example, by providing the information they need in another, more accessible format.
If you create a new public sector website on or after 23 September 2018, you need to meet accessibility standards and publish an accessibility statement by 23 September 2019. You will then need to review and update your statement regularly.
As well as helping everyone to use your website, thinking about accessibility upfront saves you money and time in the long run. It’s cheaper and quicker than fixing problems once something is built.
When you’re building a new site, you can choose software and use processes that build accessibility into what you do.
Most existing websites that were published before 23 September 2018 need to comply with the 2018 regulations by 23 September 2020.
You may not have to meet the requirements for your whole website or app if doing so would be a disproportionate burden - for example, if it’s very expensive to make even simple changes and those changes would bring very limited benefits to people with a disability.
If you’re not sure what would be disproportionate in your situation, talk to your legal adviser.
In some circumstances, you might need to do things earlier than 2020. If you make substantial changes to the code, for example to create new features, or if you create a subdomain with its own distinct codebase, it’s likely that these will need to be fully accessible from 23 September 2019 (the same deadline as for new websites).
If you’re using an agile approach to redeveloping an existing website, you can make accessibility improvements as part of your approach to iteration. This is covered in our guidance on how to approach fixing problems.
You’re legally responsible for your website meeting accessibility requirements, even if you’ve outsourced your website to a supplier.
If you’ve outsourced some or all of your website to a supplier, you’ll need to work together to make sure your website meets the 2018 regulations.
Start by asking how much it would cost to make the changes needed to make your website or app accessible. You might find that fixing everything at once would put a disproportionate burden on your organisation. Work together with your supplier to agree what it’s reasonable to fix now, and when you’ll make the remaining changes.
State what your plans are in your accessibility statement to make things as clear as possible for people using your website or app.
When you renew your contract or enter a new one, you should:
- follow government guidance on procuring technology - awarding contracts that are not too long and using open standards, for example, makes it easier to take advantage of technical advances that can improve accessibility
- where possible, use web technologies rather than native mobile apps - because it’s easier to update web technologies
- make meeting accessibility standards in procurement part of the request for quotation (RFQ)
- consider building regular accessibility reviews into the contract
- include accessibility as part of the contract evaluation
The European Commission has published guidance in its Accessible ICT Procurement Toolkit.
Accessibility requirements apply in the same way as websites for new, existing or outsourced apps, but the deadline for meeting them is 23 June 2021.
How the accessibility regulations will be enforced
The Government Digital Service will be responsible for monitoring that public sector bodies comply with the 2018 accessibility regulations.
The regulations will be enforced by the Equality and Human Rights Commission (in Great Britain) and the Equality Commission for Northern Ireland.