What makes a document accessible?
If we focus on accessibility at the content level, there are three fundamental principles which, if implemented when documents are created and edited, make content accessible.
These three principles plus a few additional items (listed below) can also be used as a check-list for manual auditing of document accessibility. This involves going through the document checking for breaches of accessibility guidelines. The following check list is divided into sections to help provide a framework for checking:
Principle 1: structure
The idea is to use structural elements (tags) such as headings to properly structure documents and therefore identify clearly the various elements which compose the document. These structural elements are often referred to as ‘styles’ in word processors.
- Does the document have a title?
- Are proper Headings (of part, chapter, sessions, subsections, etc.) used and do they impose proper hierarchical order e.g. do Heading 2s define subsections of Heading 1s, Heading 3s define subsections of Heading 2s and so on?
- Lists: are true numbered and/or bulleted lists used?
Is presentation separate from structure? For example, there should be no additional blank lines inserted, whose purpose is to put spaces between paragraphs.
Set the “space before/after” attribute for paragraphs instead. Also do not insert blank lines to move onto a new page. Insert a page break instead.
- Similarly, formatting should not be used to mimic headings.
View some Examples of document structure (the document is available in PDF format).
Principle 2: give alternatives
Every non textual element, such as an image must have a textual alternative. In all cases this alternative needs to take the context into account. For instance a single picture might have a different description whether it is used in a context or just as decoration. You may find it useful to watch the video from week 1 on ‘Video and audio barriers’ again.
- Images: Do all images have an appropriate alternative text?. We go into alternative text for image descriptions in more depth in step 2.11.
- Audio: is there a text transcription containing all the text said in the sound (if any), and all the meaningful other sounds?
- Videos: Is there a text transcription and are captions (subtitles) available?
Principle 3: identify
- Is the main language of the document specified?
- Are there other languages used and are these indicated?
- Has the document metadata in the document properties been filled in. This includes metadata like title, author, description, etc. (Microsoft Office 2016 and 365 support)
- Have abstracts for substantial document components like chapters and major sections, been provided?
- Does link anchor text make sense?
Is there any presentation feature such as colour, bold, italics, alignment, etc. used to provide information that is not present explicitly in the text.
For example are there important items in the document highlighted using a colour like red but their significance is not stated in the text.
- Is the language used clear and simple?
- Are paragraphs short?
- Are abbreviations and acronyms expanded at the first occurrence?
- Are tables simple – Do they have a header row and do they read correctly row by row, column by column? There is a short tutorial available: W3C Web Accessibility Initiative tutorial on Tables
- Is the “Repeat headings on each page” option for tables set?
- Are accents on letters present in both upper and lowercase (when writing in a language that has accents on letters e.g. French and Irish)
- Improve layout for people with print difficulties?
- Is font size 12 points used or more?
- Is a sans serif font used?
- Is text left aligned, if the language requires reading from left to right?
- Is there sufficient contrast between background and foreground colours?
- Is the page background colour a non-white colour e.g. a light pastel colour?
- Are there any animated effects such as blinking text? Can they be switched off?
See below a downloadable version of the principles that make a document accessible and links to the W3C Consortium WCAG (Web Content Accessibility Guidelines) and other standards plus further information on making documents (including those in PDF format) accessible.
From your experience, have you found times when some of these may not apply or do you find that your first language does not fit the guidelines?
© This work is a derivative of a work created by Dublin Institute of Technology and Université Paris 8 Vincennes Saint-Denis, and licensed under CC-BY BY 4.0 International Licence adapted and used by the University of Southampton. Erasmus + MOOCs for Accessibility Partnership.