WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker.

for

From: chagnon@pubcom.com
Date: Dec 15, 2023 2:28PM

Which version of PAC are you using?

The software is now back in the hands of its original developers (yes!) and PAC 2024 has been released. Download from https://support.axes4.com/hc/en-us/articles/7371921627794-PDF-Accessibility-Checker-PAC-2024 .

If PAC is flagging an error, you might want to contact axes 4 directly and let them know about it. They are super-concerned about making PAC the best checker tool around!

— — —
Bevi Chagnon | Designer, Accessibility Technician | <EMAIL REMOVED>
— — —
PubCom: Technologists for Accessible Design + Publishing
consulting • training • development • design • sec. 508 services
Upcoming classes at www.PubCom.com/classes
— — —
Latest blog-newsletter – Simple Guide to Writing Alt-Text

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Laura Roberts
Sent: Friday, December 15, 2023 3:01 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [WebAIM] WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker.

From WC3 on tagging acronyms:
https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF8.html#:~:text=In%20a%20tagged%20PDF%20document,create%20a%20new%20Span%20tag
.

Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker.
The warning is: Possibly inappropriate of a span structure element.

If you don't use the span tag at all for the word, then the screen readers read the expansion text just fine and you get no PAC errors.

Anyone have some insight into this?

--
Best regards,
Laura Roberts
413-588-8422