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
Upon reviewing implementations for sliders which use a <button> element as its base, I have not been able to come up with any present-day reasoning as to why role=slider would not be allowed on a button. At least, not any reasoning that could not also be problematic under other testable situations / WCAG rules. E.g., if the button is given a preventDefault(), then the implicit functionality which would make this a problematic role allowance can be avoided - and that functional issue could be found via other manual checks.
proposed resolution: allow role=slider on the button element and input type=button|submit|reset|image.
The text was updated successfully, but these errors were encountered:
scottaohara
changed the title
Allow role=slider on button and input type=button elements
Update: Allow role=slider on button and input type=button elements
Feb 1, 2023
closes#444closes#395closes#298
This PR makes the allowances for button-elements (button, input type=button|image|submit|reset) more consistent with each other. Additionally, slider and gridcell are now listed under the allowed roles for these elements.
the LOE to properly create the necessary UX for some of these roles when specified, especially on the `input` type buttons, is rather large _but_ possible. Any failures to not implement these properly would be caught by WCAG rules. Allowing the roles won't change that.
* Update button and input button type allowances
closes#444closes#395closes#298
This PR makes the allowances for button-elements (button, input type=button|image|submit|reset) more consistent with each other. Additionally, slider and gridcell are now listed under the allowed roles for these elements.
the LOE to properly create the necessary UX for some of these roles when specified, especially on the `input` type buttons, is rather large _but_ possible. Any failures to not implement these properly would be caught by other WCAG rules and likely other automated checks.
* add missing slider allowance for input type=image
* add changelog
Upon reviewing implementations for sliders which use a
<button>
element as its base, I have not been able to come up with any present-day reasoning as to whyrole=slider
would not be allowed on a button. At least, not any reasoning that could not also be problematic under other testable situations / WCAG rules. E.g., if the button is given apreventDefault()
, then the implicit functionality which would make this a problematic role allowance can be avoided - and that functional issue could be found via other manual checks.proposed resolution: allow role=slider on the button element and input type=button|submit|reset|image.
The text was updated successfully, but these errors were encountered: