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

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.

On Tue, May 17, 2016 at 10:30 AM Richard Schwerdtfeger <richschwer@gmail.com>
wrote:

> Hi Dominic,
>
> We currently have an ARIA 2.0 product in our issue tracking repository.
> For ARIA 2.0 (or ARIA.next) we plan to do all this in github … issues, etc.
>
> I have created an ARIA 1.2 product in tracker:
> https://www.w3.org/WAI/ARIA/track/products/52
>
> We do need to have the group agree to doing an ARIA 1.2. Based on some of
> the things people want to do it makes sense as long as we keep it small.
>
> What I think would be good to do is to put this into ARIA 2.0 as an issue
> and then go through the list to decide what we could put into a 1.2. In
> ARIA 2.0 (or ARIA.next) we planned to put issues into github and get off
> the W3C tracker.
>
> Would it be acceptable to people that I create an ARIA 2.0 issue and make
> a note in it that members would like this in an ARIA 1.2 release and link
> to the thread that James Craig started?
>
> I then need to discuss with the group about producing an ARIA 1.2?  It is
> within our charter to do so.
>
>
> Rich
>
> On May 17, 2016, at 10:48 AM, Dominic Mazzoni <dmazzoni@google.com> wrote:
>
> Is there a component for potential ARIA 1.2 issues? Even though 1.1 is
> nearly locked down I think from time to time we'll keep coming up with
> small issues like this, but it seems fine to set it aside for a while as
> we have a place to keep track of it.
>
> - Dominic
>
>
> On Tue, May 17, 2016 at 7:59 AM Richard Schwerdtfeger <
> richschwer@gmail.com> wrote:
>
>> Thank you for raising this issue. We are trying to lock down ARIA 1.1 for
>> June as HTML 5.1 and SVG2 are all trying to lock down. This is also an
>> objective of our group. We lost a minimum of 3 months in addressing charter
>> issues.
>>
>> If we are going to address this issue and it is really necessary we
>> should consider a very small ARIA 1.2. I checked with Freedom Scientific
>> today and they do not, for any browser or native Windows application
>> announce step information. Additionally, MSAA/IA2 used by both Firefox and
>> Chrome does not have a step value in its value interface. We would need to
>> either create a modification to the value interface or we would need to
>> stick it in an object attribute. Then we would need to convince at least
>> one AT that it is important to provide the information.
>>
>> I am not saying this does not have value. However, introducing a new
>> issue now would cause all of this work to get out of synch. We are trying
>> to lock down:
>>
>> SVG2 Accessibility
>> HTML 5.1 Accessibility
>> ARIA 1.1
>> ARIA DPUB
>> ARIA Graphics
>>
>> and all the associated mapping specifications. We are also looking at
>> creating automated testing. Our plate is full.
>>
>> I recommend we make this an ARIA 2.0 issue and then decide if we should
>> make an ARIA 1.2 (a very limited release) and then discuss whether we bring
>> this in. Getting this all resolved from APIs to ATs to the spec. will take
>> some time.
>>
>> What is extremely important is that we lock down ARIA 1.1 and get working
>> on Web Components as well as a JavaScript accessibility API which many
>> browser vendors want. The charter delay set us back 3 months in getting on
>> that. I would like to really be able to focus on Web Components at TPAC.
>>
>> Rich
>>
>>
>>
>>
>> > On May 16, 2016, at 10:37 PM, James Craig <jcraig@apple.com> wrote:
>> >
>> > ARIA group,
>> >
>> > A long-standing problem with ARIA sliders is that they can only be made
>> partially accessible, and only on keyboard-based interfaces. There have
>> been some recent brainstorms and discussions about what it would require to
>> make custom ARIA sliders directly operable by AT (for example, on touch
>> screen devices).
>> >
>> > One of the missing links is an a direct equivalent to the @step
>> attribute on <input type="range">.
>> >
>> > Please consider adding @aria-valuestep (or an equivalent attr) for
>> range widgets such as sliders. Ideally this would be an addition to ARIA
>> 1.1 to match HTML and allow for future AT support.
>> >
>> > Thanks,
>> > James Craig
>> >
>> >
>>
>>
>