Description
Walking Down the A11Y Road - Lessons Learnt From Working on Accessibility of A Django Project by Radina Matic
(~ 5 minutes)
- Who we are and how did we meet? WHY DO WE CARE?
(~ 10 minutes)
- Universal Design as a core value
- Who benefits?
- Why making inclusive products makes business sense?
- What liabilities you incur for not making inclusive products? WHAT CAN YOU DO WITH AN ALREADY ROUNDED PRODUCT?
(~ 10 minutes)
BABY-STEPS WITH KA LITE Easy things you can check for and correct fast (titles, headings, aria landmarks, visible focus, alttext for images, meaningful labels for EVERYTHING...)
Bit more tinkering required (menus and navigation, complex forms, accessible color schemes...)
Accessible Multimedia & Documents (offer ALTERNATIVES!)
WHAT SHOULD YOU DO RIGHT FROM THE START OF A NEW PROJECT?
(~ 10 minutes)
KOLIBRI FLIES FOR EVERYBODY - Include a11y requirements into the Usability Style Guide - Take a11y into account when choosing the libraries and frameworks - Follow the standard web semantic - Make accessible web components available from the beginning - Start including a11y automated tests as soon as possible ACCESSIBILITY IN EVERYDAY DEV TEAM LIFE
(~ 10 minutes)
- A11y Pills & lots of passion
- Make accessibility a SHARED responsibility
- Start a Tools Repository (Rome wasn't built in a day)
- Don't rely exclusively on checklists and automated testing (Involve the USERS!)
- No such thing as 100% accessible