ဤအပိုင်းအကြောင်း
01:14 - Chris’s Superpower: His Ability to Sleep.
01:50 - Why Chris Wants To Talk About Web Accessibility
- Top 3 Priorities When Building on the Web
- Accessibility
- Performance
- Security
02:45 - Whose Responsibility Is It To Build An Accessible Web?
- Anyone Building On The Web
- Dominos’ Lawsuit
- WCAG
07:38 - How To Inform And Get Colleagues On Board With Accessibility
- Understanding The Clientele
- Have Numbers To Back It Up
11:45 - Image Descriptions
- Alt Attributes
- Twitter Adds Alt Text For .gifs
16:34 - Companies Deal With Accessibility Lawsuits
19:07 - Where To Start Making Changes
- Only Shipping One Experience That Works For Everybody
- Make Sure You Are Using Semantic Markup
- Color Contrast
- Make Sure There Are Alt Attributes On Your Images
27:50 - What Can Developers Do Today To Make Changes
- Start With An Audit
- Compare To Competitors
31:06 - Work Collaboratively With The Designers
34:15 - How To Be Accessible For Various Disabilities
- Hearing
- Cognitive
- Physical
37:10 - Accessibility Can Benefit Everyone
Reflections:
Chris: Accessibility is not a requirement, it is a must. From Marcy Sutton: Every little bit of accessibility you contribute is so necessary and so needed.
Carina: The concrete useful examples such as audits are beneficial to business people.
Jacob: Wants to get better at using a screen reader to gain empathy about what the right thing is to do.
This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode
To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.
Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks!
Special Guest: Chris DeMars.
