Web Accessibility Deliverables

Test Plan and Strategy - September

Testing of First 500 Pages - December

Remediation work 

Final Report for Phase 1- A collaboration project has been created in Basecamp 

• Guidelines

  • CAPTCHA Alternatives Guidelines.docx

  • Testing Guidelines Keyboard, Image, Forms kif-protocol

  • Modal Dialog and Information Overlay Interaction Guide

  • Video, Captions, and Transcripts Guide

  • Document Structure Guide

• Training

  • Intro Training

  • QA Training

• Testing

  • Testing Process

  • Final Manual Test Plan - Desktop Mobile Units 20160209

  • Manual Test Results #2 - icann.org 20160209

  • Manual Test Results #2 - newatlarge 20160209

  • Auto Scan Results - 2016-01-27

  • Manual Test Results #1 - icann.org 20151211

  • Manual Test Results #1 - newatlarge 20151221

  • Final Testing Process Recommendations

  • Initial Manual Test Plan - Desktop Mobile Units - 20151217

  • Simply Accessible Custom Fields List for JIRA

• Report / Presentations 

  • Final Report and Presentation - Feb11 2016

Lessons Learned

• Training created eye-opening new perspective on how code is developed and importance of CSS styling, and KIFs.

• Ramp up of tools, training, and process take time but result in higher payoff in building accessible websites.

• Building Accessible websites generally result in better pleasing websites.

• Front end designer and UX are critical to the process.  

• ICANN has a lot of Accessibility technical debt due to lack of standards, discipline, knowledge, and vendors not required or aware to follow accessibility guidelines.  ICANN should build accessibility checklist and guidelines in procurement before making award.

• All ICANN IT should take the training course, ICANN should expand beyond Development and QA to create the right mind-set.

• Learning was enjoyable and meaningful.  Deep appreciation for the purpose.