WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Disabled Controls and WCAG Contrast

for

From: Donald Evans
Date: Nov 21, 2011 10:15AM


I did see that, but the grayed out content does indicate disabled to the
sighted user. So wasn't sure it was decoration?

On Mon, Nov 21, 2011 at 11:24 AM, Andrew Kirkpatrick < <EMAIL REMOVED> >wrote:

> No - see 1.4.3:
>
> " Incidental: Text or images of text that are part of an inactive user
> interface component, that are pure decoration, that are not visible to
> anyone, or that are part of a picture that contains significant other
> visual content, have no contrast requirement."
>
> Thanks,
> AWK
>
> Andrew Kirkpatrick
> Group Product Manager, Accessibility
> Adobe Systems
>
> <EMAIL REMOVED>
> http://twitter.com/awkawk
> http://blogs.adobe.com/accessibility
>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:
> <EMAIL REMOVED> ] On Behalf Of Donald Evans
> Sent: Monday, November 21, 2011 11:22 AM
> To: WebAIM Discussion List
> Subject: [WebAIM] Disabled Controls and WCAG Contrast
>
> Do disabled controls (grayed out to indicate disabled) have to meet WCAG
> SC 1.4.3?
>
> --
> Donald F. Evans,
> Making Websites Accessible
> Senior Accessibility Architect
> Deque Systems
> Email: <EMAIL REMOVED>
> Download FireEyes Free: http://www.deque.com/products/worldspace-fireeyes
>
> <http://www.deque.com>;
>