W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > October 2016

Re: Sizing SCs - post informal meeting

From: Katie Haritos-Shea <ryladog@gmail.com>
Date: Thu, 6 Oct 2016 19:32:06 -0400
Message-ID: <CAEy-OxFNhxLoU7Cyyht=H6PcDi=pUv_YUW_B4rDN0twr8QM=0Q@mail.gmail.com>
To: AlastairCampbell <acampbell@nomensa.com>
Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Thanks for sharing Alistair. It looks good!

Katie Haritos-Shea

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,
Received on Thursday, 6 October 2016 23:32:35 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 April 2017 14:44:31 UTC