RE: aria-valuestep or equivalent needed to make range widgets operable by AT

From: Dominic Mazzoni []
Sent: Tuesday, May 17, 2016 3:02 PM

Sounds good, it might be easier to just put everything in ARIA 2.0 and then when it's time to start working on those, consider pulling off some of the easy low-hanging fruit into ARIA 1.2.

At least on first reading, this seems to be a sound approach.

The truth is that the feature requests will just keep coming, and without a disciplined approach to managing the scope of each version of the specification, they’ll lead to very long delays in the process of producing W3C Recommendations.

Would it be possible to make any large-scale architectural changes, then move ARIA 2.x into shorter and more incremental development processes? I know there has been discussion of building an accessibility API that would be available to scripts, but it isn’t clear how this relates to ARIA 2.0 and what the larger design would be. Nevertheless, careful thinking about managing the feature requests (already achieved partially through modularization) would be helpful, and it would also alleviate the desire to squeeze that last new role, state or property into ARIA 1.1 before it’s finalized.


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.


Received on Wednesday, 18 May 2016 13:16:12 UTC