- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Mon, 16 May 2016 07:59:03 +0000
- To: Wayne Dick <wayneedick@gmail.com>
- CC: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>, "Patrick H. Lauke" <redux@splintered.co.uk>
- Message-ID: <0D65C438-D740-455A-BAFB-37911BBB922C@nomensa.com>
Hi Wayne, I agree that that it should be relative/proportional, but the current definition in WCAG2 uses points which some people assume are absolute sizes, and some confuse with pixels leading to smaller text being used. Item 3 on the survey this week is to ask whether we can change the notes under the definition. I.e. is it an editorial change or is it more substantive. I would argue that it is editorial because it brings the explanation closer to reality and doesn’t change the definition, but I guess that’s a discussion for the call. Once that’s decided, we can look at how much explanation is needed. Cheers, -Alastair From: Wayne Dick <wayneedick@gmail.com> I don't care what units are used. With regard to contrast minimum, relative size is the key. Normally the browser will provide a pretty usable font size for running text. So, that size is small. 1.5. Why unit of measure is unimportant. Users don't know typographic or web font units. The print is legibility or not. Developers know and care and they should be able to choose their units. Users need to modify size to support legibility. They really need to choose bigger/smaller. The content or UA can enable resize in what ever units the developer or UA wants. When this is done proportionally the minimum contrast proportions will be preserved. If we eventually enable users to change presentation at the element level, they they will probably resize at different rates, but pick their own colors and contrast. Anyway we slice it the unit of measure should be up to the developer and large vs. small should be a proportion. I think that really does it. Wayne
Received on Monday, 16 May 2016 07:59:36 UTC