- From: <bugzilla@jessica.w3.org>
- Date: Wed, 08 Jul 2015 09:33:02 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13390
Charles McCathieNevile <chaals@yandex-team.ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |chaals@yandex-team.ru
Resolution|WONTFIX |---
--- Comment #4 from Charles McCathieNevile <chaals@yandex-team.ru> ---
I think Hixie's answer here is wrong. There are reasonable use cases for not
allowing interaction with a control, but making it clear to users that it is
currently not interactive - e.g. things that will be submitted in a form, but
can't be changed (perhaps except if you did something else first).
There are common ways of indicating this visually, but making the control
disabled and removing it upsets the expectation of the screen reader user, who
may not realise that it can later become interactive.
People *are* making readonly controls other than text things, and we should not
force them to use horrible messy hacks to do so because that leads them to get
accessibility wrong…
It should be possible to apply readonly to other stuff.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 8 July 2015 09:33:05 UTC