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

Accessible Name computation skips subtree of table with role=presentation #634

Closed
jnurthen opened this issue Dec 7, 2017 · 7 comments
Closed

Comments

@jnurthen
Copy link

jnurthen commented Dec 7, 2017

      if (!shouldNeverCheckSubtree(element) && (!role || aria.getRolesWithNameFromContents().indexOf(role) !== -1)) {
        returnText = getInnerText(element, inLabelledByContext, inControlContext);
        if (nonEmptyText(returnText)) {
          return returnText;
        }
      }

shouldNeverCheckSubtree always returns true for a table element even if it is marked with role=none|presentation so the getInnerText function never gets called.

@jnurthen jnurthen changed the title Accessible Name computation skips subtrees of table with role=presentation Accessible Name computation skips subtree of table with role=presentation Dec 7, 2017
@WilcoFiers
Copy link
Contributor

What's the use case here? Is it generating false positives anywhere?

@jnurthen
Copy link
Author

jnurthen commented Dec 8, 2017

False positives at the following URL.
http://jdevadf.oracle.com/adf-richclient-demo/faces/index.jspx
Get "Headings must not be empty" errors for each of the "accordion" headings at the left hand side.

@WilcoFiers
Copy link
Contributor

Interesting! Ok sure. If you've got the time, we'd welcome a PR for this James.

@jnurthen
Copy link
Author

I'll work on getting the CLA approvals completed. I need multiple approvals so won't be any time soon.

@WilcoFiers
Copy link
Contributor

This should be resolved by #722

@marcysutton
Copy link
Contributor

@jnurthen can you confirm if the work in #722 helps resolve this issue?

@marcysutton
Copy link
Contributor

I'm going to close this issue, as we have no way to reproduce it. Let us know if the issue still persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants