[Webkit-unassigned] [Bug 196834] [iOS] Using opacity to indicate disabled form controls is not good for accessibility

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=196834

Brad <brkemper at mac.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brkemper at mac.com

--- Comment #2 from Brad <brkemper at mac.com> ---
Sorry, but I disagree. The purpose of having a disabled control is to show that something is there, but it can’t be used. An alternative is to have opacity:0, would be more reasonable than opacity:1. Or to have the text so blurred that no perfect-vision people can read it either. But doing that doesn’t make it better for anyone; it would be more symbolic than anything. Making a disabled field look like a regular field would be a disservice to everyone. It is **supposed** to be less readable, so that the enabled controls are more readable in comparison.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190412/20020493/attachment.html>