E-mail List Archives
Re: WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker.
From: Philip Kiff
Date: Dec 15, 2023 3:41PM
- Next message: Laura Roberts: "Re: WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker."
- Previous message: Philip Kiff: "Re: WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker."
- Next message in Thread: Laura Roberts: "Re: WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker."
- Previous message in Thread: Philip Kiff: "Re: WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker."
- View all messages in this Thread
Quick follow-up. If you created your Span following the instructions
provided by the W3C Example #1, then definitely double-check that your
Span is properly nested within a block tag.
I finally figured out how to follow their instructions and create a Span
that way [eye roll], but it dropped the new Span into the root of the
Document, which may produce the error about "possibly inappropriate" use
of a Span structure element. If this happens to you, then you would then
need to move the Span back to where you actually want it.
The method I described using the Reading Order tool will preserve the
tag placement better in both the Tag tree and in the Content panel,
though it requires manual editing of the tag afterwards.
Phil.
On 2023-12-15 5:02 p.m., Philip Kiff wrote:
> I just did a quick test on a sample doc and was able to add expansion
> text to a Span tag and then pass PAC 2021 and PAC 2024 cleanly. So I'm
> not sure that the example or the PAC 2024 are wrong.
>
> Though the W3C instructions for creating a new Span tag didn't work
> for me using Acrobat Pro DC: I created the Span tag by using the
> "Reading Order" tool, selecting the text, marking it as a Paragraph,
> and then manually editing the tag properties and changing it from
> Paragraph to Span using the "Accessibility Tags" panel. THEN I added
> the Expansion Text in the Content tab of the Object Properties.
>
> The error message you quote often pops up when there is an issue with
> the "Placement" attribute of a tag: especially when an "inline" tag is
> placed at the root level, or when a "block" tag is placed within
> another "block" tag incorrectly. Normally a Span tag has an "inline"
> placement and it must be nested within a tag/container with a "block"
> placement. I wonder if somehow your Span tag has the wrong placement
> attribute?
>
> Phil.
>
> On 2023-12-15 3:00 p.m., Laura Roberts wrote:
>> Â 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?
>>
> > > >
- Next message: Laura Roberts: "Re: WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker."
- Previous message: Philip Kiff: "Re: WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker."
- Next message in Thread: Laura Roberts: "Re: WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker."
- Previous message in Thread: Philip Kiff: "Re: WC3 Example #1 of tagging acronym expansion text yields a yellow warning on the PAC checker."
- View all messages in this Thread