- From: bryan rasmussen <rasmussen.bryan@gmail.com>
- Date: Wed, 27 Mar 2024 13:57:52 +0100
- To: Phill Jenkins <pjenkins@us.ibm.com>
- Cc: WAI Interest Group discussion list <w3c-wai-ig@w3.org>
- Message-ID: <CAHKsR68TeNym695PND07x7PCsZCZeKXk0p=Xgs6FUujRj7KuBw@mail.gmail.com>
The way I read it is that meaningful content must still be maintained when
the user override happens - adapting the rules example css let's suppose
the site has the following:
p.jim q::before { content: "Jim Says: " }
p.mary q::before { content: "Mary Says: " }
But the user stylesheet has the following
q::before { content: open-quote }
q::after { content: close-quote }
then we can say that the user css overrides and destroys some meaningful
content.
which could totally be foreseen - obviously the Jim says: should be before
the p.jim
text node - the qu override shown above would be something you could expect
might happen and structuring your CSS in such a way would be improper use
of before.
Thanks,
Bryan Rasmussen
On Fri, Mar 15, 2024 at 8:01 PM Phill Jenkins <pjenkins@us.ibm.com> wrote:
> Regarding the WCAG 2.2 Technique F87:
>
> Failure of Success Criterion 1.3.1 due to inserting non-decorative content
> by using ::before and ::after pseudo-elements and the 'content' property in
> CSS
>
> https://www.w3.org/WAI/WCAG22/Techniques/failures/F87
>
>
>
> 1. Does anyone agree that F87 is no longer a valid failure technique?
> - Quote: “A common way to test [this criterion]* is to disable CSS
> styles to view whether content added using pseudo-elements remains
> visible.” Who in 2024 disables CSS anymore (and why)? Disabling CSS and
> JavaScript is not a valid “disability” test in my opinion.
> - JAWS and free screen readers VoiceOver and NVDA support reading
> the content, including non-decorative content.
> - Quote: “…they may not be able to access the information that is
> inserted using CSS” is not explained why this is still valid even when
> users load their own CSS. If they load their own CSS, they are not
> disabling CSS & JavaScript.
> 2. Can anyone provide a web example where this “testing technique”
> would uncover a real accessibility problem?
>
>
>
> The text ”this critiera” is a typo on the W3C WAI page.
>
Received on Wednesday, 27 March 2024 12:58:07 UTC