Creating Accessibility Reports Designers & Developers Will Love

Session Evaluation

Class description

What are the best practices for reporting accessibility problems and remediation solutions to designers and developers? What features can you include so they love your accessibility report? Screenshots of each issue? Code Snippets? Live Demos? Screencasts? What about Collaborating with Multiple Accessibility Testers?

This session will focus on accessibility reporting on WCAG 2.0 Level AA requirements using Apple’s iWork Suite’s Numbers app. For a newbie to Accessibility, including screenshots of the accessibility violation is much easier than including a code snippet or trying to explain the intricacies of the screen reader behavior when the problem occurs. We’ll discuss common problems and best practices for collaborating with multiple testers on one accessibility report. For example how do you handle reporting an accessibility issue that repeats itself on multiple pages? Do you do a project wide issue section or include that same problem on every page or tab in the report? How do you avoid multiple testers documenting the same accessibility problem twice or reporting it inconsistently? What are best methods for reviewing a co-workers accessibility report to check for accuracy and train them to be a better tester?

This session will show you how to create an awesome accessibility report that developers and designers will learn from and actually love.


Paul Adam


May 17th, 2017


2:15 pm-3:45 pm

Class level


Class type






Take Aways

  • Accessibility Testing
  • Accessibility Reporting
  • Screenshots of Accessibility Problems
  • Code Snippets of Accessibility Issues
  • Documenting User Impact Level
  • Project-Wide and Component Issues
  • Conveying Accessibility Problems and Solutions to Designers, e.g. Color Contrast
  • Peer Review and QA of Accessibility Report


Room TH 117

Session Evaluation

  • Tell us what you thought of this class!