Jisc is pleased to be part of the Digital Accessibility Working Group. We work with the Digital Accessibility Regulations Jiscmail list to represent the HE and FE sector’s ‘digital context’ to Government Digital Services. This helps ensure guidance on the new legislation is meaningful and appropriate to the sector. Find out more on Jisc support for accessibility.
This week we met to discuss accessibility statements. HE and FE institutions – by law – will have to provide accessibility statements on their website.
The law on accessibility statements
You will need to publish an accessibility statement from:
- 23 September 2019 for new websites created from 23 September 2018,
- 23 September 2020 for existing websites,
- 23 June 2021 for mobile apps.
These have minimum requirements that will be audited. The audits will include things like what accessibility standards were used when building the site? Which elements of the site are not accessible? What are you doing about these?
This is causing anxiety for some organisations. They don’t know which (if any) accessibility standards were used, nor which parts of the site are compliant or non-compliant. It’s a good time to get an audit done – or even better – get your web developers on some accessibility courses. The latter is important. Far better that you know how to create accessible websites than you ‘have a go’ and pay for it to be corrected!
So accessibility statements are here to stay, but the big question is will they be any use? Does it help a disabled student to know “our website is AA compliant to WCAG 2.1 standard except for checkpoints 1.4.1, 1.4.2 and 1.4.3”?.
Our colleagues at Government Digital Services have asked us to come up with some sample accessibility statements that can attempt to bridge the gap between what is legally required and what is ethically useful.
We’ve started to work on this with a threefold approach, recognising that there are elements that legally have to appear but that these elements are meaningless to users unless they are interpreted into plain English ‘can do’ statements. This is the plan we’re currently trying out and we’d love to get your feedback. We should have something specific to show you within a week but in the meantime feel free to comment on the process and principle…
- A core user focused accessibility statement along the lines of ‘as a result of creating this website to accessibility standards, these are the ways you can personalise and improve your experience…”. This will be genuinely informative to all users, not least those with disabilities. It may also give organisations a chance to point to their onsite assistive technology provision, study skills guidance etc.
- Links from the user-focused statement to:
- the technically focused legal requirement – on which auditing and reporting will take place.
- a plain English ‘exceptions’ report that will signpost and explain any accessibility failures. It is important to realise that some accessibility ‘failures’ are actually accessibility successes for other users. An example would be an interactive 360⁰ campus ‘walkthrough’. It could add immense value to students with mobility difficulties, autism or anxiety yet it would be completely inaccessible to a screen reader user. The exceptions appendix can report on failures that are being actively improved as well as explaining those that can’t be. It will also point to alternative resources or support.
Currently we’re hoping to produce an HE and local government version by mid to late March with an FE version shortly after.
What do you think of this approach?
Alistair McNaught – March 2019