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

1.3.1 / F87 for input fields with mandatory visual indication via pseudo-element #3781

Closed
JOP-Temesis opened this issue Apr 12, 2024 · 4 comments · Fixed by #3818
Closed

Comments

@JOP-Temesis
Copy link

JOP-Temesis commented Apr 12, 2024

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

@mbgower
Copy link
Contributor

mbgower commented Apr 12, 2024

@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.

@JOP-Temesis
Copy link
Author

I was thinking of this kind of example
where the mandatory field indication is in a content css and the input field with aria-required="true".

<label for="xx">my label <span>::before</span></label> #CSS content : "*";
<input type="text" id="xx" aria-required="true">

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

@anevins12
Copy link
Member

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

@mbgower
Copy link
Contributor

mbgower commented May 3, 2024

We are in the process of assessing the removal of F87 via PR #2800.
I have marked this issue to be closed if that is incorporated. If you are concerned with that approach, please comment.

@mbgower mbgower mentioned this issue May 3, 2024
patrickhlauke added a commit that referenced this issue May 4, 2024
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
mbgower pushed a commit that referenced this issue Jun 12, 2024
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants