- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Tue, 14 Feb 2017 09:32:34 -0600
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Cc: GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
Hi Jon, This SC sets metrics for a normative testable baseline. Testable values (Verdana/white&black/EMs) are intended to provide a standard baseline, any particular user is likely to choose different values (especially font & color). The point is that this baseline is used to test the layout and functionality, and if it works then it is robust enough for certain user-adaptations (up to a point). White on black was chosen because if that combination works, 99% of all other combinations should be able to be overridden. The plan is to start testing sites with these metrics on the various user-agent tools, primarily bookmarklets created specifically for this. See where problems surface. Adjust measures if needed. And then provide techniques. Kindest Regards, Laura On 2/14/17, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote: > Ø LVTF has https://github.com/w3c/wcag21/pull/124 Adapting Text (address > text color, font, and spacing) > > That seems to focus on setting the background to white or black – some > people may need a background with less contrast. > > Jonathan > > From: Jim Allan [mailto:jimallan@tsbvi.edu] > Sent: Tuesday, February 14, 2017 10:18 AM > To: Jonathan Avila > Cc: GLWAI Guidelines WG org > Subject: Re: LVTF question > > LVTF has https://github.com/w3c/wcag21/pull/124 Adapting Text (address text > color, font, and spacing) > > On Tue, Feb 14, 2017 at 8:51 AM, Jonathan Avila > <jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>> wrote: > >> Otherwise we would have to have an SC that says you cannot have a white >> background on your web page. > > Creating content in a way the author does not prevent the user from > adjusting the colors through the user agent seems like an item that is > compatible with the LVTF needs. > > Jonathan > > From: Gregg C Vanderheiden > [mailto:greggvan@umd.edu<mailto:greggvan@umd.edu>] > Sent: Tuesday, February 14, 2017 9:40 AM > To: lisa.seeman > Cc: GLWAI Guidelines WG org > Subject: Re: LVTF question > > Brightness is not a function of the software. that is a function of the > hardware. > > If they are sensitive to any bright light — they can turn the brightness > down on their phone/computer — there can be no bright light. > > Otherwise we would have to have an SC that says you cannot have a white > background on your web page. > > > As for flashing we do have SC on both strong flashing that is very large at > all — and one for blinking of any size. > > If you do want to have something more about blinking content you will have > to have numbers. I don’t think a blinking period is a problem, or a very > small icon. — so “any size” is not really viable. > > Do you have any data on how many people and what size a blinking area is a > real problem? > > > Gregg C Vanderheiden > greggvan@umd.edu<mailto:greggvan@umd.edu> > > > > On Feb 13, 2017, at 2:39 PM, lisa.seeman > <lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>> wrote: > > Hi Folks > > I was wondering if we have a SC for severe photophobia -people who get pain > from intense light (any size) and flashing (any size) > > There should be a semantics to mark any section of elements with flashing > moving or blinking and these of these so that they can be blocked and make > sure that low contrast can not be overridden > > Do we have a SC that support this > > > > All the best > > Lisa Seeman > > LinkedIn<http://il.linkedin.com/in/lisaseeman/>, > Twitter<https://twitter.com/SeemanLisa> > > > > > -- > Jim Allan, 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 > -- Laura L. Carlson
Received on Tuesday, 14 February 2017 15:33:09 UTC