When creating digital documents, there are a few basic issues to keep in mind in order to ensure your content is accessible. These issues are the same regardless of whether your document is in HTML, Word, PDF, or another document format.
Below is a checklist to consult to ensure that your document meets accessibility standards.
Accessible Document Checklist
- Do Headings form an outline of the page content?
For details, see our Headings page. - Are Lists used to identify all content that can be described as a list of something?
For details on Lists, see our Navigation page. - Do Form Fields within web pages and documents have appropriately coded labels and prompts, and do they provide helpful, accessible error and verification messages?
For details, see our Forms page. - Do images have Alternative Text?
For details, see our Images page. - Are Tables used solely for presenting rows and columns of data (not for layout or aesthetic purposes), and are the column and row headers identified?
For details, see our Tables page. - Is the Tab Order and Read Order logical and intuitive?
For details, see our Tab and Read Order page. - Have you avoided using Visual Characteristics to communicate information (e.g., “click the circle on the right” or “required fields are in red”)?
For details, see our Visual Characteristics page. - Does the interface have sufficient Color Contrast between text color and background color?
For details on Color Contrast, see our Visual Characteristics page. - Are Links used appropriately and labeled correctly?
For details, see our Links page. - Does the document have a sufficent Title that describes its topic or purpose?
For details on Titles, see our Navigation page. - Are mechanisms in place that allow users to Bypass Blocks of Content (e.g., bookmarks in a PDF)?
For details, see our Navigation page. - Has the Language of the document (or individual parts of a multilingual document) been defined?
For details, see our Language page.
Additional resources
The following pages focus on issues that are unique to document accessibility:
- How to Make Accessible PDFs
- How to Use Accessibility Tags in a PDF
- How to Export Accessible PDFs (Word, InDesign, Powerpoint)
- How to Make Accessible PowerPoint Presentations
- High-Quality Scans
- How to Check for Accessibility in Microsoft Office
Outsourcing PDF Remediation
Crawford Technologies provides document remediation services at prices and turnaround times that seem to be a good match for higher education institutions.
Contact the vendor for a quote: das-quotes@crawfordtech.com
Questions about remediation orders:
- Emily Currier: ecurrier@crawfordtech.com
- James Muenster: muenster@crawfordtech.com
- Tracey Sheets, Facilities Manager: tsheets@crawfordtech.com
- Holly Bullock, Accessibility Operations Manager: hbullock@crawfordtech.com
WCAG 2.1 Success Criteria
The issues described on this page, and associated pages, map to the following success criteria in the W3C’s Web Content Accessibility Guidelines (WCAG) 2.1:
- 1.1.1 Non-text Content (Level A)
- 1.3.1 Info and Relationships (Level A)
- 1.3.2 Meaningful Sequence (Level A)
- 1.3.3 Sensory Characteristics (Level A)
- 1.3.5 Identify Input Purpose (Level AA)
- 1.4.1 Use of Color (Level A)
- 1.4.3 Contrast (Minimum) (Level AA)
- 1.4.5 Images of Text (Level AA)
- 1.4.11 Non-text Contrast (Level AA)
- 2.4.1 Bypass Blocks (Level A)
- 2.4.2 Page Titled (Level A)
- 2.4.3 Focus Order (Level A)
- 2.4.6 Headings and Labels (Level AA)
- 3.1.1 Language of Page (Level A)
- 3.1.2 Language of Parts (Level AA)
- 3.3.1 Error Identification (Level A)
- 3.3.2 Labels or Instructions (Level A)
- 3.3.3 Error Suggestions (Level AA)
- 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)