E-mail List Archives
Re: PDF/UA Quandary 1 - Bullets in LBL tags - Does this interrupt current expected screenreader flow of text?
From: chagnon
Date: May 29, 2018 3:57PM
- Next message: Dane Dunham: "WCAG 2.0 Questions"
- Previous message: Duff Johnson: "Re: PDF/UA Quandary 1 - Bullets in LBL tags - Does this interrupt current expected screenreader flow of text?"
- Next message in Thread: Duff Johnson: "Re: PDF/UA Quandary 1 - Bullets in LBL tags - Does this interrupt current expected screenreader flow of text?"
- Previous message in Thread: Duff Johnson: "Re: PDF/UA Quandary 1 - Bullets in LBL tags - Does this interrupt current expected screenreader flow of text?"
- View all messages in this Thread
We run into the same situation not just with screen readers, but with any AT that uses tabs (or similar keys) to navigate the document.
This problem ends up forcing the user to tap twice for each bullet or numbered list element.
Tap. Bullet.
Tap. Body text of the bullet.
Tap. Bullet
Tap. Body text of the next bullet.
I'm venturing that all of our AT haven't completely addressed this.
So the question is: Why haven't the AT manufacturers fixed this? Do they know it's a problem? Is there anything in the PDF and/or PDF/UA spec that tells them not to have their technology have a lag at the LBL tag or force a double-tap?
I agree, AT users and others in the community should post their bugs to the manufacturers.
Where the request will fall on deaf ears. Manufacturers go by numbers and Joe or Mary's individual request gets round-filed very quickly.
One person filing a bug report has little chance of getting the error fixed...by any of our software manufacturers.
Isn't this something that the PDF Association should help with? The association would have a much better chance of being heard, and the manufacturer might even appreciate some guidance on the finer nuances of making the PDF and PDF/UA specs work for their products and their customers.
The committees that create the ISO standards (which are called "machine" specifications) are only one part of what's needed. Guides for those who program the machines are also needed. And guides for content creators who must build content that meets the specs are needed, too.
If we don't take time to educate all the stakeholders in our entire community, we end up with annoying half-baked quassi-assistive technology that forces users to double-tap through lists. And worse.
â â â
Bevi Chagnon, founder/CEO | <EMAIL REMOVED>
â â â
PubCom: Technologists for Accessible Design + Publishing
consulting ' training ' development ' design ' sec. 508 services
Upcoming classes at www.PubCom.com/classes
â â â
- Next message: Dane Dunham: "WCAG 2.0 Questions"
- Previous message: Duff Johnson: "Re: PDF/UA Quandary 1 - Bullets in LBL tags - Does this interrupt current expected screenreader flow of text?"
- Next message in Thread: Duff Johnson: "Re: PDF/UA Quandary 1 - Bullets in LBL tags - Does this interrupt current expected screenreader flow of text?"
- Previous message in Thread: Duff Johnson: "Re: PDF/UA Quandary 1 - Bullets in LBL tags - Does this interrupt current expected screenreader flow of text?"
- View all messages in this Thread