FW: [w3c/wcag21] Understanding non-text contrast needs to allow for visible alternative text (#861)

Please read the below issue that would change what’s written for non-contrast.  Consider commenting.

Jon

Jonathan Avila
Chief Accessibility Officer
Level Access
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/>

Looking to boost your accessibility knowledge? Check out our free webinars!<https://www.levelaccess.com/compliance-resources/webinars/>

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: David MacDonald <notifications@github.com>
Sent: Tuesday, April 10, 2018 12:02 PM
To: w3c/wcag21 <wcag21@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [w3c/wcag21] Understanding non-text contrast needs to allow for visible alternative text (#861)


  *   We need an explanation that a tooltip visible on hover/focus that contains alt text would be sufficient
  *   We need an explanation that a graph with a table below it implemented with or without show/hide will be sufficient.

The text would need to be discoverable or visible without assistive technology showing up on hover, focus or activation (as in a show hide button). The reason they pass is because with these alternatives the graphic is no longer necessary to understand the content and therefore not necessary.

These two examples are important and Alex Li of Microsoft want to ensure these are in. I support this, and on the call the consensus appears that it is unanimous.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/w3c/wcag21/issues/861>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFYSM1SzAjdZdo8A5XCGgHHJualbcbPUks5tnNeEgaJpZM4TOjZO>.