Group formed to test and document assistive technologies

ARIA W3C logoThe W3C – World Wide Web Consortia – has created a community group to systematically test and document  assistive technologies use of ARIA and HTML5 accessibility features in web applications. W3C membership is NOT needed to participate in the community group.

How WAI-ARIA is supported by assistive technologies, such as screen readers, is highly variable. This variation in WAI-ARIA rendering adds unnecessary complexity to the development of high-quality web experiences for users of assistive technologies and places significant limitations on the types of web widgets that can be made widely accessible.

This community group is dedicated to:

  1. Helping assistive technology developers converge on a set of clear norms for baseline support of WAI-ARIA.
  2. Helping web developers understand the current state of support for WAI-ARIA by assistive technologies.

WAI-ARIA is as important to assistive technology presentation as CSS is to visual presentation. Join us to help make WAI-ARIA as reliable as CSS.

In order to join the group, you will need a W3C account. Please note, however, that W3C Membership is not required to join a Community Group. Complete details may be found at this link…

This is a community initiative. This group was originally proposed on 2018-11-30 by Matthew King. The following people supported its creation: Matthew King, Laura Fathauer, Shadi Abou-Zahra, David Sexton, Mark McCarthy, Aaron Leventhal. W3C’s hosting of this group does not imply endorsement of the activities.

 

ARIA – What should we know?

ARIA W3C logoAccording to the World Wide Web Consortium (W3C), “…ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies. Currently certain functionality used in Web sites is not available to some users with disabilities, especially people who rely on screen readers and people who cannot use a mouse. ARIA addresses these accessibility challenges, for example, by defining new ways for functionality to be provided to assistive technology. With ARIA, developers can make advanced Web applications accessible and usable to people with disabilities.”

But some critics have said that ARIA has “tried to be too many things to too many people” and has resulted in more problems that solutions. This recent blog article by WebAIM summarizes the controversies and gets into some of the nitty-gritty on ARIA. Be aware that this is rather technical stuff; something directed mostly to web developers.