Cross-Platform Accessibility via Metadata Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies face challenges in providing seamless cross-platform accessibility, particularly in allowing users to leverage platform-native accessibility tools across different devices, leading to inconsistencies and increased processing and memory costs.
Innovation Solution
The implementation of an event metadata monitoring engine and filtering engine on the remote device, combined with a translation engine on the host device, enables cross-platform accessibility by filtering and transforming metadata to create a native accessibility experience, allowing users to interact with remote devices through their host device's native controls.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If cross-platform remote access is implemented to allow users to interact with remote devices, then user accessibility and device compatibility are improved, but processing costs and memory usage increase
Solution Approach 1:
The patent extracts and transmits only accessibility-relevant metadata from the remote device to the host device, rather than transmitting all device data. The metadata filtering engine identifies and extracts only the necessary accessibility information, significantly reducing processing requirements while maintaining accessibility functionality.
Solution Approach 2:
The patent segments the accessibility experience into distinct components: metadata generation on the remote device, filtering of metadata to extract accessibility-relevant information, translation of metadata format, and execution by the host device's accessibility engine. This segmentation allows each component to operate independently and efficiently.
2Loss of information
If all event metadata is transmitted from remote device to host device, then accessibility information completeness is improved, but data transmission volume and processing overhead increase
Solution Approach 1:
The metadata filtering engine extracts only accessibility-relevant metadata from the complete set of event metadata generated by the remote device. This extraction process maintains all necessary accessibility information while eliminating redundant data, reducing transmission volume without compromising information completeness.
Solution Approach 2:
Instead of transmitting all metadata or using a simplified subset, the system applies partial action by selectively transmitting only the specific portion of metadata that is relevant to accessibility. This targeted approach avoids both the waste of transmitting unnecessary data and the loss of critical accessibility information.
3Ease of operation
If platform-specific accessibility tools are used on each device, then native accessibility experience is improved, but cross-platform compatibility deteriorates
Solution Approach 1:
The patent introduces metadata as an intermediary that bridges different platforms. The metadata captures accessibility-relevant information from the remote device in a standardized format, which can then be processed by the host device's native accessibility engine, enabling cross-platform compatibility while preserving native accessibility functionality.
Solution Approach 2:
The translation engine changes the parameters of the metadata from the remote device's native format to a format compatible with the host device's accessibility engine. This parameter transformation allows the host device to process and execute accessibility operations using its own native tools, achieving both cross-platform compatibility and native accessibility experience.
4Measurement precision
If full metadata processing is performed on the host device, then accessibility accuracy is improved, but processing time and resource consumption increase
Solution Approach 1:
The patent performs preliminary filtering of metadata on the remote device before transmission to the host device. The metadata filtering engine pre-processes the data to identify and extract only accessibility-relevant information, reducing the amount of data that requires detailed processing on the host device and thereby reducing processing time while maintaining accuracy.
Solution Approach 2:
The processing workload is segmented between the remote device and the host device. The remote device handles metadata generation and initial filtering, while the host device focuses on translating and executing accessibility operations. This segmentation distributes processing tasks efficiently, improving overall system responsiveness and reducing bottlenecks.
Data Source
AI summary
In non-limiting examples of the present disclosure, systems, methods and devices for assisting with cross-platform user experience accessibility are provided. A real-time connection between a remote device and a host device may be established. The remote device may apply a plurality of rules to event metadata that it generates. The filtered event metadata corresponding to a plurality of user experience events occurring on the remote device may be received by the host device. One or more transforms may be applied to the filtered event metadata on the host device. A native accessibility experience corresponding to each of the plurality of user experience events may be provided by the host device based on the transformed event metadata.