Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
When we think about “accessibility”, most of us associate it with design, HTML, CSS - in other words, the front-end. If you work primarily on the back-end of the tech stack, it’s easy to assume that your role is disengaged from accessibility concerns. In fact, there are multiple ways back-end devs can impact accessibility, both for external users and for colleagues. In this talk, we’ll walk through everything from APIs to specs to Ruby code to documentation, using examples throughout, to demonstrate how even those of us who rarely touch HTML can positively impact accessibility for all.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video "How to Accessibility if You’re Mostly Back-End" by Hilary Stohs-Krause explores the often-overlooked role of back-end developers in promoting accessibility within technology. The discussion emphasizes that accessibility is not just a front-end concern, and that back-end practices significantly influence the overall user experience, particularly for internal users. Key points discussed include: - **Understanding Accessibility**: The speaker clarifies that accessibility extends beyond visual elements and includes holistic experiences affecting various disabilities, including temporary conditions. Statistics on disability impact highlight the importance of being mindful of accessibility in technology development. - **Code and Documentation Practices**: - The speaker urges back-end developers to avoid abbreviations and acronyms to enhance code readability and user comprehension. - Complex coding examples illustrate how providing meaningful variable names leads to clearer code, aiding other developers and tools such as screen readers. - Emphasis is placed on documentation maintenance, ensuring clear instructions that are accessible to a diverse audience, including the use of simple language and avoiding images of code unless necessary. - **Designing for Inclusivity**: - The benefits of accessible design are underscored, with historical examples showing that tools initially created for individuals with disabilities have generalized advantages, thereby benefiting every user. - **Workplace Policies**: The discussion includes recommended engineering policies, such as flexible schedules and using accessible vendors, to create an inclusive work environment for all developers, including those with disabilities. In conclusion, Stohs-Krause encourages back-end developers to take an active role in enhancing accessibility through small, individual efforts, as even minimal changes can positively impact their workplace. By emphasizing communication, documentation practices, and mindful coding, back-end developers contribute to a more accessible environment for everyone. The session reinforces that accessibility is a shared responsibility across the tech stack, urging developers not to dismiss their influence in this critical area.
Suggest modifications
Cancel
