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

fix false positive related to role="combobox" #160

Closed
dylanb opened this issue Jan 8, 2016 · 7 comments
Closed

fix false positive related to role="combobox" #160

dylanb opened this issue Jan 8, 2016 · 7 comments
Labels
fix Bug fixes rules Issue or false result from an axe-core rule

Comments

@dylanb
Copy link
Contributor

dylanb commented Jan 8, 2016

Has been reported in dequelabs/axe-firefox-devtools#33

@dylanb dylanb added fix Bug fixes rules Issue or false result from an axe-core rule labels Jan 8, 2016
@dylanb dylanb changed the title ARIA required role false positive fix false positive related to role="combobox" Jan 29, 2016
@dylanb
Copy link
Contributor Author

dylanb commented Jan 29, 2016

The solution should be the following:

If the element on which the role has been placed is a native input element, then make the required children optional

@WilcoFiers
Copy link
Contributor

I raised this issue on html-aria and Steve Faulkner got back on it. We have a different issue. Axe has two 'types' of 'owned' propertyes, 'all' and 'one'. All means every one of the roles is required, one means just one of them. ARIA doesn't actually ever require all children to be present. combobox is the only role in Axe which is set to require multiple children. Other uses of 'all' only has one role.

The fix is to change this to 'one'. Though I think it's probably better to also remove this difference all together as it adds unnecessary complexity.

@dylanb
Copy link
Contributor Author

dylanb commented Jan 29, 2016

If there is a combobox implementation that does not use a standard input element and also does not have a textbox child, then this will have severe compatibility issues when a screen reader is turned on.

For that reason, I think we should still raise the issue if there is no native element (note: this would be a temporary solution until the issue gets resolved in ARIA).

@johncaseysmith
Copy link

Hey @dylanb, any updates on this? Does the previously mentioned solution still apply?

@adamliptrot-oc
Copy link

Hi, what's the current situation with this? I'm running into this issue with automated testing.

@isner
Copy link
Contributor

isner commented Aug 9, 2017

Proposed solution: #481

marcysutton pushed a commit that referenced this issue Aug 9, 2017
…mbobox missing textbox

Remove textbox from the list of missing roles when checking a combobox node that is a native input element

#160
marcysutton pushed a commit that referenced this issue Aug 9, 2017
…mbobox missing textbox

Remove textbox from the list of missing roles when checking a combobox node that is a native input element

#160
@marcysutton
Copy link
Contributor

Fixed with #481.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix Bug fixes rules Issue or false result from an axe-core rule
Projects
None yet
Development

No branches or pull requests

6 participants