No user should be excluded on the basis of disability. To do so would breach the Equality Act, Public Sector Accessibility Regulations, and the trust of our members.
Accessibility is not an annual accreditation, a box to tick before moving on to something else. Accessibility is everyone’s responsibility and needs to be a fundamental part of your service. Built-in from day one. You need to follow accessibility guidelines and test what you do with older and disabled people.
Your service must also comply with any other legal requirements, including providing content and functionality in Welsh if appropriate.
You must develop with a ‘usability first’ approach. Many pitfalls can be avoided by first considering usability.
- Does the site make sense?
- Is it easy to use?
- Is it presented in a logical manner?
- Are the interactions standard and intuitive?
- Is the content useful and clearly written?
- Does the design enhance or detract from the core content and functionality?
The answers to these questions affect both usability and accessibility for everyone, regardless of disability.
When designed or restructured for optimal usability for everyone, accessibility then becomes much easier, and is often found to have been addressed entirely in the usability fixes.
- You must aim to meet Level AA of the Web Content Accessibility Guidelines (WCAG) 2.1
- You should take a ‘common sense’ approach to accessibility, using the WAI guidelines to inform your decisions rather than treating them as a box-ticking exercise
- You must flag and share for discussion any exceptions to this during development
Find out about rules to follow when using WAI-ARIA.
- Your service should be tested by disabled people, older people, and people who use assistive technologies
- You should aim to do this at least twice as your service is developed
Find out about how to conduct accessibility testing. There is also advice on doing a basic accessibility check if you can’t do a detailed one.
Find out about choosing appropriate formats.
When writing content you should consider what information would be useful to people with access needs.
All Jisc sites will need to publish an accessibility statement (view a sample accessibility statement). This should outline the problems you know about, and what you’re planning to do about them.
Users can now request accessible versions of any inaccessible content, and expect it in a reasonable time.
If you’ve identified any of your content as inaccessible you should consider how you could quickly provide alternatives if someone makes a request.
Public Sector Bodies Accessibility Regulations
Websites and apps created by Jisc are subject to the Public Sector Bodies Accessibility Regulations. While teams should already be working to make their sites accessible the regulations make accessibility statements and providing alternative formats a legal obligation.
The deadline for implementation depends on when your site was created (or substantially updated).
- Sites created before 23 September 2018 will need to comply by 23 September 2020
- Sites created on or after 23 September 2018 will need to comply by 23 September 2019
- Mobile apps will need to comply by 23 June 2021
Find out more about meeting the new regulations.
Jisc sites should be usable by recent versions of these screen readers:
They should also be usable by basic operating system screen magnifiers like:
They should also be usable by: