UI Component Accessibility Testing via Dynamic Interaction Simulation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for accessibility testing of User Interface (UI) components are inadequate, as they often rely on manual processes and do not effectively simulate dynamic user interactions, leading to incomplete validation of accessibility compliance.

Innovation Solution

A method and system for analyzing Web content that involves simulating dynamic user interactions with target UI components, monitoring their reactions, and validating accessibility compliance based on these interactions, using a combination of static and dynamic evaluators.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If manual accessibility testing is used, then testing complexity is reduced, but testing completeness and reliability deteriorate

Engineering Contradiction:
Improvetesting complexityVSAvoidaccessibility validation reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system performs self-testing by automatically executing code that simulates user interactions with UI components. The executable code includes static evaluators that analyze accessibility parameters and dynamic evaluators that simulate user actions, allowing the system to test itself without requiring manual intervention while maintaining high reliability and completeness.

Inventive Principle:
Principle #25Self-service

2Productivity

If automated accessibility testing is implemented, then testing completeness improves, but device complexity increases

Engineering Contradiction:
Improvetesting completenessVSAvoidtesting system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The testing system is segmented into distinct evaluators: static evaluators that analyze accessibility parameters at given points in time, and dynamic evaluators that simulate user interactions. This segmentation allows complex accessibility testing to be broken down into manageable, modular components that can be executed systematically without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The executable code is designed to be universal, handling multiple types of UI components and accessibility checks through a single framework. The same code structure can test different UI components (buttons, inputs, lists) against various accessibility standards (WCAG, ARIA), reducing overall system complexity while maintaining comprehensive testing capability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Measurement precision

If dynamic user interaction simulation is added, then accessibility validation accuracy improves, but testing time increases

Engineering Contradiction:
Improveaccessibility validation accuracyVSAvoidtesting time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary analysis by executing static evaluators before dynamic interaction simulation. Static evaluators analyze accessibility parameters at given points in time to establish baseline conditions, and dynamic evaluators then simulate user interactions to verify behavior. This preliminary action ensures that time-consuming dynamic testing is performed only when necessary, optimizing the balance between accuracy and testing time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250036562A1User Interface (UI) Component Accessibility Testing
Publication Date: 2025.01.30 EVINCED INC
  • US20250036562A1 patent drawing
  • US20250036562A1 patent drawing
  • US20250036562A1 patent drawing

AI summary

A method for analyzing Web content includes receiving a request to validate accessibility compliance of a target User Interface (UI) component in the Web content. In response to the request, executable code is run, including (i) simulating dynamic user interaction with the target UI component, (ii) monitoring a reaction of the target UI component to the simulated user interaction, and (iii) validating the accessibility compliance of the target UI component based on the reaction to the simulated dynamic user interaction.