Accessibility Verification Testing via Source Code Feature Extraction
Solution Overview
Problem
Manual testing for accessibility issues, such as keyboard accessibility, is time-consuming and inefficient, often requiring manual intervention and device dependencies.
Innovation Solution
A computer-implemented method and system that automatically detects accessibility issues by identifying and classifying UI elements, extracting features from source code, and building an accessibility issue detection model to identify focusable and non-focusable elements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual testing is used to detect accessibility issues, then testing accuracy can be maintained, but testing time and manual effort increase significantly
Solution Approach 1:
The patent replaces manual mechanical testing processes with an automated computer-based system. The system automatically analyzes source code, extracts features, classifies UI elements, and detects accessibility issues without requiring manual intervention, thereby reducing testing time while maintaining detection accuracy through structured analysis protocols
Solution Approach 2:
The accessibility testing system performs self-service by automatically executing the complete testing workflow including source code analysis, feature extraction, element classification, and issue detection. The system uses its own built-in models and algorithms to conduct testing without external manual testing tools or human operators, enabling autonomous accessibility verification
2Reliability
If manual accessibility testing is performed, then comprehensive accessibility verification can be achieved, but device dependencies and operational complexity increase
Solution Approach 1:
The patent eliminates device dependencies by replacing physical testing equipment and manual operations with a software-based automated system. The system analyzes accessibility issues directly from source code through computational algorithms, removing the need for specialized hardware, screen readers, or manual testing devices while maintaining comprehensive verification capability
Solution Approach 2:
The automated accessibility testing system provides universal functionality by handling multiple testing tasks through a single integrated platform. The system can analyze various UI element types, detect different accessibility issues, and operate across different development environments without requiring separate specialized tools for each testing function
3Productivity
If automated testing is implemented, then testing efficiency improves, but the complexity of the testing system increases
Solution Approach 1:
The patent applies segmentation by dividing the automated testing process into distinct modular components: source code analysis module, feature extraction module, UI element classification module, and accessibility issue detection module. Each component performs a specific function independently, making the overall complex system manageable and easier to implement while maintaining high automation efficiency
Solution Approach 2:
The system performs preliminary actions by pre-defining accessibility rules, extracting features from source code in advance, and classifying UI elements before actual accessibility issue detection. This preparation phase establishes the foundation for automated testing, reducing the complexity of real-time analysis and enabling more efficient automated verification
Data Source
AI summary
A computer-implemented method includes identifying a webpage comprising a set of user interface (UI) elements, analyzing the set of user UI elements to identify a set of interactable elements, classifying the elements of the set interactable elements as either focusable or not focusable, extracting features from source code corresponding to interactable elements of the set of interactable elements classified as focusable, and building an accessibility issue detection model using the extracted features from source code corresponding to focusable interactable elements as training data. The method may further include extracting features from source code corresponding to interactable elements classified as not focusable and updating the accessibility issue detection model using the extracted features from source code corresponding to interactable elements which are not focusable as training data. The method may further include storing one or more passed results and one or more failed results in a results database.



