-
Notifications
You must be signed in to change notification settings - Fork 355
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
aria-* and grid with filtering #465
Comments
It should be the number of rows which are in the set of results which are "displayed" in the table - so the filtered set.
It should be re-calculated. Good question about the header and footer. Header rows should be included. See Example 3 at https://w3c.github.io/aria-practices/examples/grid/dataGrids.html |
Thank you! |
For issue #465, in aria-practices.html, revised rough draft of the sections covering aria-colcount, aria-rowcount, aria-colindex, and aria-rowindex. 1. Grouped rowindex and row count together. 2. Grouped colcount and colindex together. 3. Added information about valid value restrictions. 5. Added warning about impact of invalid or missing values. 6. Swapped out example for contiguous columns (used the one from the spec). 7. General editorial cleanup.
I hope it's allowed to ask such questions here.
The documentation for aria-rowcount states the following:
The 'full table' kinda raises questions for me.
How do we proceed if the table can be filtered? Should the aria-rowcount be changed depending on the applied filter by the user or should it always remain where it was without a filter added?
The same goes for aria-rowindex, should it be re-calculated after a filter was applied? Or should the aria-rowindex change depending on the aria-sort? Should rows in the header and footer included in this as well?
Thank you for your time! I would love to implement it 'right' so it won't cause problems for our sightless users.
The text was updated successfully, but these errors were encountered: