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: Joshua Hori
Date: Dec 15, 2023 3:02PM

Hello Laura,

That’s the only time WCAG is used on the document, so putting a span over it would indeed be correct. You can tell the checker to ignore in this case.

Sometimes the document may start off with Web Content Accessibility Guidelines (WCAG). If this is the case, the span is unnecessary and should be marked with a yellow notification area for manual review. Manual review should see that as an accessibility error and remove the span.

Best,

Joshua

From: WebAIM-Forum < <EMAIL REMOVED> > on behalf of Laura Roberts < <EMAIL REMOVED> >
Date: Friday, December 15, 2023 at 12: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