An Extension-Based Accessibility Framework for Making Blockly Accessible to Blind and Low-Vision Users

TL;DR

Block-based programming environments are widely used in education but remain inaccessible to blind and low-vision learners. The authors propose an Extension-Based Accessibility Framework (EAF) that integrates accessibility into Blockly-based BBPEs without forking the core library, featuring a 3D navigation model, stack labeling, mode-based editing, and WAI-ARIA–driven screen-reader support. They validate EAF through integration tests on two BBPEs with 177 test cases and a semi-structured interview with four participants using VoiceOver, JAWS, and NVDA, achieving an 85.9% pass rate and positive feedback on navigation and mental models. The work demonstrates a scalable, cross-platform path to accessible block-based programming with potential for widespread adoption in K-12 curricula.

Abstract

Block-based programming environments (BBPEs) such as Scratch and Code.org are now widely used in K-12 computer science classes, but they remain mostly inaccessible to blind or visually impaired (BVI) learners. A major problem is that prior accessibility solutions have relied on modifications to the Blockly library, making them difficult to apply in existing BBPEs and thereby limiting adoption. We present an Extension-based Accessibility Framework (EAF) to make BBPEs accessible for BVI students. The framework uses a modular architecture that enables seamless integration with existing Blockly-based BBPEs. We present an innovative three-dimensional (3D) hierarchical navigation model featuring stack labeling and block numbering, mode-based editing to prevent accidental modifications, and WAI-ARIA implementation to ensure compatibility with external screen readers. We evaluated our approach by integrating the EAF framework into two BBPEs (covering 177 test cases) and conducting semi-structured interviews with four participants using VoiceOver, JAWS, and NVDA. Participants reported clearer spatial orientation and easier mental model formation compared to default Blockly keyboard navigation. EAF shows that modular architecture can provide comprehensive accessibility while ensuring compatibility with existing BBPEs.

Figures (5)

• Figure 1: Extension-based Accessibility Framework (EAF) Architecture
• Figure 2: 3D Navigation Model Abstraction and Layers
• Figure 3: 3D Navigation Model with Keys
• Figure 4: Context-aware Edit Mode
• Figure 5: EAF Blockly Workspace with stack labels and block numbers