The need for clean tag structures and green check marks keeps me up at night. Seriously. But, it wasn’t until I took a JAWS screen reader class lead by a great blind guy named Z, that the answer to the question “How much is too much?” became clear. You remediate to be first, compliant; second, create a logical user experience; and third, to present data in the most complete way possible.
Compliance items like tag structures, alt-text, languages, TD, TR etc. etc. all need to follow WCAG and PDF/UA to ensure the user experience makes sense. P.O.U.R. Perceivable, Operable, Understandable, Robust.
- Does all the text read in the right order and as you would expect (nothing artifacted or skipped that should have been voiced)?
- Can they navigate from header to header?
- Can they pull up the list of key items like:
- Are those items voiced properly and have all the interactivity required?
Cleaning empty <P> tags and consolidating <Sections> literally gives me zen. I mean it. Seeing an unorganized and cluttered tag tree is the stuff of nightmares for me. But most of the time I have a pile of pdfs to review and approve. The truly accessible PDF is one that allows the AT user to have very, very close to the same information as the sighted user. The guidelines and rules are there to give us boundaries and paths to follow. But, in the end, it is the usability that makes the document accessible.
When I was able to get JAWS and walk through the document to test for usability I found that I could spend less time chasing the stuff no one sees and focus on the things that matter to the user experience. I still need those green check marks and I am still checking for colorblind compliance. But I am focused on the user experience much more than before. The rules are the means by which I can create the same user experience. They drive the process. Remember, no one is going to not get sued for an empty <P> tag. But if you turn a table into a jpeg and slap some alt-text on it and call it good, you are asking for trouble.