- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Thu, 9 Jul 2015 13:05:22 -0400
- To: Joanmarie Diggs <jdiggs@igalia.com>, W3C WAI Protocols & Formats <public-pfwg@w3.org>
Hi Joanie,
On 2015-07-08 1:09 PM, Joanmarie Diggs wrote:
> If aria-readonly should be a supported property of checkbox and textbox
> and switch and... Should it not also be a supported property of:
>
> * ...
> * slider
> * spinbutton
The first sentence of the second paragraph of aria-readonly says:
" This means the user can read but not set the value of the widget".
I'm not sure if this is a problem for enabled but readonly sliders or
spinbuttons, which have a value (aria-valuenow). For example, does it
mean that users can drag the thumb of the slider, but when they let go,
it snaps back to its original position? Compare that with a disabled
slider: the user cannot manipulate the thumb at all.
Note that there is no analogous issue with read-only checkboxes and
switches, since they have a checked state, not a value.
What are the use case for readonly sliders/spinbuttons? Is it the same
as readonly checkboxes?
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
Received on Thursday, 9 July 2015 17:05:51 UTC