Feedback for "Introduction to ARIA Essentials for Developers"

Hi, EO

I’m *so* sorry that I didn’t get a chance to complete this yesterday. But I’ve gone through the tutorial and noticed just a handful of typos. These may have already been caught. Feedback is below.


Unsure about the tone and use of "amazing powers." I’m fine with it if others are. I just didn’t think the tone matched the rest of the tutorial.

  *   Purpose: What ARIA does, i.e., understanding the amazing powers of ARIA.
  *   Limits: What ARIA does not do, i.e., using those amazing powers comes with critical responsibilities.

Typo under Objective http://wai.accessibility.rocks/aria-concepts/build/aria-concepts/


  *   Safely and creatively exploit ARIA to build rrich experiences that are fully accessible.

Is there a way to separate the last two paragraphs, perhaps by giving them a heading? http://wai.accessibility.rocks/aria-concepts/build/aria-concepts/2-scenario/


  *   "However, XYZ web site management wants something new. They have asked for a redesign that…"

This sentence confused me at first. I think adding the word "that" would make it clearer. http://wai.accessibility.rocks/aria-concepts/build/aria-concepts/3-automaticAX/


  1.  Browsers populate operating system accessibility APIs with information that assistive technologies use to render and interact with the element.

http://wai.accessibility.rocks/aria-concepts/build/aria-concepts/3-automaticAX/

Another instance where I personally believe adding the word "that" would improve readability.

  *   While sighted users can easily determine that the purpose of each radio is to choose a plan, browsers are able to explicitly communicate the label for the radio group to assistive technologies because of the legend element contained inside of the fieldset element.

http://wai.accessibility.rocks/aria-concepts/build/aria-concepts/5-purpose/

"Analogous" is misspelled.
Note that:

  1.  A wrapping div was added for the radiogroup role. This is analgous to the HTML fieldset.

http://wai.accessibility.rocks/aria-concepts/build/aria-concepts/5-purpose/

"Straightforward" is one word.

  *   Choosing a pattern to apply to a custom UI component from the ARIA Authoring Practices design patterns<https://www.w3.org/TR/wai-aria-practices-1.1/#aria_ex> is typically straight forward. However, like much of UI engineering, there are circumstances where it requires as much art as science.

http://wai.accessibility.rocks/aria-concepts/build/aria-concepts/5-purpose/

It appears "giant" is misspelled here.

  *   Behavior matters more than appearance. If a widget behaves like a radio group, for example, even if it looks nothing like a radio group, radio group may be the best fit. With careful attention to detail, this concept opens up all kinds of possibilities, e.g., a gant chart built from a stack of ARIA toolbars containing menu buttons.

http://wai.accessibility.rocks/aria-concepts/build/aria-concepts/6-risks/
"Devastating" is misspelled here.

  *   Incorrect ARIA markup can have devistating effects for users of assistive technologies. It gives assistive technologies information about the UI that misleads the user. Incorrect ARIA ccan not only make learning a UI more difficult but even unintentionally hide information or block interactions.



Jesús Pulido, CPACC
Accessible Multimedia Coordinator



Georgia Institute of Technology | College of Design
AMAC | 512 Means Street | Suite 250 | Atlanta, GA 30318
Office: 404.894.8303<tel:404.894.8303> | Fax: 404.894.8323<tel:404.894.8323>