All Jisc websites need to comply with new regulations on the accessibility of websites and mobile applications of public sector bodies. These ensure that the information and services we provide are accessible to all users, including disabled people.
This is living guidance that will grow over time. Last updated 19 August 2021.
Images
All images should have meaningful file names and descriptive alt text that accurately describes the image.
Infographics
Good infographics can be great for people who find reading lots of text hard. However, alt text is really important for these – you need to make sure you convey the full meaning in your description.
Consider who the audience is and whether the purpose of the infographic is to convey what something is, or if it is instructional. If you cannot adequately describe the meaning of the infographic, you may need to choose another way to present this information.
- The Poet image training tool offers training and guidance on how to write effective image descriptions
Documents
Adding content to a web page as HTML is always preferable to hosting it as a separate document. For most users HTML is quicker, easier and more widely accessible. However, in some cases a Word document or pdf may be the most appropriate format.
Word documents (.docx)
If a Word document is the best format for your content:
- Use the accessible Jisc-branded Word document template on Panacea, where appropriate
- Make sure any links in your document have meaningful descriptions – a clear action or description such as ‘view our staff policy‘ is far more accessible than ‘to see our staff policy, click here‘
- Using clear, helpful language is important. Read some pointers on writing clear, accessible content for the web and see our written style guide for all Jisc websites and printed materials
- Run Microsoft’s inbuilt accessibility checker and fix any issues flagged before uploading
- Read Jisc’s detailed guide to improving accessibility with Microsoft Word on SharePoint
Pdf documents (.pdf)
HTML is always preferable, but if a pdf is the best format for your content:
- Use the accessible Jisc-branded Word document template on Panacea, where appropriate
- Use the Adobe Acrobat Pro DC Accessibility Checker (or run the inbuilt Microsoft Word accessibility checker before you convert it) and fix any issues flagged before uploading
- Read GDS guidance on documents
- Read advice from Lexdis on making accessible pdfs and other documents
PowerPoint presentations
We can offer presentations as accessible PowerPoint or pdf downloads and host them via SlideShare. As we cannot guarantee the downloadable option SlideShare offers meets accessibility regulations we need to offer a fully accessible version of the presentation by request, so please be aware of this when creating content.
- Use the accessible Jisc-branded PowerPoint template on Panacea, where appropriate
- Check using Microsoft’s inbuilt accessibility checker and fix any issues flagged
- If converting to pdf, follow the pdf document guidance and checks before uploading
- Aim to use as large a font size as possible – ideally, size 24 – and avoid using all caps in text
- Read Jisc’s detailed guide to improving accessibility with Microsoft PowerPoint on SharePoint
Podcasts
You must make a transcript available for any new podcast recordings you upload – offer this as a downloadable, accessible Word document.
You can use Otter.ai to create a transcript (free for up to 600 minutes per month).
Videos
All videos uploaded to or linked from Jisc websites should have closed captions and include a good, clear text description explaining what the video is showing and its purpose.
For resources such as webinars and video tutorials, you need to provide a transcript – you can offer this as a downloadable, accessible word document.
You will need to manually check captions and transcripts thoroughly for accuracy before you can share them. Captions and transcripts generated using an automated tool are a good start, but often need significant editing for accuracy and context in order to make these useful. You’ll need to ensure they contain all the meaningful content from the audio.
- Read WCAG guidelines on time-based media (which includes videos, animations and audio recordings) from W3C
- Read GDS guidance on making videos accessible
- You can generate closed captions in Microsoft Stream, Microsoft Teams and YouTube
- You can use Otter.ai to create a transcript (free for up to 600 minutes per month, limited to 40 minutes per video). Please remember to manually check these for accuracy
Audio descriptions
Ask yourself, “without audio, can I understand what the video is trying to convey?” If the answer is no, or if you are in doubt, add audio description.
Ensure video will not induce seizures
Check font size
Ideally, font size should be user selectable. If not, try and make sure it does not obscure the action in the video.