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

  • Design Principles

    Designing accessible programming languages involves simplifying syntax to accommodate screen readers and novice programmers. highlights the importance of intuitive syntax, such as using "repeat" instead of "for" loops, to enhance readability and understanding for visually impaired users 1. He explains that common programming symbols like parentheses and braces can confuse beginners, so alternatives like the word "end" are used in Quorum to clarify code structure 2.

    Oddly enough, we even designed test cases where we used them both right next to each other to try to trip novices up because we were thinking, if we're gonna overload it, that's gotta fall. P yup. Turns out not.

    ---

    These design choices not only aid blind programmers but also make programming more accessible for all novices.

       

    Empirical Studies

    Empirical research plays a crucial role in developing accessible programming languages. discusses how studies have shown that dynamic typing can slow down programmers, especially those who are visually impaired, due to navigation challenges 3. He emphasizes the need for evidence-based design, noting that some features, like lambdas, may not benefit novices and can even hinder their learning 4.

    We found that the experts had no benefit at all and it basically crushed all of the novices.

    ---

    This research-driven approach ensures that programming languages evolve to meet the needs of diverse users.

       

    IDE Accessibility

    Integrated Development Environments (IDEs) often face challenges in maintaining accessibility for visually impaired users. notes that while some IDEs like Visual Studio offer accessibility features, they can be inconsistent across updates, affecting usability 5. He also highlights the potential of talking debuggers, which provide context about code changes, as a valuable tool for both visually impaired and sighted developers 6.

    Simple little things can sometimes make a big difference for accessibility.

    ---

    These features demonstrate how accessibility improvements can benefit all users, not just those with disabilities.

Related Episodes