You don’t implement accessibility — you start from it
About
Accessibility, a11y, WCAG... A bunch of designers and developers feel these are optional extras for a project. But caring for accessible user experience transforms the internet into a friendly place for all.
Can you see the content of your mobile app on a sunny day? Are the buttons bulk enough to notice and click them for regular users and the short-sighted or seniors? And if I break my right hand, will I be able to surf through the app’s navigation with my left one?
Lastly — is accessibility needless buzz or an actual requirement?
Don’t assume you can take apart an app right now to make it friendlier. Designers should work on accessibility before they design the first mockup and when teammates create content, the branding, and the code. That’s why they need to grasp how different work areas in a project connect and influence the end-result accessibility.
So how can you start with accessibility and lead a process that you start and end spot-on? Alicja Łagodzińska will be #CrossingPerspectives to debate business vs design, exploring plenty of their personal stories based on real projects and real human needs.
Accessible charts and graphs
Neurodiversity or what UX should know to (even better) design
Designing Accessible Digital Solutions in the Real World: Lessons Learned
Making a mountain out of a molehill. Designing an application accessible to seniors.
Designing for Silver Economy - how to ensure the things we design empower and not exploit the ageing population
Disability or mismatch? Accessibility and inclusion ⊂ UX?
