Published Sep 3, 2019

SE-Radio Episode 329 Andreas Stefik on Accessibility for the Visually

Andreas Stefik explores the intricacies of designing accessible programming languages for visually impaired users, emphasizing intuitive syntax, empirical research, and the critical role of screen readers and accessibility standards in enhancing usability.
Episode Highlights
Software Engineering Radio - the podcast for professional software developers logo

Popular Clips

Episode Highlights

  • Screen Readers

    Screen readers are essential tools for visually impaired users, providing both content and navigation cues. explains that these devices, such as VoiceOver on Mac and NVDA on Windows, help users understand their location on a webpage through the "where am I?" problem, a concept coined by Joan Francione 1. This involves conveying the semantics of a webpage, like headings and paragraphs, to aid navigation.

    The screen reader tries to give you both a sense of the content and a sense of like, where you are on the page.

    ---

    For apps, the accessibility varies by platform, with Apple’s VoiceOver using gestures to interact with content, allowing users to tap and hear app names before selecting them 2.

       

    Navigation

    Navigating digital content, especially in coding environments, presents unique challenges for visually impaired users. highlights that while screen readers can navigate code, understanding complex methods requires memorization, unlike sighted developers who can quickly glance at code 3. This makes comprehension slower and different, not necessarily harder.

    If I'm looking at a screen of code, I can kind of glance up and down to get very quick context. That's a little bit harder if you're blind.

    ---

    The academic community lacks sufficient data on programming language accessibility, especially for diverse groups, indicating a need for more research to create inclusive tools 4.

       

    Improvement

    Improving screen reader accessibility requires strategic approaches and awareness of diverse user needs. suggests that developers should test their tools with screen readers and consider hiring consultants to ensure accessibility 5. This includes addressing issues like color contrast and magnification for the visually impaired, beyond just the blind community.

    A lot of the issues that you do with accessibility, they tend to have these other little benefits. Like your site is generally easier reading.

    ---

    Inconsistencies in IDE accessibility, such as broken features or illogical interfaces, can hinder both learners and professionals, highlighting the need for consistent and thoughtful design 6.

Related Episodes