[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
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

Clarification requested on how to implement "not mapped" aria-sort=none for NSAccessibility's accessibilitySortDirection #239

Open
joanmarie opened this issue Oct 29, 2024 · 0 comments
Assignees

Comments

@joanmarie
Copy link
Contributor
joanmarie commented Oct 29, 2024

According to the spec, aria-sort=none for NSAccessibility is "not mapped".

But it's not clear to me how to implement that for accessibilitySortDirection, because the only available NSAccessibilitySortDirections are:

  • unknown
  • ascending
  • descending

The first of those three is the expected mapping for aria-sort=other. And an unknown sort order isn't the same thing as the known lack of a sort order (right?).

I suppose an implementation could just not support accessibilitySortDirection until the items in question become sorted. But that feels not-quite-right to me. Things that can never be sorted should of course not support accessibilitySortDirection. However, it seems like things which could be sorted and just happen to be unsorted should support accessibilitySortDirection.

Whatever the correct implementation should be, having it stated in the Core-AAM would be helpful. Guidance in the meantime would be most appreciated! Thanks in advance!

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