WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Disabled Controls and WCAG Contrast

for

From: Andrew Kirkpatrick
Date: Nov 21, 2011 9:57AM

Don,
I think that in that situation the user will essentially need to think - "hey, there's a button here but I can't read the text on it like I can other buttons in this app, and I can't seem to click on it either - it must be currently non-functional".

Re: Paul's suggestion, I don't recommend using readonly when the object is an inactive control. Read only and inactive are not equivalent. If the desire is to keep disabled controls in the tab order, then please make that comment to the HTML5 specification so browser vendors will implement the right method. I'm not sure that I agree that disabled controls should be in the tab order - as a sighted user who relies heavily on the keyboard I'd prefer that inactive controls not be in the tab order as it just adds unnecessary tab stops.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe Systems

<EMAIL REMOVED>
http://twitter.com/awkawk
http://blogs.adobe.com/accessibility