Hands up if you were asked to do a manual check
Editoria11y, the accessibility checker we are using in the WMS, has made it easy to spot issues with your web pages. But聽鈥� and I鈥檓 sure you鈥檝e noticed this 鈥� it cannot do the same for the PDFs and Word documents you upload to those pages. Instead, it warns you that a 鈥渕anual check is needed鈥�. What then? How can you make your files accessible? Here are some tips.
Word has its own accessibility checker
If you first create a document in Word, and then convert it to PDF, you can use the built-in before exporting to PDF. It will look familiar to you because it works like Editoria11y, highlighting and explaining each issue it spots. And those issues will also look familiar because they are almost the same as the ones that Editoria11y alerts you about on your WMS site.
Accessibility rules for documents are (mostly) the same as for your webpage
By now you know what goes into making a web page accessible. Apply that knowledge when working in Word and you will be well on your way to creating an accessible document.
- Check that the order of headings is logical: Heading 1 at the top, Heading 2 above each new section, describing the content below, Heading 3 for a subsection.
- to each image or mark it as decorative if the image conveys no meaning.
- Use meaningful text for links, don鈥檛 just paste in the URL.
- Avoid tables if possible. If you must use a table, include table headers, avoid setting a fixed width, and adjust the table so it doesn鈥檛 spread over multiple pages (this might be seen as two distinct tables when exported to PDF).
- for the screen reader to read out loud to its user.
Preserve the accessibility settings when saving as PDF
When , make sure to select the correct options so the PDF you are creating will make use of the accessible structure you have put in place.
- When saving on Windows: on the 鈥淪ave As鈥� dialog box select聽鈥淥ptions鈥�, then 鈥淒ocument structure tags for accessibility鈥�.
- When saving on a Mac: select聽鈥淏est for electronic distribution and accessibility鈥�.
Or maybe this content shouldn鈥檛 be in a document
Keep in mind that even an accessible document can seem unwelcoming to your site's visitors. PDFs and Word documents are designed for printing, and reading them on a browser or mobile device is not ideal.
Also, it is easier for you to manage updates to a web page than a PDF. Editing a WMS page is straightforward; you know where to find it, you can work on a draft until it鈥檚 ready, and the old versions are retained. Whereas to make a change to a PDF, you have to find the original document, save it as a new PDF, upload it to your website, and make sure existing links point to the new version.
To keep things simple for you and for visitors to your website, create a web page for anything that you expect people to read on their screen, and create an accessible PDF for anything meant for printing.
Courses that offer a deeper dive into accessibility
Interested in gaining a deeper understanding about accessibility? Check out these courses:
- Web Accessibility WS-106
- (through LinkedIn Learning)
