WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2and high contrast

for

From: Birkir R. Gunnarsson
Date: Oct 11, 2015 6:00PM

What are people's thoughts on using a a CSS background image to
rpvodie info about a focusable element, also providing an off-screen
"alternative text".
<!--
- The PDF_Icon CSS class includes a PDF log or image displayed in the
background.
- The visuallyHidden class uses clip method to hide text off screen
but make it available to screen reder users.
-->

<button class="PDF-_icon">Download File
<span class="visuallyHidden">PDF</span>
</button>

While this works for a screen reader, it would not work for someone
who customized styl sheets (and I also believe that inverting color
mode hides the image, as previously discussed).

The very obvious answer is that, yes, it is a CSS image, it has
information, and that would violate SC 1.1.1.
Use an inline image with appropriate alt tag instead.

But often webpages are turning to this technique to avoid loading
multiple inline images.

What if we made use of to the title attribute here
<button class="PDF-_icon" title="PDF">Download File</button>


I guess the CSS content attribute may solve this, though the
definition of CSS (use for presentation) is getting increasingly
inaccurate.



On 10/5/15, Kevin Prince < <EMAIL REMOVED> > wrote:
> 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?
>> >> >> >> >
> > > > >


--
Work hard. Have fun. Make history.