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

Selectors can be plain language and not needed to be CSS Selector #70

Closed
moekraft opened this issue Mar 15, 2017 · 0 comments
Closed

Selectors can be plain language and not needed to be CSS Selector #70

moekraft opened this issue Mar 15, 2017 · 0 comments

Comments

@moekraft
Copy link
Collaborator

From Jonathan Avila comments on survey, https://www.w3.org/2002/09/wbs/93339/ACTFrameworkFPWD/results

"The reliance on CSS selectors is an over simplification of accessibility issues. Many things can be impacted by added ARIA roles that change the meaning of the element. In addition, ancestor elements can not be determined by CSS selectors. Also things like not in this set and not in this or in this set and also in this set can't be done with CSS selectors (although the could be done in a JQuery selector). While selectors are very important to the process there are some limitations that must be acknowledged. This should be acknowledged in the sections that refer to their use." - Jonathan Avila

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

2 participants