You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been looking into various html controls presented by wcomponents it has come to my attention that the table headers for sortable columns should have the role="button" as this is a typical mark up for screen readers.
Thanks @SteveHarney . When the last update was made to the table HTML column sorting was intrinsic to the th element column header when the table had the sortable attribute. That attribute has been dropped from 5.2 so we will have to update the table.
I am not convinced the th element is the right place for a role of button as that would remove its intrinsic role of columnheader but you are right, we should make explicit the interactive nature of the sort function in some way.
It appears that WAI-ARIA authoring practices suggest use of role grid on a table which is interactive and no role on sortable column headers - instead the use of property aria-sort implies a sortable column. This will still require rewriting the table HTML and providing an implementation of keywalker to comply but will not require role masking.
See https://www.w3.org/TR/wai-aria-practices-1.1/examples/grid/dataGrids.html#ex2_label for an example.
The aria-sort does not indicate sortable, but rather that the data has been sorted. the example provided actually still uses role="button" on a span inside the TH.
I have been looking into various html controls presented by wcomponents it has come to my attention that the table headers for sortable columns should have the role="button" as this is a typical mark up for screen readers.
This is a snippet generated from from 1.5.23
The text was updated successfully, but these errors were encountered: