Webpage Accessibility Injection Without Source Code Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Adding additional content to webpages, such as accessibility features for users with disabilities, often requires changing the source code, which is complex and labor-intensive, especially for large legacy systems, and conventional methods lack specificity in providing valid accessibility content.
Innovation Solution
A system and method that allow additional content to be injected into webpages without modifying the source code, using a client-server architecture, a rules database, and a controller to identify and apply content rules based on URL identifiers, enabling the provision of accessibility features like audible descriptions for screen readers without altering the original page's source code.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If source code for the webpage is changed to add additional content, then accessibility features can be added, but the complexity and manpower required increase significantly
Solution Approach 1:
The patent separates accessibility content from the main webpage source code by using embedded objects (such as JavaScript objects or data structures) that contain accessibility-specific information. This segmentation allows accessibility features to be added independently without modifying the core webpage structure, thereby reducing complexity while maintaining reliability.
Solution Approach 2:
The patent introduces an intermediary mechanism (embedded objects with identifiers) that bridges the main webpage content and accessibility content. Screen readers or accessibility tools can query these embedded objects to retrieve appropriate accessibility information without requiring changes to the original source code, thus resolving the contradiction between adding features and maintaining simplicity.
2Loss of information
If source code is modified to add accessibility content, then specific accessibility information can be provided, but the effort and time required increase
Solution Approach 1:
The patent embeds accessibility-related information (such as descriptions, labels, or validation rules) directly into the webpage source code as pre-prepared objects during the initial webpage creation. This preliminary action ensures that accessibility information is already available and structured, eliminating the need for time-consuming modifications later when accessibility content needs to be added or updated.
Solution Approach 2:
The patent uses embedded objects that can be copied and reused across multiple webpages or sections. Once accessibility information is defined in an embedded object, it can be referenced multiple times without recreating it, significantly reducing the time required to provide comprehensive accessibility information across large websites.
3Ease of operation
If conventional screen readers parse source code to provide accessibility content, then basic accessibility is achieved, but specific and valid accessibility information is not provided
Solution Approach 1:
The patent introduces embedded objects as an intermediary layer between the source code and screen readers. These objects contain structured accessibility information that screen readers can query using specific identifiers. This intermediary mechanism enables screen readers to access specific and valid accessibility content (such as detailed descriptions, validation requirements, and contextual information) without complicating the basic screen reader operation.
Solution Approach 2:
The patent changes the parameter structure of accessibility information by organizing it into queryable objects with specific identifiers and properties. Instead of relying on screen readers to parse unstructured source code, the embedded objects provide structured parameters that can be efficiently queried and retrieved, enabling screen readers to deliver specific and valid accessibility information while maintaining ease of operation.
Data Source
AI summary
In various example embodiments, a system and method for providing additional content on a webpage are provided. In example embodiments, a server receives a trigger for a rule generation process. In response to the receiving of the trigger, the server initiates the rule generation process. The server receives a selection of an element on a webpage to which additional content is to be added without revising source code for the webpage. A user interface panel is displayed through which inputs to configure a content rule for the element and to configure the additional content to be added to the element are received. The server receives the inputs via the user interface panel, and generates, based on the inputs, a rule set that includes the content rule and the additional content. The rule set is stored to a rules database.