yatil
commented
6 years ago From @bakkenb on April 4, 2017 21:28
I am in favor of having this be more of a guide than a tutorial. I like the concept of a guide or overview understanding resource of ARIA, what it is for, examples, when to use, when to not abuse, etc. A lot of the ideas in this outline are good. This topic just doesn't lend itself to a succinct tutorial. I understand that the tutorial would/could focus on one examlpe, like the slider and then more understanding content around ARIA, but that doesn't seem to match our current tutorial structure.
On another note, I do think that the tutorial "area" is a place to generate views/interest in this topic of understanding ARIA and knowing where to find the ARIA Authoring Practices document. I would be interested in turning this into a more comprehensive guide, many of the outlined concepts, an example or two of components with ARIA code, and links to supporting documentation and the Authoring Practices. Then find a way to call attention to it in the tutorials or some sort of a developer landing area.
From @yatil on March 29, 2017 16:54
I generally don’t think that tutorials should be broad overviews, but more focused. Also I am concerned with how this tutorial is framed. We want to provide technique-inclusive tutorials, not siloed of tutorials. Maybe here it is also appropriate to see if parts of the draft can be repurposed for the ARIA Overview pages.
We already have a lot of ARIA guidance in the current tutorials.
Copied from original issue: w3c/wai-tutorials#476