- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Wed, 27 Apr 2016 09:26:41 -0500
- To: Wayne Dick <wayneedick@gmail.com>
- Cc: Jim Allan <jimallan@tsbvi.edu>, Low Vision Accessibility Task Force <public-low-vision-a11y-tf@w3.org>
Works for me. Thanks, Wayne. Maybe one small typo? Should "Specifically, all such visual cures" be "Specifically, all such visual cues"? Kindest Regards, Laura On 4/26/16, Wayne Dick <wayneedick@gmail.com> wrote: > Let's block that a little better. Sorry about the typographic mess above. > > Need: When the content author uses visual cues to guide the visual user’s > scanning of the page, a user with reduced contrast sensitivity should be > able to perceive the visual cues being used. Specifically, all such visual > cures must provide sufficient contrast to support detection by users with > reduced contrast sensitivity. > > > Explanation: Often form fields and special blocks of text like definition > or navigation sections are called out using borders or changes in > background color. In these cases, the borders and altered background colors > should provide sufficient contrast with the all adjacent regions of the > page. This includes all borders used for form fields, radio buttons, check > boxes and focus indicators. Objects that are distinguished by alternative > colors including form fields should also have sufficient contrast as > defined in the WCAG 2.0 glossary. > > That should be easier to read. > > On Tue, Apr 26, 2016 at 12:52 PM, Wayne Dick <wayneedick@gmail.com> wrote: > >> Hi all, >> >> Maybe this wording will do it. >> >> When the content author uses visual cues to guide the visual use’s visual >> scanning of the page, a user with reduced contrast sensitivity should be >> able to perceive the visual cues being used. Specifically, all such >> visual >> cures must provide sufficient contrast to support detection by users with >> reduced contrast sensitivity. >> >> Explanation: Often form fields and special blocks of text like definition >> or navigation sections are called out using borders or changes in >> background color. In these cases, the borders and altered background >> colors >> should provide sufficient contrast with the all adjacent regions of the >> page. This includes all borders used for form fields, radio buttons, >> check >> boxes and focus indicators. Objects that are distinguished by alternative >> colors including form fields should also have sufficient contrast as >> defined in the WCAG 2.0 glossary. >> >> >> On Wed, Apr 20, 2016 at 10:28 AM, Jim Allan <jimallan@tsbvi.edu> wrote: >> >>> Note: 3.5.1 Element-level customization talks about borders and colors. >>> perhaps we can expand the explanatory text to illustrate the need to >>> change >>> "non-text contrast". >>> >>> That said, I think this is a major issue to be added to WCAG. Minimum >>> contrast (WCAG 1.4.3) should apply to more than only text and images of >>> text content. It should apply to form controls and other elements with >>> borders. >>> Jim >>> >>> On Wed, Apr 20, 2016 at 10:34 AM, Low Vision Accessibility Task Force >>> Issue Tracker <sysbot+tracker@w3.org> wrote: >>> >>>> lvtf-ACTION-51: Write user need on "non-text contrast" - [can change >>>> the >>>> name, border, grids, etc] >>>> >>>> http://www.w3.org/WAI/GL/low-vision-a11y-tf/track/actions/51 >>>> >>>> Assigned to: Wayne Dick >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> 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 Wednesday, 27 April 2016 14:27:09 UTC