Skip to content

Latest commit

 

History

History
17 lines (12 loc) · 1.24 KB

non-html-content.md

File metadata and controls

17 lines (12 loc) · 1.24 KB

Non-HTML Content

Ensure accessibility of non-HTML content. Such as:

  • Adobe PDF documents
  • Forms
  • Microsoft Word documents
  • Microsoft PowerPoint presentations

In addition to all of the other principles, PDF documents, forms, and other non-HTML content must be as accessible as possible. If you cannot make these materials accessible, consider using HTML instead or, at the very least, provide an accessible alternative to visitors.

PDF documents and forms should also include a series of labels, with organization, to make it more accessible. A PDF file with labels looks the same, but it is almost always more accessible to a person using a screen reader.

WAVE Chrome extension

If you are designing an interactive map, with an option to download non-HTML content, the WAVE Chrome extension will provide an alert indicating a separate review is needed to confirm it's accessibility, like so:
WAVE screenshot indicating a PDF document is present and a separate accessibility review is needed to confirm its accessibility

Return to the Best Practices homepage.