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-sort recommendation to have it only on ONE header #582

Closed
DavidMacDonald opened this issue May 17, 2017 · 8 comments
Closed

aria-sort recommendation to have it only on ONE header #582

DavidMacDonald opened this issue May 17, 2017 · 8 comments
Assignees
Labels
Milestone

Comments

@DavidMacDonald
Copy link

DavidMacDonald commented May 17, 2017

This sentence on aria-sort is a bit confusing.

For each table or grid, authors should apply aria-sort to only one header at a time.

It seems its saying add the attribute when the column is sorted and remove it completely if another column is sorted. I think that is a strange request. Usually in aria we swap out values rather than remove the whole attribute when things change. Perhaps say something like this:

For each table or grid, authors should apply only one of the following at a time

  • aria-sort="ascending"
  • aria-sort="descending"
  • aria-sort="other"

The remaining headers should either have aria-sort="none" or should not have the attribute.

@joanmarie
Copy link
Contributor

At the risk of spawning a discussion (somewhat) beyond the scope of the opening report and (definitely) beyond the scope of ARIA 1.1: I'm not sure we want to restrict sorting to only one header. Spreadsheets and other interactive tables in native/desktop apps allow for multiple sort columns; why should web apps be any different?

@hartman
Copy link

hartman commented May 31, 2017

Was just going to say the same thing. Ordering a table by multiple columns in sequence is not uncommon at all (and used by most spreadsheet programs). Having said that, is there any screenreader that supports keeping track of the sort state of a table that way ?

I guess you could have a live region or something pronounce the current order: "Table 1, 8 columns 200 rows, is ordered by column 2 ascending, column 3 descending" then when you order by column 6: "Table 1, 8 columns 200 rows, is ordered by column 2 ascending, column 3 descending, column 6 ascending"

@tmorehouse
Copy link

It would also be nice to have an aria-sort-order="#" attribute (indexed from 1 upwards) that would signify which columns are sorted first, then second, etc, when sorting multiple columns, or an attribute placed on the table that lists the column indexes (comma separated) of the current columns sort order.

@jnurthen jnurthen added this to the ARIA 1.3 milestone Nov 29, 2018
@jnurthen
Copy link
Member

@jnurthen jnurthen removed the Agenda label Nov 29, 2018
@DavidMacDonald
Copy link
Author

Reading through the minutes. Should this get a 1.3 label?

@jnurthen

@jnurthen
Copy link
Member

It has a 1.3 Milestone already - we don't use labels for release tracking.

@zelliott
Copy link

zelliott commented Oct 9, 2019

Can W3C provide any guidance on the referenced question above? (w3c/aria-practices#1192)

@jnurthen
Copy link
Member

jnurthen commented Mar 4, 2021

#283

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Table and Grids
  
Closed
Development

No branches or pull requests

7 participants