WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Thoughts on PDF Accessibility

for

From: Birkir R. Gunnarsson
Date: Sep 27, 2019 5:40PM

I guess there are a few things in WCAG that do not apply to PDF files,
keyboard focus outline (2.4.7) and maybe text resizing (1.4.4) come to
mind. I'm honestly not sure if there's a way to customize focus
outline or resizing in PDf files (well, assuming the PDF file is real
text, not an image of text of course).
Then there are interaction specific criteria like change of context on
focus or on state change (3.2.1 and 3.2.2) which I'm not sure would
apply to PDFs, fortunately I've managed to stick to the more
traditional and static ones, not testing the limit of what's
technically possible in the PDF format.

With forms, I don't know if there is a PDF equivalent of
aria-describedby to assign a tag as the accessible description for
another focusable tag (e.g. error message or tooltip scenarios).


On 9/27/19, William O'Donnell < <EMAIL REMOVED> > wrote:
> Forgot about Read Out Loud, I agree.
> Have a good day. Sorry if emails are coming across twice, internet is bad
> here.
>
>
> On 9/27/19, Karlen Communications < <EMAIL REMOVED> > wrote:
>> NEVER use Read Out Loud to do testing for accessibility...or at all!
>>
>> The best approach is to walk down the Tags Tree to perform three parts of
>> a
>> quality assurance process:
>>
>> 1. Is everything in the document that needs a tag have a tag?
>> 2. Are the tags correct for the type of content (headings, lists,
>> paragraphs, tables and so forth).
>> 3. Are the Tags in a logical reading order for the content/type of
>> document.
>>
>> Additionally, if the document was scanned and needed OCR, you want to use
>> a
>> screen reader like JAWS or NVDA to make sure that there are spaces
>> between
>> words and that words don't have spaces between characters.
>>
>> Cheers, Karen
>>
>>