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

RE: Combining the sizing SCs

From: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Date: Mon, 3 Oct 2016 10:26:23 -0400
To: "'Laura Carlson'" <laura.lee.carlson@gmail.com>
Cc: "'AlastairCampbell'" <acampbell@nomensa.com>, "'WCAG'" <w3c-wai-gl@w3.org>, "'public-low-vision-a11y-tf'" <public-low-vision-a11y-tf@w3.org>
Message-ID: <0c4401d21d82$1eb26f10$5c174d30$@gmail.com>
Laura,

Thanks! So if I am correct about the requirements of 2.1....

That would mean maybe trying to combine the 2 NEW SC, Seeing All Interface Elements and Size of All Content. Leaving Resize Text as is.

​​​​​



* katie *
 
Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)
 
Cell: 703-371-5545 | ryladog@gmail.com | Oakton, VA | LinkedIn Profile | Office: 703-371-5545 | @ryladog


-----Original Message-----
From: Laura Carlson [mailto:laura.lee.carlson@gmail.com] 
Sent: Monday, October 3, 2016 10:07 AM
To: Katie Haritos-Shea <ryladog@gmail.com>
Cc: AlastairCampbell <acampbell@nomensa.com>; WCAG <w3c-wai-gl@w3.org>; public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Subject: Re: Combining the sizing SCs

Hi Katie, Alastair, and all,

I wonder if we make a new combined SC for those 2, we should fold in the current  "Seeing All Interface Elements" too. All 3 (Seeing All Interface Elements, Size of All Content, and "Text Size") seem to overlap.

Thanks,
Laura

[1] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Seeing_All_Interface_Elements

Reference  LVFT Success Criteria Progress Table:
https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Tracking_Success_Criteria_Progress

On 10/3/16, Katie Haritos-Shea <ryladog@gmail.com> wrote:
> Alistair,
>
> While this seems like a good idea, remember that 2.1 has to be 100% 
> backwards compatable (in that it will add new things, but all of the 
> old things will still be true), so it may be more complicated to so.
>
> In other words you would still have to have the Resize SC (with it 
> existing
> number) and a Resize Text plus Resize Content (with a new number). So 
> it seems best to just make the new idea, Resize Content by itself the 
> new number.
>
> We *do* want to combine all NEW SC ideas as much as we can, but 
> combining old with a new will be much harder to do, considering our 
> requirements for 2.1.
>
> Do others agree or disagree that this is consistant with one of the 
> goals of 2.1?
>
> Katie Haritos-Shea
> 703-371-5545
>
> On Oct 3, 2016 4:59 AM, "Alastair Campbell" <acampbell@nomensa.com> wrote:
>
>> Hi everyone,
>>
>>
>>
>> I’m not sure how many people track the github issues, but I added one 
>> on Friday about the sizing SCs:
>>
>> https://github.com/w3c/low-vision-SC/issues/16
>>
>>
>>
>> It covers the issues that came up at the meeting in TPAC, and 
>> proposes a replacement for Sizing All Content & Text-Sizing.
>>
>>
>>
>> I don’t have access to editing the LVTF wiki area, but it’s probably 
>> best to have a new one and copy over some of the associated text for 
>> benefits, techniques etc.
>>
>>
>>
>> Is it best to discuss on-list or on-github?
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> -Alastair
>>
>>
>>
>> --
>>
>>
>>
>> Alastair Campbell
>>
>>
>>
>> www.nomensa.com
>>
>> tel: +44 (0)117 929 7333 / 07970 879 653
>>
>> follow us: @we_are_nomensa or me: @alastc
>>
>>
>>
>> Nomensa Ltd. King William House, 13 Queen Square, Bristol BS1 4NT
>>
>> Company number: 4214477 | UK VAT registration: GB 771727411

--
Laura L. Carlson
Received on Monday, 3 October 2016 14:26:58 UTC

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