WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2and high contrast

for

From: Kevin Prince
Date: Oct 5, 2015 8:34PM

Interpret the language of the page - that's ambitious. So schadenfreude will be easy enough I'm sure but what about all the other words borrowed and absorbed over the years. Probably pushed by a developer with a more consistent version of language - wouldn't work in New Zealand - kia ora.
K

K
Access1in5
0212220638
039290692
Independent Accessibility and IT Consultancy.



> On 6/10/2015, at 15:21, Paul J. Adam < <EMAIL REMOVED> > wrote:
>
> My argument is that the accessible name has already been provided by the author for the screen reader user so the WinHCM at should take advantage. I'm not saying AT should try to guess something like what the language is or what the form label is. Authors provide the info to A11y API and the AT should present it. I don't think authors should have to hack their way around very specific AT like Windows High Contrast mode.
>
> Paul J. Adam
> Accessibility Evangelist
> www.deque.com
>>
>>
>>> I would rather Windows HCM not hide background images on focusable elements than to try and convince all web developers of the world to implement a specific hack for WinHCM.
>>
>> You could make the same argument for just about anything -- why not have screen readers interpret the language so web developers don't need to set the language -- this is a valid argument I've seen in W3C lists. You could even say -- why have authors set the contrast of pages at all if the user can change the contrast?
> > > >