- From: Wayne Dick <wayneedick@gmail.com>
- Date: Wed, 1 Feb 2017 16:38:16 -0800
- To: "Sean Murphy (seanmmur)" <seanmmur@cisco.com>
- Cc: Glenda Sims <glenda.sims@deque.com>, W3C WAI ig <w3c-wai-ig@w3.org>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>, Jim Allan <jimallan@tsbvi.edu>, Joshue O Connor <josh@interaccess.ie>, Andrew Kirkpatrick <akirkpat@adobe.com>
- Message-ID: <CAJeQ8SB=HdNgm2LCzN8oe+QcJW__eHoAcJ=rvCHQH9_6rGdfQA@mail.gmail.com>
Dear Sean, That is correct, but effective accommodation doesn't really begin until you reach 300% (or you narrow the width of the field to about 1/30. The number 200% is a leftover from the paper era. It was almost impossible to create large print books at more than 200%. It just took too much paper. You still find well meaning sites like the American Printing House for the Blind that recommend using Braille if you need 280%. Since WCAG 2.0, responsive web design has demonstrated the ability to enlarge by up to 500%. I requires a little arithmetic to see this. When we transform a site that looks good on a 13 inch laptop to a 4.7 inch phone we accommodate for 2 shrinking processes. Reduction of width, and rotation to portrait mode. The combined adjust is equivalent to shrinking text by 1/5. If we stayed on the laptop the same transformation could support 500% enlargement. Technology has changed since WCAG 2.0. What seemed out of scope then is mainstream technology. Right now there is no screen magnification system that can enlarge at 300% with word wrapping and remain fully functional. That is why we need to expand the size range with word wrapping. Wayne On Wed, Feb 1, 2017 at 4:15 PM, Sean Murphy (seanmmur) <seanmmur@cisco.com> wrote: > Wayne, > > > > Interesting research and if I have read it correctly. As the WCAG 2.0 only > recommends 200% and based upon your research. There is no difference > between wrap and zoom. Should the SC be updated or change to include wrap > magnification to permit a higher level? > > > > Sean Murphy > > Accessibility Software engineer > > seanmmur@cisco.com > > Tel: +61 2 8446 7751 <+61%202%208446%207751> Cisco Systems, Inc. > > The Forum 201 Pacific Highway > > ST LEONARDS > > 2065 > > Australia > > cisco.com > > Think before you print. > > This email may contain confidential and privileged material for the sole > use of the intended recipient. Any review, use, distribution or disclosure > by others is strictly prohibited. If you are not the intended recipient (or > authorized to receive for the recipient), please contact the sender by > reply email and delete all copies of this message. > > > > *From:* Glenda Sims [mailto:glenda.sims@deque.com] > *Sent:* Thursday, 2 February 2017 10:50 AM > *To:* Wayne Dick <wayneedick@gmail.com> > *Cc:* W3C WAI ig <w3c-wai-ig@w3.org>; public-low-vision-a11y-tf < > public-low-vision-a11y-tf@w3.org>; Jim Allan <jimallan@tsbvi.edu>; Joshue > O Connor <josh@interaccess.ie>; Andrew Kirkpatrick <akirkpat@adobe.com> > *Subject:* Re: Horizontal Scrolling for Reading Text: Why it doesn't work. > > > > Wayne, > > > > I'm deeply grateful for your research on this! I always knew it was a > pain, but I did not truly understand how bad it was until I experienced it > myself. I want the world to understand this now! > > > > G > > > glenda sims | team a11y lead | deque.com | 512.963.3773 > <(512)%20963-3773> > > *web for everyone. web on everything.* - w3 goals > > > > On Wed, Feb 1, 2017 at 5:01 PM, Wayne Dick <wayneedick@gmail.com> wrote: > > If you would want to understand why horizontal scrolling is really not the > following gives a quantitative explanation. Nobody has ever done this > analysis before. > > http://nosetothepage.org/Fitz/2dScroll.html > > You cannot make an informed judgement of Resize Content and Linearize > without considering this proof of extreme user need. Two dimensional > scrolling of blocks of text is not just annoying it is a profound > disruption of the reading process. > > Wayne > > > > Wayne > > > > > > > >
Received on Thursday, 2 February 2017 00:39:32 UTC