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

aria-* and grid with filtering #465

Closed
knoobie opened this issue Sep 22, 2017 · 2 comments
Closed

aria-* and grid with filtering #465

knoobie opened this issue Sep 22, 2017 · 2 comments

Comments

@knoobie
Copy link

knoobie commented Sep 22, 2017

I hope it's allowed to ask such questions here.

The documentation for aria-rowcount states the following:

If all of the rows are present in the DOM, it is not necessary to set this attribute as the user agent can automatically calculate the total number of rows. However, if only a portion of the rows is present in the DOM at a given moment, this attribute is needed to provide an explicit indication of the number of rows in the full table.

Authors MUST set the value of aria-rowcount to an integer equal to the number of rows in the full table. If the total number of rows is unknown, authors MUST set the value of aria-rowcount to -1 to indicate that the value should not be calculated by the user agent.

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.

@jnurthen
Copy link
Member

jnurthen commented Oct 3, 2017

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?

It should be the number of rows which are in the set of results which are "displayed" in the table - so the filtered set.

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?

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

@jnurthen jnurthen closed this as completed Oct 3, 2017
@knoobie
Copy link
Author

knoobie commented Oct 4, 2017

Thank you!

mcking65 added a commit that referenced this issue Oct 29, 2017
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.
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