Allow aria-* attributes on form elements
See original GitHub issueRelated to #1635. Allows aria-*
attributes on all input
form elements and increases flexibility of accessibility.
Enable engineering use
See dataProps architecture here.
- ~Input~
- ~Button~
- Radio
- ~Checkbox~
- Colorpicker (input)
- Combobox
- Date Picker
- ~Text-area~
- Slider
Button has this working. I’m not sure why some of these are striked through.
Highlight implied prop on doc site
Add to comment paragraph above class declaration:
This component contains an
input
element. Any prop starting witharia
will be added toinput
even thougharia-*
props are not listed below.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
ARIA: form role - Accessibility - MDN Web Docs - Mozilla
The form role can be used to identify a group of elements on a page that provide equivalent functionality to an HTML form....
Read more >ARIA in HTML - W3C
WAI-ARIA identifies roles which have prohibited states and properties. These roles do not allow certain WAI-ARIA attributes to be specified by ...
Read more >Elements must only use allowed ARIA attributes | Axe Rules
Not all ARIA role-attribute combinations are valid. This Rule checks that each role is supplied with allowed attributes. The Algorithm (in simple terms)....
Read more >Improve Your HTML With ARIA Attributes - OpenClassrooms
For example, the HTML header element can also be expressed with ARIA by using role=”banner” . In other cases, they can provide information ......
Read more >Attribute “aria-required” is unnecessary for elements that have ...
The aria-required attribute is used to indicate to screen reader users that a form input is required. As there is now in HTML...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I honestly don’t remember why I striked those out. Please audit all components with
input
elements. There could be some newly added. Sorry, for the out of date issue.Yes, you are right. Button is only one implemented.
HTML
<input/>