Useful books and resources - LinkedIn post
Accessibility For Designers Checklist (PDF: https://lnkd.in/e9Z2G2kF), a practical set of cards on WCAG accessibility guidelines, from accessible color, typography, animations, media, layout and development — to kick-off accessibility conversations early on. Kindly put together by Geri Reid.
WCAG for Designers Checklist, by Geri Reid
Article: https://lnkd.in/ef8-Yy9E
PDF: https://lnkd.in/e9Z2G2kF
WCAG 2.2 Guidelines: https://lnkd.in/eYmzrNh7
Accessibility isn’t about compliance. It’s not about ticking off checkboxes. And it’s not about plugging in accessibility overlays or AI engines either. It’s about *designing* with a wide range of people in mind — from the very start, independent of their skills and preferences.
In my experience, the most impactful way to embed accessibility in your work is to bring a handful of people with different needs early into design process and usability testing. It’s making these test sessions accessible to the entire team, and showing real impact of design and code on real people using a real product.
Teams usually don’t get time to work on features which don’t have a clear business case. But no manager really wants to be seen publicly ignoring their prospect customers. Visualize accessibility to everyone on the team and try to make an argument about potential reach and potential income.
Don’t ask for big commitments: embed accessibility in your work by default. Account for accessibility needs in your estimates. Create accessibility tickets and flag accessibility issues. Don’t mistake smiling and nodding for support — establish timelines, roles, specifics, objectives.
And most importantly: measure the impact of your work by repeatedly conducting accessibility testing with real people. Build a strong before/after case to show the change that the team has enabled and contributed to, and celebrate small and big accessibility wins.
It might not sound like much, but it can start changing the culture faster than you think.
Useful resources:
Giving A Damn About Accessibility, by Sheri Byrne-Haber (disabled)
https://lnkd.in/eCeFutuJ
Accessibility For Designers: Where Do I Start?, by Stéphanie Walter
https://lnkd.in/ecG5qASY
Web Accessibility In Plain Language (Free Book), by Charlie Triplett
https://lnkd.in/e2AMAwyt
Building Accessibility Research Practices, by Maya Alvarado
https://lnkd.in/eq_3zSPJ
How To Build A Strong Case For Accessibility,
↳ https://lnkd.in/ehGivAdY, by 🦞 Todd Libby
↳ https://lnkd.in/eC4jehMX, by Yichan Wang
#ux #accessibility
Over the years, I've also been publishing a few posts here on LinkedIn on accessibility that you might find helpful as well:
Accessibility: https://lnkd.in/ekq2q7Zb
Autism: https://lnkd.in/ekujAteM
Children: https://lnkd.in/eh3fv-US
Colorblindness: https://lnkd.in/eqjvPgSZ
Color contrast: hhttps://lnkd.in/ecWS4ue7
Deafness: https://lnkd.in/ejVYAvud
Dyscalculia: https://lnkd.in/e8wyMWp4
Dyslexia: https://lnkd.in/ei9mncR7
Legibility: https://lnkd.in/eEarXzD8
Left-Handed Users: https://lnkd.in/eWyzRdy5
LGBTQI: https://lnkd.in/eumCiYrk
Mental Health: https://lnkd.in/eEaXjs9x
Older Adults: https://lnkd.in/e54f2FT2
Screen readers: https://lnkd.in/eaviMFkf
Target sizes: https://lnkd.in/ePuc3mbJ
Teenagers: https://lnkd.in/et3XbUTJ
Templates: https://lnkd.in/ey3ua5b7
WCAG 2.2: https://lnkd.in/eYmzrNh
Deafness ranges across a continuum: from minor to moderate to profound hearing loss. It can also be situational and temporary, as people with “normal” hearing (0 to 25 dB hearing loss) will always encounter situations where they can’t hear — e.g. due to background noise.
Useful resources:
Beyond Video Captions and Sign Language, by Svetlana K.
https://lnkd.in/dMeU9SAe
Designing For Deaf People Helps Everyone, by Marie Van Driessche
https://lnkd.in/dBj6e4nJ
Best Practices For CC and Subtitles UX, by Vitaly Friedman
https://lnkd.in/e26EKXph
Web Accessibility for Deaf Users
https://lnkd.in/dpv_n-4J
Inclusive Design Toolkit
https://lnkd.in/dc6RDhcR
What It’s Like To Be Born Hard of Hearing, by Twanna A. Hines, M.S. (Substack)
https://lnkd.in/dkNJC8_v
Dax Castro post:
Microsoft Word is said to be one of the best applications for making accessible documents, but how true is that claim? There are a lot of practices that designers use that set them back while working within Word. Join Chad Chelius, ADS and Dax Castro, ADS as they talk about some of the most common issues document creators encounter when working within this application, best rules to follow to avoid those issues, and how to remediate your document when issues arise.
Listen in and learn why you should use caution with templates, missing or artifact document covers within the header, title tags versus H1 tags, accessible links in the footer, how to turn off auto-generated alt-text, bulleted lists and 2 column layouts, creating an automated table of contents, and layout tables.
Full episodes are streaming on your favorite podcast platform
Full Episode on Youtube: https://lnkd.in/dYE4eGCH
Time Stamps
• 0:00 - Introduction
• 2:13 - Introducing the Topic
• 3:03 - Using Caution with Pre-Built Templates
• 5:15 - Document Cover and Headers
• 7:35 - Title Tag Versus H1 Tag
• 13:11 - Accessible Links in the Footer
• 20:04 - How to turn off Auto-generated Alt-text
• 25:05 - Bulleted Lists and 2 Column Layouts
• 29:22 - Manual Table of Contents
• 35:13 - Layout Tables
Episode Resources:
How does my Bulleted List Sound Document?
https://lnkd.in/d7DRVAxR
Learn More about axesWord Demonstration
https://lnkd.in/d3Y7QakY
Creating Accessible Dot Leaders By Chad Chelius
https://lnkd.in/dBPq-YPa
Are Track Changes Accessible? By Dax Castro
https://lnkd.in/d-CZhkQi
Follow Us Online!
Follow Chax on LinkedIn: https://lnkd.in/gMZ8jhjG
Follow Chad Chelius on LinkedIn: https://lnkd.in/geeyU-bD
Follow Dax Castro on LinkedIn: https://lnkd.in/gqbRJTx4
Join our Facebook Group: https://lnkd.in/dpsZatnV
Find our upcoming Classes and Episode Transcript: https://lnkd.in/gU6_TR94
Learn more about Tamman, Inc at https://tammaninc.com/
ADHD




Comments
Post a Comment