- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Wed, 12 Dec 2018 12:38:29 +0000
- To: "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
> I know it's much more involved, but: could we just mock up some of these examples as actual live examples (i.e. "THIS is the sort of thing I mean here...is this covered by the SC or not?") The new doc has quite a few in, and here are some others that came up during the github / webaim threads: 1. Boundaries https://alastairc.ac/tests/wcag21-examples/non-text-contrast.html Examples 7, 10, 12a, 16. 2. "States do not have to be differentiated within the component" Jared did some examples of button hover styles here: https://webaim.org/temp/1-4-11examples.htm I did something similar for focus styles: https://alastairc.ac/tests/wcag21-examples/ntc-focus-styles.html NB: List of potential link states: http://blog.selfthinker.org/2011/07/10/trick-question-how-many-link-states-can-be-defined-in-css/ 3. "Functional / value states do require differentiation via ‘adjacent’ background." https://alastairc.ac/tests/wcag21-examples/non-text-contrast.html Examples 2 (if it were actual tabs), 13, 17. Other examples welcome... Also, a better way of terming "functional states" would be great. A way to differentiate link-only states (visited) from those which convey a value in the name/role/value sense like checkboxes. -Alastair
Received on Wednesday, 12 December 2018 12:38:55 UTC