- From: Glenda Sims <glenda.sims@deque.com>
- Date: Thu, 20 Apr 2017 13:45:46 -0500
- To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
- Message-ID: <CAH2ngERyJmR_OZBMyoZS17JRJa_sGHzrtLw+YRRmAGFPLZWsZA@mail.gmail.com>
Ooooo Alastair, 1. *Where should we handle the visual affordances of native html table borders?* Your SC or mine? - We could try and stuff it in mine...but then I would have to rename my SC...because currently I just focus on active/interactive UI elements. Can we include it (in understanding and maybe a sufficient technique) for Graphics Contrast? 2. *Where should we handle the visual affordances of the upcoming "triangle" affordance for the native <details> and <summary> feature* as seen here (currently only supported by chrome) http://html5doctor.com/the-details-and-summary-elements/ - I believe it should be in mine...because it is an active/interactive UI element that will be rendered by the browser (it is not an image). Currently, the proposed "User Interface Component Contrast (Minimum)" has only been handling things that are interactive and rendered/drawn by the browser. And your proposed "Graphics Contrast" has been focused on anything that is an image provided by the author (active or static/informative). But now we need to agree how we are going to handle table borders. So...what do you think? Which SC do you think it fits best with? G glenda sims | team a11y lead | deque.com | 512.963.3773 *web for everyone. web on everything.* - w3 goals
Received on Thursday, 20 April 2017 18:46:20 UTC