-
Notifications
You must be signed in to change notification settings - Fork 235
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
Remove failure technique F87 #3818
Conversation
Rationale: this is not *always* a failure. User agent/screen reader support has improved considerably since the technique was first devised, with most (all?) combinations now happily reading/announcing CSS-generated content. Supersedes #2800 (which was having too many merge conflicts due to its age) Closes #1554, closes #3781
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did some followup discussion with other Deque folks and we're on board with removing the failure technique. We acknowledge that :before
/:after
content involves some usability issues:
- Can't Ctrl+F for it
- Can't select/copy/paste it
- Doesn't show up in some "Reader Mode" UIs (eg, Safari's)
...but we agree with points made during today's TF meetings that even though these may create usability issues, these probably don't constitute 1.3.1 failures (other acceptable 1.3.1 techniques have similar usability limitations).
I think it might be nice to add an understanding doc note or advisory technique or something that warns about the potential for usability issues, but I don't think that blocks this PR.
Rationale: this is not always a failure. User agent/screen reader support has improved considerably since the technique was first devised, with most (all?) combinations now happily reading/announcing CSS-generated content.
Supersedes #2800 (which was having too many merge conflicts due to its age)
Closes #1554, closes #3781