- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Wed, 4 Nov 2015 08:40:04 -0600
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- Cc: Shawn Henry <shawn@w3.org>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
- Message-ID: <CA+=z1W=2pGeN1HjjQoxHtNcU4BhXdV8_5rYimmemACTZ8sH7HQ@mail.gmail.com>
I agree with Laura and Jon. Doesn't matter who or what caused the problem, HCM and background images IS a low vision issue. Jim On Tue, Nov 3, 2015 at 3:36 PM, Laura Carlson <laura.lee.carlson@gmail.com> wrote: > Hi Shawn, > > It is an issue for people with low vision who do not use a screen > reader but rather Windows High Contrast Mode. > > Check what Jon wrote back in July, "...This forces users with low > vision who use high contrast or ignore colors to completely turn off > CSS for the page. Requiring the user to turn off CSS to simply have > access to a meaningful image that the developer should not have made a > presentation layer image is an issue for me." > https://lists.w3.org/Archives/Public/w3c-wai-gl/2014JulSep/0090.html > > Me too. > > As Aurelien Levy said "I think there is two things that may lead to > think it's not a failure : > - there is a sufficient technique allowing to use hidden text with css > http://www.w3.org/TR/WCAG20-TECHS/C7.html (so same technique but in > one case is a failure and in an other case it's not) > - for me an association with the guideline 1.3 is missing because > using user css or high contrast mode is clearly a case where content > is presented in different ways and it must be without losing > information or structure." > https://lists.w3.org/Archives/Public/w3c-wai-gl/2014JulSep/0091.html > > Thanks, > Laura > > On 11/3/15, Shawn Henry <shawn@w3.org> wrote: > > Laura Carlson wrote: > >> WCAG has Technique F3: Failure of Success Criterion 1.1.1 due to using > CSS > >> to include images that convey important information > > > > Right! Thanks for the reminder. > > > > So this issue is not specific to low vision. > > > > ~Shawn > > > > > > > > Laura Carlson wrote: > >> Hi Shawn, > >> > >> The fundamental user issue is that CSS background images in HCM vanish > >> and are not perceivable. > >> > >> It could potentially be solved by any of the 3. > >> > >> WCAG has Technique F3: Failure of Success Criterion 1.1.1 due to using > >> CSS to include images that convey important information > >> http://www.w3.org/TR/WCAG20-TECHS/F3.html > >> > >> Kindest Regards, > >> Laura > >> > >> On 10/28/15, Shawn Henry <shawn@w3.org> wrote: > >>> Re below: Is the fundamental issue that: > >>> 1. images that provide contextual information should not be included > via > >>> CSS > >>> background? > >>> *or* > >>> 2. high contrast mode (HCM) and other setting should not turn off > >>> background > >>> images? > >>> *or* > >>> 3. users should have the option of turning background images on or off > >>> in > >>> HCM and other settings? > >>> *or* > >>> 4. other... > >>> > >>> > >>> > >>> On 10/28/2015 10:52 AM, Laura Carlson wrote: > >>>> Hi Shawn Jon, and all, > >>>> > >>>> Good catch, Jon. That is one of our use cases page. It is currently > >>>> the second point under color and contrast with the unique identifier > >>>> [Laura, UC-7] . > >>>> > https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/User_stories_-_use_cases#Color_and_Contrast > >>>> > >>>> It might be good to include the unique identifier [Person, UC-#] from > >>>> the "User stories - use cases" on the user requirements table for > >>>> reference, mapping and to be sure we don't miss others, which should > >>>> be included. > >>> > >>> Done (after I post the up date :-). > >>> ~Shawn > >>> > >>>> > >>>> Thanks. > >>>> > >>>> Best Regards, > >>>> Laura > >>>> > >>>> On 10/28/15, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote: > >>>>> Shawn, I wanted to discuss another potential item for the user > >>>>> requirements > >>>>> - what about removal of background/non-decorative images. That is > >>>>> a11y > >>>>> features such as High contrast in Windows will remove background > >>>>> images > >>>>> that > >>>>> are seen as decorative from the page content. This is an issue when > >>>>> background image techniques are incorrectly used by developers with > >>>>> meaningful images and then content is missing. If this is already > >>>>> covered - > >>>>> please excuse this note. > >>>>> > >>>>> Best Regards, > >>>>> > >>>>> Jonathan > >>>>> > >>>>> -- > >>>>> Jonathan Avila > >>>>> Chief Accessibility Officer > >>>>> SSB BART Group > >>>>> jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com> > >>>>> Phone 703.637.8957 > >>>>> Follow us: Facebook<http://www.facebook.com/#!/ssbbartgroup> | > >>>>> Twitter<http://twitter.com/#!/SSBBARTGroup> | > >>>>> LinkedIn<http://www.linkedin.com/company/355266?trk=tyah> | > >>>>> Blog<http://www.ssbbartgroup.com/blog> | > >>>>> Newsletter<http://eepurl.com/O5DP> > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >> > >> > > > > > > > -- > Laura L. Carlson > > -- 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
Received on Wednesday, 4 November 2015 14:40:34 UTC