#GAAD #a11y #BugBash Global Community Effort to Squash Accessibility Bugs

Celebrate Global Accessibility Awareness Day with Deque and the #a11y Community by helping file accessibility bug reports with assistive technology vendors and web browser developers.


The plan is to ask everyone involved in GAAD and #a11y on Twitter to file as many UA/AT accessibility related bugs as they can handle and post what bugs they’ve filed to the GAAD Bug Bash Google Spreadsheet Tracker.

#GAAD #a11y #BugBash Tracker


The GAAD Bug Tracker is a publicly editable Google Spreadsheet that should be accessible and available for anyone to add new bugs. So far I’ve listed column headers for what a typical bug report needs and typed in a few bugs that I’ll be filing personally :).

Work in Progress, Always Happy To Evolve

This is a community effort so please leave comments with suggestions or find me on twitter @pauljadam to provide feedback. Thanks!

So far the column headers I’ve listed are:

  1. Bug #
  2. Title
  3. Description
  4. Steps to Reproduce
  5. Expected Results
  6. Actual Results
  7. Screenshot
  8. Platform
  9. User Agent
  10. Assistive Technology
  11. Impact
  12. Status
  13. URL to Bug Report
  14. Bug Report ID#
  15. Bug Reported By
  16. Additional Notes

Where to File Bugs?

Now where would we file all these bugs to exactly? Well it depends on if it’s a browser (User Agent) bug or a screen reader/assistive technology bug. Not all UA/AT vendors have public bug trackers or any bug tracker but most do. Many of the bug trackers also have bug reporting guidelines to show you how to file a actionable bug report that we hope will actually get fixed one day 🙂

Current List of Bug Tracker Systems
Bug Tracker URL Details/Bug Reporting Guidelines Bug Type
Apple Bug Reporter http://bugreport.apple.com Screen Reader
Assistive Technology
Native iOS/OS X
Open Radar http://www.openradar.me Open radar is a way make your bug reports with Apple public as their tracker is not searchable. This does require you to file both with apple and with open radar (to let the world know). Screen Reader
Assistive Technology
Native iOS/OS X
Chromium bug tracker https://code.google.com/p/chromium/issues/list http://www.chromium.org/for-testers/bug-reporting-guidlines-for-the-mac-linux-builds Browser
Internet Explorer Feedback https://connect.microsoft.com/ie/ https://connect.microsoft.com/IE/content/content.aspx?ContentID=29582 Browser
Bugzilla@Mozilla https://bugzilla.mozilla.org https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines Browser
NVDA Issues http://community.nvda-project.org/wiki/Issues Screen Reader
Webkit bugzilla https://bugs.webkit.org/ https://bugs.webkit.org/page.cgi?id=bug-writing.html Browser
GNOME (Orca) Bugzilla https://bugzilla.gnome.org/enter_bug.cgi?product=orca Screen Reader

Steve Faulkner’s filing bugs tutorial

Duplicate Bug Reports

The issue of duplicate bug reports is a problem with non-public bug trackers like Apple’s. I’ve filed bug reports with apple only to find out they were duplicates but once you find that out there’s no actual way to search the bug tracker to read what the previous person’s bug report says. So you basically have to take them at their word that someone else really did file the same #a11y bug as you!

The community solution to Apple’s secrecy is www.openradar.me where you basically have to file a duplicate bug report to let the community know about the bug and ask them to promote it being fixed by duplicating the same issue into the official apple bug reporter.

Promoting Bug Reports or The Popularity of an Accessibility Bug

Some public bug trackers allow registered users to “Star” or Favorite an issue to hopefully get it more attention and fixed faster.

vote for issue

Vote for this issue and get email change notifications.

Another accessibility bug tracking project of note is the a11y bugs project, http://a11ybugs.org. Though it has not been updated in 2 years based on the last tweet. https://twitter.com/a11ybugs/status/358253366964523008

You can also search for “Accessibility” in the bug trackers to find a11y bugs already entered.

Please File Accessibility Bugs for #GAAD! Thanks!

Here is the bug tracker with all the info you need to fill out and links to the various bug reporting systems.

#GAAD #a11y #BugBash Tracker


Please make sure to report the bugs you’ve filed so others can duplicate them if they are serious issues or they just want to call more attention to Accessibility for GAAD.

Also please feel free to leave a comment on this post with the bug you filed or any other suggestions, questions, or comments.

The bugs can be filed starting now and on GAAD we’ll get them even more attention, star them, dupe them, tweet, and promote the issues caused by bugs in assistive technologies and browsers that do make accessibility more difficult and less “Global”.

One Reply to “#GAAD #a11y #BugBash Global Community Effort to Squash Accessibility Bugs”

  1. Hi Paul,
    I wondered for the column, would it be useful to have a column for when the bug was logged? and what version of operating system, browser, and screen reader? I thought it would help in instances where there’s a recent upgrade, or if the date is later, then I know there might be a chance it was addressed.

Leave a Reply

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