derek featherstone: web accessibility (webdagene 2013)
DESCRIPTION
TRANSCRIPT
Why should that interface be accessible?
How would we make that accessible?
To whom should it be accessible?
• blind• low-vision• hearing• mobility/dexterity• cognitive• speech
erceivableperablenderstandableobust
POUR
w3.org/WAI
P O U R
Focuses on user needs, not technology.
Web Accessibility is a Design Tool
Accessibility is part of User Experience.
extremes extremes
Accessibility is not binary, all-or-nothing, black and white. We have every shade of grey in between. How you view this point frames everything that you learn and do about accessibility.
The checklist is a starting point, not an end point.
Just because something is compliant, doesn’t mean it will be easy to use.
How can we get beyond the checklist?
Great design, technical excellence, the right content and functionality.
Great design, technical excellence, the right content and functionality.
PRINCIPLE 1
Start with content
Content specific to people with disabilities?
PRINCIPLE 2
Move from what to why.
Overlapping Map Polygons: Non-visual access
Different method to get the same information(Fictitious) proposed boundary changes, City of Ottawa
Does this change affect you?Use our Postal Code lookup:Postal code:
Search
PRINCIPLE 3
Out of sight, out of mind.
GROUP CLOSELY RELATED ITEMS
Layout: Proximity for Low-vision users
Layout: Proximity for Low-vision users
Use layout to create the right "chunks"
Use layout to create the right "chunks"
PRINCIPLE 4
Design for Quick Consumption
Front-loaded content
USE HEADINGSFOR QUICK CONSUMPTION
PRINCIPLE 5
Keyboard. Keyboard. Keyboard.
PRINCIPLE 6
Design for forgetfulness.
Summary and Field-level errors
These principles helpmake better, more accessible
designs for everyone.
simplyaccessible.com/newsletter
Accessibility consulting, strategy and assessmentsAccessible development and remediation servicesTraining courses, workshops and conferences
simplyaccessible.com
[email protected]@feather on twitter
Derek Featherstone