Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
If you work mostly on the back-end of the tech stack, it's easy to assume that your role is disengaged from accessibility concerns. After all, that's the front-end's job! However, there are multiple, specific ways back-end devs can impact accessibility: primarily, for colleagues and fellow programmers. https://www.wnb-rb.dev/meetups/2024/07/30
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
In the video titled "How to Accessibility if You're Mostly Back-End," speaker Hilary Stohs-Krause, a senior software engineer at Red Canary, discusses the often-overlooked role of back-end developers in accessibility. The primary message is that back-end developers can significantly impact accessibility for their colleagues and fellow programmers, even if they are not directly involved in front-end design. The session begins by defining accessibility, emphasizing that it is not solely about making technology usable for external users but also for internal users—specifically colleagues with various disabilities. Statistically, about 16% of the global population has some form of disability, highlighting the need for accessibility features in all aspects of software development. Key points discussed include: - **Understanding Disabilities**: Accessibility is critical not just for users with known disabilities but also for co-workers who may face temporary or situational challenges. Back-end developers have the opportunity to minimize struggle for everyone by adopting inclusive coding practices. - **Coding for Accessibility**: The speaker covers specific coding practices that improve accessibility, such as avoiding abbreviations, ensuring readability, and using descriptive naming conventions. She stresses that clarity in code helps everyone, including screen readers and non-native speakers, to understand the functionality better. - **Linters and Code Consistency**: Utilizing linters is suggested to maintain code consistency and predictability, which supports all developers. Good naming conventions and well-structured code enhance both accessibility and maintainable codebases. - **Enhanced Documentation**: The necessity of clear documentation is emphasized—it should be accessible and up-to-date, allowing for effective collaboration. Using simple language, avoiding ambiguous terms, and providing context in comments were highlighted as essential practices. - **APIs and Specifications**: Best practices for making APIs more accessible through descriptive fields and clear separation of words were discussed, with an emphasis on avoiding abbreviations. - **Implications for Testing and Specifications**: Testing specs should be comprehensive and narratively structured to ensure clarity in the code's functionality and expected behavior. - **Environmental Considerations**: The talk concludes by addressing organizational policies that support accessibility, like flexible work schedules and appropriate tools for developers with disabilities. In conclusion, Stohs-Krause urges back-end developers to take small, deliberate steps that can lead to significant improvements in accessibility. Her overarching takeaway is that even backend developers can make a positive impact on accessibility for their teams and that striving for accessibility is both a professional and moral responsibility.
Suggest modifications
Cancel
