Write accessible digital content - introduction and index
Content is king; it is what makes your site special and attractive to users. You should always write clear and consistent content to ensure that all users can benefit from it, regardless of any impairment.
Users read and interact with digital content in a very different way to printed material. You must present digital content in a way that allows users to rapidly absorb and understand the information you are communicating.
In essence:
• Write clear and concise content, and prioritise the most important information;
• Ensure your content is well structured, as consistent as possible, and supports users in scanning for key information;
• Ensure image use is appropriate and relevant, and provide equivalent descriptions of all images for those who will not be able to see them;
• Present data, including tables and charts, as clearly and simply as possible;
• Content should be specifically written or modified, and prepared for digital consumption – you should not simply reuse documents prepared for print.
If you use a content management system, or you submit content in a particular template or format, read all the available documentation, and try the accessibility guidance out.
Whatever method you are asked to use to supply content, it should support you to deliver all of the accessibility guidance contained here, without the need for technical knowledge. If it cannot, this issue will need to be addressed. Refer those responsible for implementing your site to the guidance contained here.
In this section
The following pages include techniques that are designed to help you create accessible user experiences. They are grouped according to related practices and can be referred to as necessary. While these techniques are tried and tested, keep in mind that they may not be the only way to address a particular user need.
- Write Accessible Text
- Structure your content to help users scan for key information
- Use clear and simple language
- Provide alternatives for images, video and audio content
- Aim for maximum consistency
- Style to maximise readability
- Keep tables and data representation simple
- Provide meaningful links
- Provide simple form instructions and feedback
- Create accessible web pages
- Create accessible MS Word documents
- Use styles
- Specify headings
- Specify table headers and titles
- Name files in a helpful way
- Provide Alt Text for each image
- Specify the language of the content
- Check your work is accessible
- Create accessible MS PowerPoint documents
- Use slide masters
- Specify headings
- Specify table headers and titles
- Name files in a helpful way
- Give each slide a title
- Provide Alt Text for each image
- Specify the language of the content
- Check your work is accessible
- Create accessible PDFs
- Always test your content with users who have access needs
References for this section
WCAG 2.1
- 1.1.1 Non-text Content (A)
- 1.2.1 Audio-only and Video-only (Pre-recorded) (A)
- 1.2.2 Captions (Pre-recorded) (A)
- 1.2.3 Audio Descriptions or Media Alternative (Pre-recorded) (A)
- 1.2.4 Captions (Live) (A)
- 1.2.5 Audio Description (Pre-recorded) (AA)
- 1.2.6 Sign Language (Pre-recorded) (AAA)
- 1.3.1 Info and Relationships (A)
- 1.3.3 Sensory Characteristics (A)
- 1.4.1 Use of Colour (A)
- 1.4.3 Contrast (Minimum) (AA)
- 1.4.5 Images of Text (AA)
- 2.4.2 Page Titled (A)
- 2.4.3 Focus Order (A)
- 2.4.4 Link Purpose (In Context) (A)
- 2.4.6 Headings and Labels (AA)
- 2.4.9 Link Purpose (Link Only) (AAA)
- 3.1.1 Language of Page (A)
- 3.1.2 Language of Parts (AA)
- 3.1.4 Abbreviations (AAA)
- 3.1.5 Reading Level (AAA)
- 3.2.3 Consistent Navigation (AA)
- 3.2.4 Consistent Identification (AA)
- 3.3.1 Error Identification (A)
- 3.3.2 Labels or Instructions (A)
- 3.3.3 Error Suggestion (AA)
EN 301 549 v 2.1.2
- 9.1.1.1 Non-text Content
- 9.1.2.1 Audio-only and Video-only (Pre-recorded)
- 9.1.2.2 Captions (Pre-recorded)
- 9.1.2.3 Audio Descriptions or Media Alternative (Pre-recorded)
- 9.1.2.4 Captions (Live)
- 9.1.2.5 Audio Description (Pre-recorded)
- 9.1.3.1 Info and Relationships
- 9.1.3.3 Sensory Characteristics
- 9.1.4.1 Use of Colour
- 9.1.4.3 Contrast (Minimum)
- 9.1.4.5 Images of Text
- 2.4.2 Page Titled
- 2.4.3 Focus Order
- 9.2.4.4 Link Purpose (In Context)
- 9.2.4.6 Headings and Labels
- 3.1.1 Language of Page
- 3.1.2 Language of Parts
- 9.3.2.3 Consistent Navigation
- 9.3.2.4 Consistent Identification
- 9.3.3.1 Error Identification
- 9.3.3.2 Labels or Instructions
- 9.3.3.3 Error Suggestion
Further reading
- WebAIM’s alternative text page
- WebAIM’s complex image tutorial
- WAI guidance on images
- WAI Alt text Decision Tree
- Text descriptions and emotion rich images
- Writing great alt text: Emotion matters
- 3 questions to Help Decide If an Image Doesn't Need Alt Text
- WAI Decorative Images
- 5 most annoying website features I face as a blind person every single day
- Deafness and the User Experience
- Accessibility according to actual people with disabilities
- Register of Irish Sign Language Interpreters
- Guidelines for Working with Interpreters, June 2021 (PDF)
- A guide to using subtitles, captions and transcripts for accessibility
- WAI guidance on Captions/Subtitles
- Google – Add subtitles and captions
- Why Consistency is Important to Accessible Design
- Readability (Yale University)
- Meaningful links (Princeton University)
- Links (Yale University)
- Making Accessible Links: 15 Golden Rules For Developers
- The Trouble with Tables: A Brief Introduction
- Make your Word documents accessible to people with disabilities
- Make your PowerPoint presentations accessible to people with disabilities
- Office Accessibility Center - Resources for people with disabilities
- Improve accessibility with the Accessibility Checker
- WebAIM’s PowerPoint Accessibility
- Make your PowerPoint presentations accessible to people with disabilities