You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the big challenges with web components is how to make them accessible. We can use some ARIA features to expose the role or state of component pieces, but we are currently unable to create explicit connections that rely on id references. That means we cannot connect web components parts to the page within which they are used nor can we connect pieces of two separate components across their boundaries. We need to fix this to build truly accessible component systems.
This discussion was converted from issue #212 on December 04, 2020 22:38.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
One of the big challenges with web components is how to make them accessible. We can use some ARIA features to expose the
role
or state of component pieces, but we are currently unable to create explicit connections that rely onid
references. That means we cannot connect web components parts to the page within which they are used nor can we connect pieces of two separate components across their boundaries. We need to fix this to build truly accessible component systems.https://webwewant.fyi/wants/121/
Beta Was this translation helpful? Give feedback.
All reactions