W3C home > Mailing lists > Public > public-low-vision-comments@w3.org > April to June 2017

Re: Accessibility Requirements for People with Low Vision

From: Jim Allan <jimallan@tsbvi.edu>
Date: Tue, 18 Apr 2017 15:00:18 -0500
Message-ID: <CA+=z1Wnq2+JXE0etG18shVopGqcopUY9z9pVg+duWmrRVqMVdA@mail.gmail.com>
To: public-low-vision-comments@w3.org, Ike Presley <ipresley@afb.net>
Hello Ike,
Thank you for your comments. The Low Vision Task Force has been busy.
Our reply is inline prefaced with LVTF:

From: *Ike Presley* <ipresley@afb.net
<ipresley@afb.net?Subject=Re%3A%20Accessibility%20Requirements%20for%20People%20with%20Low%20Vision&In-Reply-To=%3CCA%2B%3Dz1W%3DLYgnZvL88-F4-5VkcUZUZ6oKkgOLhk-5QNffcvyNnsw%40mail.gmail.com%3E&References=%3CCA%2B%3Dz1W%3DLYgnZvL88-F4-5VkcUZUZ6oKkgOLhk-5QNffcvyNnsw%40mail.gmail.com%3E>
Date: Friday, March 18, 2016
Subject: Accessibility Requirements for People with Low Vision
To: "Jim Allan (jimallan@tsbvi.edu
<jimallan@tsbvi.edu?Subject=Re%3A%20Accessibility%20Requirements%20for%20People%20with%20Low%20Vision&In-Reply-To=%3CCA%2B%3Dz1W%3DLYgnZvL88-F4-5VkcUZUZ6oKkgOLhk-5QNffcvyNnsw%40mail.gmail.com%3E&References=%3CCA%2B%3Dz1W%3DLYgnZvL88-F4-5VkcUZUZ6oKkgOLhk-5QNffcvyNnsw%40mail.gmail.com%3E>
Cc: Ellen Bilofsky <ebilofsky@afb.net
<ebilofsky@afb.net?Subject=Re%3A%20Accessibility%20Requirements%20for%20People%20with%20Low%20Vision&In-Reply-To=%3CCA%2B%3Dz1W%3DLYgnZvL88-F4-5VkcUZUZ6oKkgOLhk-5QNffcvyNnsw%40mail.gmail.com%3E&References=%3CCA%2B%3Dz1W%3DLYgnZvL88-F4-5VkcUZUZ6oKkgOLhk-5QNffcvyNnsw%40mail.gmail.com%3E>
George Abbott <gabbott@afb.net
<gabbott@afb.net?Subject=Re%3A%20Accessibility%20Requirements%20for%20People%20with%20Low%20Vision&In-Reply-To=%3CCA%2B%3Dz1W%3DLYgnZvL88-F4-5VkcUZUZ6oKkgOLhk-5QNffcvyNnsw%40mail.gmail.com%3E&References=%3CCA%2B%3Dz1W%3DLYgnZvL88-F4-5VkcUZUZ6oKkgOLhk-5QNffcvyNnsw%40mail.gmail.com%3E>

*Hi Jim,*
*I have reviewed the guidelines and made some comments below.*

*If these guidelines are designed for web and e-text programmers I think
the more examples, the better, so that they can see the differences between
traditional displays of text & elements and those adjusted for people with
low vision. *

LVTF: We agree, and have added many images and user stories.

 *Section 3.1.1 – “*Some people turn down the brightness of their screen or
use an overlay.*“ I would suggest, “*Some people turn down the brightness
of their screen or use an overlay, while others like to increase the
brightness especially on mobile devices.” Or something like that.
LVTF: We changed the document to include brightness
Edit 3.1.1 to include brightness.
<https://www.w3.org/2016/04/06-lvtf-minutes.html#resolution03>

 *Section 3.1.2 – I really like the examples and the emphasis on “**User
Need - Contrast:*

Users can set the background color and the text color from the full color
spectrum.*”*
LVTF: thank you

 *Section 3.1.3 – I really like the color wheel examples from 2.4.5. If you
think people might be jumping around in this resource it might be worth
repeating the color wheels here.*

LVTF: After group discussion we decided to Leave the color whels
images as is. <https://www.w3.org/2016/04/06-lvtf-minutes.html#resolution04>

*Section 3.2.1 & 3.2.2 – I am so happy to see these sections. For me
personally this is one of the most important accommodations when reading
electronic text regardless of device or software application. I wish every
piece of software was required to have these feature.*

LVTF: we are finding that this is a huge issue.

*Section 3.3.2 – I think this section should also include something like
the following. “Avoid the use of serif fonts such as **Times New Roman**
because the serifs produce visual clutter that makes it more difficult to
distinguish characters and impedes reading efficiency.” Include examples
like how the lower case “**g**” in Times New Roman looks like the number 8.
I am not sure if you want to mention or include the work that Dr. Elaine
Kitchel (APH) did when she developed APHont. It would be nice to offer that
as one of the font choices available. *

*I think there will also need to be a note about using Accessibility
options available in the browser such as in IE under Tools:Internet
Options:Accessibility. Looks like this might be covered in Section 3.7.3.*

LVTF: Leave section 3.3.2 as it and cover specific fonts in best
practice. <https://www.w3.org/2016/04/06-lvtf-minutes.html#resolution05>

*Section 3.3.3 – I would suggest adding, “Avoid the use of italics when
possible.”*
LVTF: Leave 3.3.3. Cover italics in best practices.
<https://www.w3.org/2016/04/06-lvtf-minutes.html#resolution06>

*Section 3.5.1 – The contrast in Fig. 12 is not very good and illustrates a
poor example.*

LVTF: reply previously sent
 https://lists.w3.org/Archives/Public/public-low-vision-comments/2016AprJun/0004.html

 *I do not recognize the names on the Low Vision Task Force. Do any of them
have low vision? I’m guessing at least one of them does, but I  just don’t
know the names well enough.*

*Please give my thanks and sincere appreciation to the task force for
working on this much needed topic. At times it seems that much of the
attention to accessibility is geared towards users with no usable vision so
it’s nice to see this initiative. Please let me know if I can help further.*

*Hope this helps,*

*Ike*



*Ike Presley, TVI, CLVT, CATIS*

*National Project Manager*

*American Foundation for the Blind*

*739 W. Peachtree St. N.W., Suite 250*

*Atlanta, GA 30308*

*404-525-2303*

*www.afb.org <http://www.afb.org/>*


-- 
Jim Allan,
​Facilitator - Low Vision Task Force​

Accessibility Coordinator
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Tuesday, 18 April 2017 20:00:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:23:41 UTC