- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Tue, 30 Jan 2018 23:11:49 +0000
- To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Interesting comments on a thread that started with a Chrome test for text-contrast: https://twitter.com/kevinmarks/status/958320468322287617 Kevin Marks made the point that WCAG adjusts for thick (bold) text, but not thin text, and included a link to some research about it: https://t.co/BCsmGTCf6k (PDF, probably doesn't reflow very well :-/ ) This is a good illustration: https://kevinmarks.github.io/colourandcontrast.html So it occurs to me that might be a good SC for after 2.1 (I'd rather an update, but it would probably have to be a new requirement.) That research was for general population rather than low-vision users, so we'd need to find (or conduct) some disability specific research. He suggested finding some participants from the comments here: https://medium.com/backchannel/how-the-web-became-unreadable-a781ddc711b6 Possibly not an ethical way to source participants, but I don't have the kit for this kind of research anyway! -Alastair
Received on Tuesday, 30 January 2018 23:12:50 UTC