- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Fri, 7 Oct 2016 08:52:50 -0500
- To: Katie Haritos-Shea <ryladog@gmail.com>, AlastairCampbell <acampbell@nomensa.com>
- Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
+1. Thank you, Alastair! Kindest Regards, Laura On 10/6/16, Katie Haritos-Shea <ryladog@gmail.com> wrote: > Thanks for sharing Alistair. It looks good! > > Katie Haritos-Shea > 703-371-5545 > > On Oct 6, 2016 7:10 PM, "Alastair Campbell" <acampbell@nomensa.com> wrote: > >> Hi everyone, >> >> Good discussion today, and I'd like to summarise some of it with updates >> & >> proposals. >> >> As discussed I have merged the wording that Jason, David and I worked on >> with "Size of all content". I suggest that we call it "Resize content" to >> align with and expand on "Resize text": >> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Size_of_all_elements >> >> So the sizing related SCs would be: >> 1.4.4 Resize text (the current 200% one with no restriction on horizontal >> scrolling) >> 1.4.x Resize content (up to 400% without horizontal scrolling) >> 1.4.x Reflow to single column >> >> I think they work well together, you effectively have an SC for making >> sure zoom works without scrolling, a fall back for when that doesn't >> apply, >> and the re-flow allows for more extreme text-sizes. >> >> I'm not sure that proposed "Text size" SC adds much though, the wording >> "up to the user agent maximum without loss of content and functionality" >> isn't possible for authors to achieve. It can be achieved with user-agent >> changes such as removing styles, but then if you've removed author styles >> it isn't something the author controls. The reflow SC covers that >> scenario, >> where you need a meaningful & understandable order of content. >> >> I will read (and re-read) Wayne's Reflow SC, I understand what it's aimed >> to acheive, and it is very thorough, >> > -- Laura L. Carlson
Received on Friday, 7 October 2016 13:53:18 UTC