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

Investigate utilities to simplify a11y for WebComponents #3

Open
rodneyrehm opened this issue Dec 27, 2014 · 0 comments
Open

Investigate utilities to simplify a11y for WebComponents #3

rodneyrehm opened this issue Dec 27, 2014 · 0 comments

Comments

@rodneyrehm
Copy link
Member

With Custom Elements on the rise and the specification itself promoting the use of WAI-ARIA it is even more important to make this stuff as simple as possible.

The <taco-button> example illustrates how disabling a role="button" is supposed to work: by removing tabindex, onclick, onkeypress and adding aria-disabled="true" - that is a lot of DOM action necessary to compensate for something otherwise as simple as <button … disabled>.

It looks like form element semantics like [disabled] and :disabled will be available to Type Extensions (<input … is="my-cool-thing">) only.

@rodneyrehm rodneyrehm added this to the v0.3.0 - WAI-ARIA milestone Dec 27, 2014
@rodneyrehm rodneyrehm removed this from the v0.3.0 - WAI-ARIA milestone Aug 22, 2015
@rodneyrehm rodneyrehm added research and removed test labels Dec 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant