- From: James Nurthen <james.nurthen@oracle.com>
- Date: Wed, 25 Feb 2015 10:55:26 -0800
- To: public-pfwg@w3.org
- Message-ID: <54EE1A9E.7050709@oracle.com>
To me this is a deficiency of HTML and the kind of thing that developers need to end up using ARIA to paper over. The lack of a read-only checkbox state forces developers to use disabled when they want checkboxes to not be changeable. This leads to a legibility issue as disabled checkboxes are (intentionally) hard to read. When a UI design calls for a checkbox which cannot be modified - and where the value is still important to be conveyed to the user - readonly is the correct choice. This also applies to the new switch role which needs to support the readonly state. Regards, James On 2/25/2015 10:32 AM, Alexander Surkov wrote: > It's interesting. Also the browsers seems allow to change the value on > readonly checkboxes. So, ARIA checkbox shouldn't have readonly state > as well? > > On Wed, Feb 25, 2015 at 11:55 AM, Steve Faulkner > <faulkner.steve@gmail.com <mailto:faulkner.steve@gmail.com>> wrote: > > note, native html checkbox is not allowed readonly > http://www.w3.org/TR/html5/forms.html#checkbox-state-%28type=checkbox%29 > > -- > > Regards > > SteveF > HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> > > On 25 February 2015 at 16:28, Alexander Surkov > <surkov.alexander@gmail.com <mailto:surkov.alexander@gmail.com>> > wrote: > > Hi. ARIA role checkbox [1] doesn't list aria-readonly > property, however it's supported in Firefox. That makes me > think aria-readonly on checkbox was dropped from the spec at > some point. I'm curious if anybody recalls what was the point. > Does readonly state make any sense on checkboxes? > > Thanks! > Alexander. > > > [1] http://rawgit.com/w3c/aria/master/aria/aria.html#checkbox > > >
Received on Wednesday, 25 February 2015 18:56:00 UTC