“ Neil Lenane Talent Acquisition/Diversity and Inclusion Leader Progressive Insurance If you do not intentionally include, you unintentionally exclude.
The Business Case for Accessibility • Return on Disability Group Annual Report (PDF) www.rod-group.com/sites/default/files/2016 Annual Report - The Global Economics of Disability.pdf • The Financial Brand thefinancialbrand.com/68136/pwd-banking-disabled-customer-ada/ • How to Attract and Maintain Customer Loyalty odenetwork.com/news/how-to-attract-maintain-customer-loyalty • How much do bugs cost to fix during each phase of the SDLC? www.synopsys.com/blogs/software-security/cost-to-fix-bugs-during-each-sdlc-phase/
“It doesn't mean you're designing one thing for all people. It means you're designing a diversity of ways for people to participate in an experience, so that everyone has a sense of belonging. Susan Goltsman Founding Principal of MIG, Inc. Co-author of Play for All Guidelines and The Inclusive City
Product / Project Managers • Understand accessibility and how it applies to your project • Communicate with and support all team members • Think about a11y throughout process • Engage with and represent users • Hold team accountable, escalate when needed • Stay firm
Executive / C Suite • Understand accessibility and how it applies to your organization, departments and staff • Understand risks and benefits • Build accessibility into the budget • Be an advocate
• Devise consistent navigation • “Chunk” content, embrace lists • Use headings, sub-headings • Transcribe audio • Caption video • Craft appropriate alt text • Document instructions for forms and uncommon workflows • Document form error handling and status messages • No images of text
• Use good color contrast • Don’t use color alone for meaning • Provide visible focus (“outlines”) • Design bypass blocks (“skip navigation”) • Ensure labels are on all form fields • Design error and status messages • Use proximity for related elements.Ensure text spacing • Designs scale/adjust for varying viewports • Use images, icons thoughtfully
• Implement keyboard support & skip link(s) • Make visual focus order match source code order • Use semantic HTML • Include page landmarks • Properly code headings • Properly associate labels with form fields • Use ARIA wisely • Test with a screen reader • Test with a keyboard • Test with high contrast • Validate code
Quality Assurance • Develop test plans with accessibility built-in • Use automated tools where practical • Use manual testing for full coverage • Reduce false positives • Act as accessibility safety net
Gutenberg Editor • Known a11y issues • Not ready for production teams that need a11y • Can still support accessible authoring • Classic Editor plugin wordpress.org/plugins/classic-editor/
emilylewis
mhrtech
taka2noda
isaoshimizu
keio_smilab
devops_vtj
takaking22
iwamot
nyankotaro
dzeyelid
sakaguchi
kthrtty
yayoi_dd
kneath
jonrohan
jeffersonlam
mraible
chriscoyier
soudai
denniskardys
palkan
mojombo
jasonvnalue
sstephenson
geoffreycrofte