We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Walking Down the A11Y Road - Lessons Learnt From Working on Accessibility of A Django Project

1
 Cite
 Share
 Download
 Purchase
No logo availableDjangoCon US
 Matic, Radina

Formal Metadata

Title
Walking Down the A11Y Road - Lessons Learnt From Working on Accessibility of A Django Project
Title of Series
Part Number
43
Number of Parts
52
Author
License
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
- Who we are and how did we meet? WHY DO WE CARE? - 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? 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? 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 - 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