RE: Sortable tables how to design/ describe icons for not sorted/ ascending/ descending

Marc, the opportunities are in WCAG 2.2 and the next version of the Accessibility Guidelines code named Silver.  I would like to see these types of situations including visual affordances addressed somehow.  The WAI has a WCAG github page where they track issues and feedback and where you can provide additional comments and suggestions for wording of user needs, etc.
https://github.com/w3c/wcag

Beyond WAI many of us do raise these types of questions when working with customers during design and when creating design systems.

Jonathan

From: Marc Haunschild <haunschild@mhis.onmicrosoft.de>
Sent: Friday, May 3, 2019 10:33 AM
To: Jonathan Avila <jon.avila@levelaccess.com>
Cc: w3c-wai-ig@w3.org
Subject: Re: Sortable tables how to design/ describe icons for not sorted/ ascending/ descending

WARNING: The sender of this email could not be validated and may not match the person in the "From" field.
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Jonathan,

thank you very much for your answer - so this is why i didn’t find any examples nor explanations.

Just a short explanation: We in Germany have something similar to the WCAG which is mainly a translation of the WCAG (Level AA), but with differences and without all the explanations. To make things worse, there is a compliance test, which tests things, that never had been in the WCAG nor in our own version.

That is sometimes confusing. But they made it more and more similar to the WCAG and the strangest thing about this similar but not identical thing called BITV is, that it still exists…

Anyway, I hoped to find some inspiration for how to improve the table, so it is less confusing and easier to access. But if it’s not in the WCAG there is no „How to meet the success criterion“ or something like this…

If you or anybody else has an idea or tipp for further reading, I would appreciate this.

Marc




Am 03.05.2019 um 15:51 schrieb Jonathan Avila <jon.avila@levelaccess.com<mailto:jon.avila@levelaccess.com>>:

My personal opinion is that there are 2 potential issues.


  *   There is no WCAG A or AA requirement for icons having a visual description.
  *   Icons can be used in different way to indicate the current state or a change in state.  This is a longstanding issue and can also affect screen reader users as well.    I’ve seen many mute icons in web presentation software where I can’t tell if it’s muted or unmuted because the state of the mute button is not clear – e.g. a grayed mute button with a line.    Seems muted – but when clicking it turns red and as well.  Which state is which?  There is no WCAG requirement related to this as well.

Jonathan

Jonathan Avila, CPWA
Chief Accessibility Officer
Level Access
jon.avila@levelaccess.com<mailto:jon.avila@levelaccess.com>
703.637.8957 office
Visit us online:
Website<http://www.levelaccess.com/> | Twitter<https://twitter.com/LevelAccessA11y> | Facebook<https://www.facebook.com/LevelAccessA11y/> | LinkedIn<https://www.linkedin.com/company/level-access> | Blog<http://www.levelaccess.com/blog/>

<image002.jpg><https://levelaccess.com/state-of-digital-accessibility-2019>

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

From: Mhis-Archiv <haunschild@mhis.de<mailto:haunschild@mhis.de>>
Sent: Friday, May 3, 2019 5:06 AM
To: w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Subject: Sortable tables how to design/ describe icons for not sorted/ ascending/ descending

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Although I'm already for a long time making websites accessible, there still sometimes are problems and questions, that I would like to hear other peoples opnion about.
Today I have a question about sortable tables. I found an example by Heydon Pickering (see link below) and I understand, that there is a aria-sort for screenreader users, but as a seeing person, I find it confusing, that the arrow up (for ascending) results in values, where the lowest is on the top (which is logically right, because you start reading at the top, so the higher values are coming one after another and the highest should stand according to natural reading direction at the bottom - but why the arrow shows up? To me this implicitly means, the highest value should be on the top).

So this brings me to a demand from former german accessibility testing, where every icon should have a visible text alternative. Is there something similar in the WCAG (I can't find it)?

What is your opinion? And how would you provide this text? Honestly I have no idea where to put a text in this example table for people who can see...

Also I don't know what to do with the button itself. When coming to this table for the first time, of course all the buttons are "not pressed", but after one of them has been pressed once, you can change this particular button only from "pressed" (ascending) to also "pressed" (but descending). So first you toggle the button from "not pressed, not sorted" to "pressed, ascending" and with the next click not back to "not pressed, not sorted", but to "still pressed, descending".

Also confusing (this time for screen reader users).

So for me this example (which is already the best, taht I have found) still does not solve all issues for me and I would really appreciate any suggestion to improve it!


--
Mit freundlichen Grüßen

Marc Haunschild
www.mhis.de<http://www.mhis.de/>