- From: Wayne Dick <wed@csulb.edu>
- Date: Thu, 10 Mar 2011 12:44:04 -0800
- To: Shadi Abou-Zahra <shadi@w3.org>
- Cc: EOWG <w3c-wai-eo@w3.org>, BAD TF <public-wai-eo-badtf@w3.org>, Artur Ortega <ortega@yahoo-inc.com>, Sylvie Duchateau <sylvie.duchateau@snv.jussieu.fr>, Jennifer Sutton <jsuttondc@gmail.com>, Wilco Fiers <wfiers@bartimeus.nl>, Liam McGee <liam.mcgee@communis.co.uk>, Ian Pouncey <w3c@ipouncey.co.uk>, Michael Stenitzer <stenitzer@wienfluss.net>
If you get this twice, I am sorry. I am not sure who is on what list. I am having problems with using the multi-tab in very large print (>300%). The columns bleed into each other. If I linearize the page, there is so much navigational verbiage, I get lost. While the multi column format of the WAI page is not a problem with single article pages, the multi tab page becomes a problem. There are a couple of ways to address this problem: (1) Let everything float, including the primary navigation bar on the left; (2) Make the primary navigation expand/collapsable as well. While we're we could collapse that on this page box as well. Overall the expand collapse technology is good. Apple Voice Over and Safari reader mode pick it up. Just remember a person who needs enlargement wants a single column view of the main content that is sufficiently large to permit reading. Right now here is what I do to avoid a stiff neck from pressing my nose to the page. 1) I enlarge the page 200%. That works. Next because the text column doesn't take more than 50% of the page I zoom 200%. That gives me 400%. When the column widens I stop the zoom and and pump the browser zoom to 400%. That is a lot of user excise just to read the content. I hope this helps. Wayne
Received on Thursday, 10 March 2011 20:44:39 UTC