Skip to content

Instantly share code, notes, and snippets.

What would you like to do?

As always, web accessibility specialist Adrian Roselli summed up the situation around the Authoring Practices on one tweet in a brief but tougue in cheek way Source:

There are issues because the patterns are often incomplete, untested, or make use of ARIA in a way that is trying to turn the web into Windows 95. APG patterns are experiments. That is it. Few are production ready, all require testing.

So if Authoring Patterns are about the pure use of ARIA, and some of them can be disputed, incomplete or only partially supported in assistive technology – what can you do about it?

There isn't a silver bullet. But here's my strategy, and in its core is research:

  • Is the pattern of your choice disputed or not? Fortunately, the discussion regarding that is held online at Look into the issue sections of this repository and search for the pattern name specifically.
  • You also need to have support in assistive technology in mind before deciding in favor of one pattern. In a perfect world you would run tests with AT and users, but the next best thing is to look out for discussions regarding the pattern (in the GitHub Repo stated above) and check the page for compatibility data.
  • Check, whether the people known for their accessibility expertise (see chapter 7) have published about the pattern in question. Either in the form of social media updates, blog posts or even example code or
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment