[aria-concepts-with-sliders] Why Sliders?

[yatil]

From @kakinney on March 28, 2017 19:36

Wondering why we are doing the tutorial on Aria concepts with sliders? Aren't there more basic options like check boxes or radio buttons (totally boring stuff, I know) that people may find more universally useful?

Copied from original issue: w3c/wai-tutorials#469

[yatil]

From @sharronrush on March 29, 2017 17:33

This is a good point and gets to the tendency we have to silo certain topics and treat them as if they are somehow separate from the whole practice of accessibility. That is our current approach to Mobile for example and is not very effective.

We currently have many quite natural references to ARIA within the existing tutorials, which is the way for this to be most effective in my opinion. If the purpose is "How to use the ARIA Authoring Guide" I can see that being useful. If that is the point, then it seems we may not want to focus on only one component but use several examples of how you might reference the Guide as you build your widget.

[yatil]

From @kakinney on March 31, 2017 14:32

@brewerj - this was my comment.

[yatil]

From @nrhsinclair on April 20, 2017 17:50

I agree with that statement and that's where I was hung up. A more basic example would be a good starting point in an introduction.

[yatil]

From @mcking65 on April 21, 2017 18:35

I think the goals/purpose Judy and I discussed will become more clear as we hammer a little more shape into the tutorial.

Basically, there are a few things everyone should understand about ARIA before you use it at all. They are things that must be stated in several ways in several places, and can't be repeated often enough.

These are things we want people to understand before they start using what is in the APG. They will be restated in a similar way in the APG intro. And, I plan to have the APG intro point people to this tutorial as well.

My plan is to use a real life example that is super simple to get these points across. We will talk primarily in code; the goal is to reach people who learn that way.

I was originally thinking of using checkbox to teach these concepts, but after discussion with some engineers here at Facebook about what we see in real life, button will serve the purpose better. In everyday engineering, there are more reasons not to use an html button than not to use an html checkbox. And, we see that reflected in our code base as well as in publicly available code.

[yatil]

In everyday engineering, there are more reasons not to use an html button

Playing devil’s advocate here :-) I can’t think of one reason not to use an HTML <button> element :-) Happy to learn in what situations they are not working.

[yatil]

From @mcking65 on April 21, 2017 21:13

Styling limitations, state/property limitations.