-
Notifications
You must be signed in to change notification settings - Fork 266
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
1.3.1 / F87 for input fields with mandatory visual indication via pseudo-element #3781
Comments
@JOP-Temesis I believe we need some more context to properly answer your question. Can you please provide more details or an example? In the meantime, please examine #3748 to consider whether the discussion there on the use of pseudo elements is relevant. |
I was thinking of this kind of example
I don't see in which case the styles are replaced by users who could knowingly delete the *. For me users will use custom styles via aria-required |
Sounds reasonable |
We are in the process of assessing the removal of F87 via PR #2800. |
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
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
Does the F87 fail test for the CSS override of a pseudo-element concern the case of an input field with aria-required attributes?
What are your thoughts on this?
/J
The text was updated successfully, but these errors were encountered: