W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

Re: Accessibility st AFB.org's AccessWorld

From: Chaals McCathieNevile <w3b@chaals.com>
Date: Fri, 10 Aug 2012 15:45:13 +0200
Cc: "'WAI Interest Group'" <w3c-wai-ig@w3.org>, "Crista Earl" <cearl@afb.net>, "Lee Huffman" <lhuffman@afb.net>, "Aries Arditi" <arditi@verizon.net>, rcole@jgb.org
To: "GF Mueden@" <gfmueden@verizon.net>
Message-ID: <op.witu5nss22x22q@chaals.local>
On Fri, 10 Aug 2012 14:11:47 +0200, GF Mueden@ <gfmueden@verizon.net>
wrote:

> Thank you, Chaas.  Close but no cigar.   The needs of those with limited  
> visual fields are not met by full screen width accessibility.

Ah, sorry, I'd misunderstood the requirement :)

> They need a narrow column.

Right.

> That calls for pulling in the margins and having word wrap within those  
> margins.  This can be done, is in wide use, but is it covered in the  
> guidelines?

Not easily. As close as you get directly is:

1.4.8 Visual Presentation: For the visual presentation of blocks of text,
a mechanism is available to achieve the following: (Level AAA)
[...]
   2. Width is no more than 80 characters or glyphs (40 if CJK).

which isn't necessarily enough. :(

Time to raise an issue for WCAG 3?

Cheers

> ===gm===
>
> On 8/10/2012 6:25 AM, Chaals McCathieNevile wrote:
>> On Fri, 10 Aug 2012 12:01:42 +0200, GF Mueden@ <gfmueden@verizon.net>  
>> wrote:
>>
>>> Hi all.
>>>
>>> The August issue of AccessWorld, reading the editorial, my old eyes  
>>> were the width of the lines away from the screen.  I pulled in the  
>>> margins to get a shorter line, but it truncated the lines.  It should  
>>> have had word wrap for the benefit of those with limited visual field.
>>
>> How did you pull in themargins? Which browser were you using?
>>
>> I zoomed the text in Opera Next (I'm a poet, but it is hard to realise)  
>> and the words got wrapped to maintain the layout - up to a certain  
>> amount of zoom which I guess was more than 200%.
>>
>>>   Is this problem covered in the guidelines?  Where should AFB be  
>>> looking?
>>
>> There are a couple of relevante requirements:
>>
>> 1.4.4 Resize text: Except for captions and images of text, text can be  
>> resized without assistive technology up to 200 percent without loss of  
>> content or functionality. (Level AA)
>>
>> and
>>
>> 1.4.8 Visual Presentation: For the visual presentation of blocks of  
>> text, a mechanism is available to achieve the following: (Level AAA)
>> [points 1-4 are not relevant]
>>   5. Text can be resized without assistive technology up to 200
>>      percent in a way that does not require the user to scroll
>>      horizontally to read a line of text on a full-screen window.
>>
>> This is not exactly brilliant, but it does cover what you are asking  
>> for.
>>
>> cheers
>>
>> Chaals
>>
>


-- 
Chaals - standards declaimer
Received on Friday, 10 August 2012 13:45:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:30 UTC