Striving to remove barriers that prevent us from building Vibrant, Diverse, Inclusive, Accessible Communities!



The University of Washington Accessible Technology - Documents Information

The University of Washington Accessible Technology provides a well organized web presentation on Document Accessibility.  Here are some of the main highlights and the links to each section:

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. A good starting point for learning about accessibility is our IT Accessibility Checklist. The following items from the Checklist are especially applicable to digital documents:

  1. Do headings form an outline of the page content?
    For details, see our Headings page.
  2. Are lists used to identify all content that can be described as a list of something?
    For details, see our Lists page.
  3. 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.
  4. Do images have alternative text?
    For details, see our Images page.
  5. Are tables used solely for presenting rows and columns of data (not for layout), and are the column and row headers identified?
    For details, see our Tables page.
  6. Is the tab order and read order logical and intuitive?
    For details, see our Tab and Read Order page.
  7. 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.
  8. Does the interface have sufficient contrast between text color and background color?
    For details, see our Color Contrast page.
  9. Are links and buttons used appropriately and labeled correctly?
    For details, see our Links page.
  10. Does the document have a title that describes its topic or purpose?
    For details, see our Titles page.
  11. Are mechanisms in place that allow users to bypass blocks of content (e.g., bookmarks in a PDF)?
    For details, see our Navigation page.
  12. 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:

Also see:

View Topic - Accessible PDFs


Striving to remove barriers that prevent us from building a Diverse, Vibrant, Inclusive, Accessible Community!

Share or Print with: