W3C home > Mailing lists > Public > public-wai-eo-badtf@w3.org > March 2011

Re: updated expand/collapse functionality for review

From: Wayne Dick <wed@csulb.edu>
Date: Thu, 10 Mar 2011 15:21:25 -0800
Message-ID: <AANLkTinqdr9GvFN4fjKbQd3QniN0qBKpHbckwxE7BXTP@mail.gmail.com>
To: Shadi Abou-Zahra <shadi@w3.org>
Cc: EOWG <w3c-wai-eo@w3.org>, BAD TF <public-wai-eo-badtf@w3.org>
Hi Shadi,

Here is a little more precise information.

Column bleeding starts at the break between 36x and 40px.  Bleeding is
really bad at 44px+.  That is a reasonable print size for moderate low
vision.

Also my work around in the previous note doesn't work in Firefox--
just in Safari.

You really should look at it in Firefox with the following settings:
Set all font size to between 48-72px using the tools>options>content>
[size][advanced] tool.  This would be a good setting for someone with
moderate low vision or mild legal blindness (20/70-20/400) and fair
reading functionality.

Then use view>page style>no style.

Note how the expand / collapse menu content is buried, and hard to
find in the forest of large print.  The effect is very different from
the expand all option.  Also, the expand all / collapse all button
just kind of hangs there in a weird document order.  It should be
right after or before the menu in reading order.

Now, go back to your styling, but leave the font size at 48-72px.
Also, choose any tab but Overview.  You will notice that the line:
"[DRAFT] How People with Disabilities Use the Web: ..." bleeds on
itself.  You must have used an absolute line-height on those pages.

Cheers, Wayne
Received on Thursday, 10 March 2011 23:21:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 10 March 2011 23:22:00 GMT