Resize content - questions remaining

Hi everyone,

To make the most of the time in the call, I suggest focusing on a couple of key questions that are blocking progress:


1.       The level of Resize content vs the current Resize text

The Resize content SC has a broad exception for content which needs to be two dimensional, such as data tables. Due to the exception it useful to still have an SC like 1.4.4 which requires 200% but no prohibition on scrolling. Personally, I would like to adjust the current 1.4.4 to align with the new SC so that:


a)       Level A: Cater for a 200% increase in text-size and allow horizontal scrolling (current SC at different level).

b)       Level AA: Cater for 400% increase in content without horizontal scrolling, with exception for 2D content (new SC)

Could people live with increasing the level of 1.4.4, or should we (confusingly) make them both AA?


2.       Testability on it’s face.

Currently the test process includes: Start with a browser width of 1280px and increase with zoom to 400%.  If you take any arbitary width of browser window you will get different results due to the inclusion on no-horizontal scrolling compared with 1.4.4.

I’m surprised no-one has asked about this until Jake this week, but the other option is to rephrase it to something like:
“Content can be resized to fit 320 CSS pixels wide without loss of content or functionality, and without requiring scrolling in the direction of text except for parts of the content where fixed spatial layout is necessary to use or meaning.”

Ironically that *looks* more technology specific, although the effect is exactly the same.

Are people concerned about specifying the exact test criterial in the understanding document?


Other issues, just so people know I’m not ignoring things:

-          I’ve answered most comments here: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Resize_content_issues_review


-          I need to create a definition for “fixed spacial layout” for the SC.

-          GregL brought up a point about single-line edit controls that I’m considering that at the moment.

Kind regards,

-Alastair

--

www.nomensa.com<http://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