The 5 Rules of ARIA

Leave a comment on The 5 Rules of ARIA

Directly from the spec, the 5 Rules of ARIA:

  1. If you can use a native HTML element or attribute with the semantics and behavior you require already built in […] then do so.
  2. Do not change native semantics, unless you really have to.
  3. All interactive ARIA controls must be usable with the keyboard.
  4. Do not use role="presentation" or aria-hidden="true" on a focusable element .
  5. All interactive elements must have an accessible name.

That first rule is like music to my ears … embrace the platform, folks!

Published by Bramus!

Bramus is a frontend web developer from Belgium, working as a Chrome Developer Relations Engineer at Google. From the moment he discovered view-source at the age of 14 (way back in 1997), he fell in love with the web and has been tinkering with it ever since (more …)

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.