Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F87 is incomprehensibly formulated #907

Open
JAWS-test opened this issue Sep 27, 2019 · 1 comment · May be fixed by #1034
Open

F87 is incomprehensibly formulated #907

JAWS-test opened this issue Sep 27, 2019 · 1 comment · May be fixed by #1034

Comments

@JAWS-test
Copy link

https://www.w3.org/WAI/WCAG21/Techniques/failures/F87

A common way to test this critieria is to disable CSS styles to view whether content added using pseudo-elements remains visible.

If CSS is disabled, this content will not remain visible. A better wording would be:

"A common way to test this critieria is to disable CSS styles to view whether the page contains content added using pseudo-elements because these are then no longer displayed."

Check that non-decorative information presented by the generated content is available when styles are overridden.

Here it remains completely unclear in which way the CSS should be overwritten. With many methods the content remains visible. Only with certain methods it becomes invisible. Therefore the method should be specified exactly or the test should be done by deactivating the CSS.

Note: CSS content is not only a problem when deactivating or overwriting CSS, but also for screenreader users:

See also: #433

@JAWS-test
Copy link
Author

JAWS-test commented Sep 28, 2019

Considering ARIA24, the test for F87 should look like removing all generated content except when it or an ancestor element has been tagged with role=img

So it could look something like this:

*:not([role="img"]):before {content:"" !important;}
*:not([role="img"]):after {content:"" !important;}

(Successfully tested with Semantically identifying a font icon with role="img" examples. However, this variant does not yet take into account the case that the generated content can occur in a descendant).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants