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

Reference Target for Cross-Root ARIA #356

Open
keithamus opened this issue May 29, 2024 · 3 comments
Open

Reference Target for Cross-Root ARIA #356

keithamus opened this issue May 29, 2024 · 3 comments
Assignees
Labels
topic: accessibility Spec relates to accessibility topic: html Spec relates to HTML (Hypertext Markup Language) topic: web components

Comments

@keithamus
Copy link
Member

WebKittens

@annevk @cookiecrook

Title of the spec

Reference Target for Cross-Root ARIA

URL to the spec

https://github.com/WICG/aom/blob/gh-pages/reference-target-explainer.md

URL to the spec's repository

https://github.com/WICG/aom

Issue Tracker URL

No response

Explainer URL

No response

TAG Design Review URL

No response

Mozilla standards-positions issue URL

mozilla/standards-positions#1035

WebKit Bugzilla URL

No response

Radar URL

No response

Description

Reference Targets allow forwarding IDREFs to members of the ShadowDOM which will make it signficantly easier to create web components which rely on ARIA (which itself heavily relies on IDREFs).

The Web Components Community Group considers this a pivotol feature.

@annevk
Copy link
Contributor

annevk commented May 30, 2024

I think some relationships should be implicit as we don't want to regress on how label works today: WICG/aom#209.

Overall though I like the direction this is going in.

cc @rniwa

@annevk annevk added topic: accessibility Spec relates to accessibility topic: html Spec relates to HTML (Hypertext Markup Language) topic: web components labels May 30, 2024
@Westbrook
Copy link

Now that w3c TAG has blessed phase 1 of this API and Chromium is moving into experimentations with it, when do you think can we expect to hear positioning from Webkit on this API?

@annevk
Copy link
Contributor

annevk commented Nov 20, 2024

People are generally excited about this solving a set of a11y problems with shadow roots, but generally we only take a position once there's more formal specification text to review. @LeaVerou's concern around non-ARIA attributes is also quite interesting. Was that addressed anywhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: accessibility Spec relates to accessibility topic: html Spec relates to HTML (Hypertext Markup Language) topic: web components
Projects
None yet
Development

No branches or pull requests

4 participants