Runtime Object Model for Context-Aware Accessibility Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods are inefficient and resource-intensive for testing software applications for accessibility compliance, particularly for rich user interfaces and dynamically assembled screens, as conventional tools cannot evaluate context and are limited to HTML-level testing.
Innovation Solution
Systems and methods that expose semantic information for user interface elements at runtime through an object model, allowing for context-aware accessibility checks and compliance testing with standards like Section 508, using an object model generator, accessibility checking tool, and application object model exerciser.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Difficulty of detecting and measuring
If conventional HTML-level testing tools are used, then testing process is simple, but context evaluation capability is insufficient and cannot handle dynamically assembled screens
Solution Approach 1:
The patent introduces an intermediary layer (object model) between the application and the testing tool. This object model captures semantic information about user interface elements at runtime, enabling context-aware accessibility checks without requiring the testing tool to directly analyze complex dynamic screen assemblies. The intermediary translates complex runtime states into testable representations.
Solution Approach 2:
The system performs preliminary actions by extracting and capturing semantic information about user interface elements during application runtime. This preliminary data collection enables subsequent accessibility testing to be performed efficiently with full context awareness, as the necessary information is already prepared and structured in the object model.
2Reliability
If thorough accessibility testing is performed manually, then testing completeness is high, but time consumption and resource requirements increase significantly
Solution Approach 1:
The accessibility testing system performs self-service by automatically executing comprehensive accessibility checks against the object model without requiring manual intervention for each check. The system autonomously navigates the object model, evaluates accessibility rules, and generates reports, maintaining testing completeness while dramatically reducing time investment compared to manual methods.
Solution Approach 2:
The patent replaces manual mechanical testing processes with automated computational processes. Instead of human testers manually navigating and evaluating each interface element, the system uses computer-based automated testing that processes the object model to verify accessibility compliance, achieving both thoroughness and efficiency.
3Measurement precision
If accessibility testing is performed on dynamically assembled screens, then testing accuracy is improved, but testing efficiency decreases due to runtime requirements
Solution Approach 1:
The system captures semantic information about user interface elements during application runtime as a preliminary step. This preliminary extraction of contextual data enables subsequent accessibility testing to be performed efficiently with high accuracy, as the necessary information is already structured in the object model rather than requiring real-time analysis during testing.
Solution Approach 2:
The patent extracts and stores more semantic information than strictly necessary for a single test execution. This excessive data capture during runtime ensures that all required contextual information is available for comprehensive accessibility checking, maintaining both accuracy and enabling efficient retesting without re-executing the application.
Data Source
AI summary
Systems, methods, and computer program products consistent with the invention expose semantic information for the user interface elements of an application at runtime as part of a rich object model and check accessibility requirements compliance, such as Section 508 compliance, for each user screen or other user-interface that the application presents. In some embodiments, accessibility checks are based at least in part on the context of the user interface elements as exposed through the object model.