Skip to content

Remove redundant UA CSS requirement #2531

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.

Sign up for GitHub

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

Jump to bottom
Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Remove redundant UA CSS requirement #2531

wants to merge 2 commits into from

Conversation

@scottaohara
Copy link
Member

@scottaohara scottaohara commented May 10, 2025 •
edited by pr-preview bot
Loading

closes #2521

removes the following from the spec:

If a CSS selector includes a WAI-ARIA attribute (e.g.,
input[aria-invalid="true"]
), user agents MUST update the visual display of any elements matching (or no longer matching) the selector any time the attribute is added/changed/removed in the DOM.

as CSS already defines how UAs are to handle element/attribute selectors

Preview | Diff

@scottaohara
Remove redundant UA CSS requirement
2d13c7e 
closes #2521

removes the following from the spec:
>If a CSS selector includes a WAI-ARIA attribute (e.g.,
input[aria-invalid="true"]
), user agents MUST update the visual display of any elements matching (or no longer matching) the selector any time the attribute is added/changed/removed in the DOM.

as CSS already defines how UAs are to handle element/attribute selectors
@netlify
Copy link

netlify bot commented May 10, 2025 •
edited
Loading

✅ Deploy Preview for wai-aria ready!

Name Link
🔨 Latest commit 09e6f26
🔍 Latest deploy log https://app.netlify.com/sites/wai-aria/deploys/681f61ef184a240008a2add9
😎 Deploy Preview https://deploy-preview-2531--wai-aria.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@scottaohara
Copy link
Member Author

scottaohara commented May 10, 2025

i know the issue is marked for discussion in an upcoming ARIA editor's meeting. We can discuss this PR / what may need to change about it then as well. cc @pkra

@pkra
Copy link
Member

pkra commented May 12, 2025

If we remove this, we should also remove the normative statement in 8.7.

I think it would be good to keep a note on the general topic anyway, with a link to somewhere in CSS where these normative statements are made.

I put it on the editors' agenda because I've been wondering about what "supporting host languages" means these days, i.e. what does ARIA expect from a "supporting host language"?

@pkra pkra self-assigned this May 15, 2025
@pkra
Copy link
Member

pkra commented May 15, 2025

From our conversation: I'll update the PR to rewrite the second occurrence to make a reference https://drafts.csswg.org/selectors/#attribute-selectors (via xref https://respec.org/xref/?term=attribute+selector).

@scottaohara scottaohara marked this pull request as draft May 15, 2025 13:44
@spectranaut spectranaut moved this from All PRS to Draft in ARIA Normative PR Tracking Jun 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@pkra pkra

Labels

spec:aria

Projects

ARIA Normative PR Tracking
Status: Draft

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Duplicates requirements of Selectors

3 participants

@scottaohara @pkra