RE: 1100% enlargement from Katie Haritos-Shea GMAIL on 2016-07-10 (public-low-vision-a11y-tf@w3.org from July 2016)

From: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Date: Sun, 10 Jul 2016 14:09:09 -0400
To: "'Wayne Dick'" <wayneedick@gmail.com>, "'public-low-vision-a11y-tf'" <public-low-vision-a11y-tf@w3.org>
Message-ID: <07f401d1dad6$288cd5f0$79a681d0$@gmail.com>

I agree Wayne….:-)

 



 

 

 

* katie *

 

Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)

 

Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 |  <https://twitter.com/Ryladog> @ryladog

 

From: Wayne Dick [mailto:wayneedick@gmail.com] 
Sent: Sunday, July 10, 2016 12:34 PM
To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Subject: 1100% enlargement

 

The size 1100% seems crazy o first glance, but it is very practical for reading. I first thought of getting all logical, but an example is better. Look at WCAG 1.4.8 Issue #5.  I have included a screen shot of 1100% enlargement of 16px on a 22 inch screen. It looks like a reasonable reading interface to me.

Take a look. https://github.com/w3c/low-vision-SC/issues/5

Wayne

Received on Sunday, 10 July 2016 18:09:42 UTC