Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

aria-allowed-role fails for role spinbutton on input type tel

See original GitHub issue

Expectation: <input type="tel" role="spinbutton" /> should pass aria-allowed-role

Actual: It fails. It looks like maybe only type="text" and type="number" pass.

Motivation: Inputs of type="tel" are used frequently for inputs that need to take numerical values, including period and comma characters for decimal values. It seems to me that this should be considered a valid type for a role="spinbutton".

Issue Analytics

State:
Created 4 years ago
Comments:11 (10 by maintainers)

Top GitHub Comments

1reaction

erin-doylecommented, Feb 26, 2020

Awesome, got it, thanks! PR posted!

1reaction

erin-doylecommented, Dec 10, 2019

Yep I can put together a pull request for this. Thanks!

Top Results From Across the Web

ARIA: spinbutton role - Accessibility - MDN Web Docs

The spinbutton role indicates that the element is an input widget that restricts its value to a set or range of discrete values....

What is a role of input with type number - Stack Overflow

An input number is like a counter, so it is spinning its values up and down by clicking in the spin buttons on...

Renovate Bot Package Diff

+ - **finishRun:** handle null for failed iframe results ... Your use of this Source Code Form is subject to the terms of...

axe-core | Yarn - Package Manager

aria-allowed-role : allow role=spinbutton on inputtype=tel; color-contrast: ignore form elements that move text outside of node using text-indent (#2044 ...

Diff - chromium/src - Google Git

Revert "Reland Update axe-core to v3.3.2" This reverts commit de35a0973ddba93070fa647b5c664077cef128be. Reason for revert: Failing on all ...