Patent ID: 12216986

The figures are not exhaustive and do not limit the present disclosure to the precise form disclosed.

DETAILED DESCRIPTION

The computer implemented accessibility system and method has been developed and is described herein. It provides many new features including an accessibility component that acts to modify the display of a website to help the website achieve international accessibility standards. In various embodiments, the computer implemented accessibility system may act to modify the display of a mobile device, an operating system, or a kiosk. The computer implemented accessibility system may act to modify the display of a program application in addition to a web page. Another new feature is accessibility modules for a website that are configurable by a back-end web page server content management system. One of the configurable aspects is the ability to toggle accessibility modules on and off instantly. Another new feature is the ability to track usage of accessibility modules and user details to help improve accessibility modules and confirm that they are used. Another new feature is a monochrome color filter that modifies the display of a web page and allows for a selection of a singular color. Another new feature is a virtual keyboard that is selectable and is displayed on a web page. Another new feature is language translation in which a user can select a language for the computer implemented accessibility system to translate the contents of the web page. Another new feature is the ability to print modifications into another format such as a paper copy. Another new feature is the ability to remove images and disable animations. Another new feature is a control for the line height, word spacing, and letter spacing of text. Another new feature is the control to modify the alignment of text on a web page. Another new feature is a color picker to modify the color of titles or body text. Another new feature is a graphic representation of accessibility module settings. Another new feature is a logic component to prevent unusable combinations of modules by sequential layering. Another new feature is full keyboard navigation of the accessibility modules themselves. Another new feature is configurability of selectable accessibility icons. Another new feature is a built-in screen reader embedded in code on the client side that can read website content aloud. Another new feature is a server user interface on a web page for configuring the accessibility modules and features. Another new feature is the ability to track the accessibility module's usage by individual users and the ability to kill the accessibility modules. Another new feature is the ability to use tracked usage to optimize the web browsing experience across multiple websites and browser sessions. Another new feature is the ability to update the accessibility modules and features of websites from an independent server. Another new feature is the ability to track and retain individual usage statistics with the goal of using the information to defend against litigation that alleges noncompliance with accessibility standards. Another new feature is the ability to save the preferred settings of accessibility modules so that the settings may be easily transferred or applied to other devices.

The configuration of the accessibility modules will generally be controlled by a host server or web page server while the function of accessibility modules will be conducted by a client device. The functions of most accessibility modules are intended to be completed by client-side instructions such as Javascript. However, it is possible that some embodiments of accessibility modules may incorporate server processing.

Referring toFIG.1, a computer implemented accessibility system100for making a website more accessible to individuals with impairments. The computer implemented accessibility system100may include, among other systems, a host server102, a web page server115, and a client device122. The host server102, web page server115, and client device122may communicate over any network, including but not limited to, the internet or a local area network. The host server102, web page server115, and client device122may each be a computer system capable of storing, receiving, and transmitting data over a network. The computer implemented accessibility system100may be a distributed computer system. In some embodiments, host server102and web page server115may be co-located or may be both on a cloud-based computer system. The computer implemented accessibility system100is configured to create a widget that is displayed on a client device122on web pages that include the accessibility components.

The host server102is a server computer that is capable of communicating over a network with one or more computers to control or transfer the functionality of an accessibility component with the one or more computers. The host server102includes a processor, memory, hard drive input device output device and the like. The host server102includes a host server accessibility component105, which includes a client configuration component110, a function update module112and a host usage tracker114. The client configuration component110is an instruction set capable of generating a web page accessibility component125that incorporates accessibility functions into a web page. The host server102may be used by an individual or entity to distribute web page accessibility components to web page servers115across any network. The host server102may also be used to update a web page accessibility component125and web page server115that may be stored on a web page server115.

The host usage tracker114is configured to tabulate and record data collected by accessibility modules140. In one embodiment, the client usage tracker159transmits data relating to the accessibility modules140to the host usage tracker114. In another embodiment, web page servers115transmit data collected by the web page accessibility component125. Data from the host usage tracker114may be used to improve the accessibility component generated by the client configuration component110. Improved accessibility components may also be pushed to update web page accessibility components125from the function update module112. The improvements can be done manually or through an automated process.

The host server102may be a central hub to deliver web page accessibility components125to web page servers115. The web page server115delivers client accessibility modules140to client devices122. The host server102may be used to distribute a web page accessibility component125to any number of web page servers115, thus saving the time, expense, and liability of web page developers. In one embodiment, the host server102is set up as a service over the Internet, whereby web page hosts may request to have a web page accessibility component125transmitted to their pages. In another embodiment, the host server is set up on the internal network of an entity that is bound by regulations that require accessibility for users or employees with impairments.

In some embodiments, the host server102receives a request from a web page server115for a web page accessibility component125. The client configuration component110generates a web page accessibility component125that is transmitted back to the web page server115.

The client configuration component110generates the web page accessibility component125, which may include accessibility modules and be incorporated into the objects and operations of the original web page component120. In one embodiment, the client configuration component copies a piece of HyperText Markup Language (“HTML”) code. In another embodiment, the client configuration component110reads the web page component120of a web page server115before generating a custom HTML code for that web page component120.

The function update module112updates the HTML code that the client configuration component110generates. A possible motivation for the update might be to improve the accessibility modules140. Another possible motivation could be to keep up with evolving accessibility standards.

In one embodiment, the function update module112can push updates remotely from an independent host server102. The independent host server102does not wait for a request from a web page server115to update the web page accessibility component125. Instead, when the independent host server102updates its client configuration component110, it generates a web page accessibility component125, and pushes the updated web page accessibility component125to the web page server115automatically.

In another embodiment, the host server102independently assesses one or more web page servers115to determine whether the web page server115requires an accessibility component before transferring a web page accessibility component125to the web page server115. The assessment criteria, for determining whether a web page server115requires accessibility modules127, may be any measure that one would reasonably conclude that the web page needs accessibility modules140. In other implementations, the host server102connects to a web page server115and transfers the web page component120to the web page server115if the web page server115has a minimum amount of text. In another implementation of this embodiment, a host server102transfers a web page component120to all web page servers115that are subject to increased government regulation, such as any web page servers115on an internal business network that are accessed by employees.

In another embodiment, the client configuration component110creates custom accessibility modules based on the content of the web page server115. In one embodiment, the host server102connects to a web page server115and generates a color filter167accessibility module based on the original color of the text and background in the web page. The custom color filter algorithm would be optimized to create a color filter167that closely matches the original text and background color of the web site while also creating high contrast between the background and text.

The web page server115is a server computer that is capable of communicating over a network with one or more computers to control or transfer the functionality of an accessibility component with the one or more computers. The web page server115includes a processor, memory, hard drive input device output device and the like. It includes the web page component120and the web page accessibility component, which includes accessibility modules127, a usage tracker130, and an accessibility content manager135.

The web page component120may be coded with programming languages such as, but not limited to, HTML, Javascript, cascading style sheets (“CSS”), or any other language or code or combination thereof that defines the objects and operations of a web page. The web page component120defines the way web pages in a website look to an individual user and how that user interacts with them. The background, placement of buttons, links to other web pages, text, font, cursor, images, and more can all be precisely placed and defined by the web page component120. The web page component120can also define different variations of web pages based on the browser145, device, geographic location, or any variable that distinguishes an individual user from another.

In one embodiment, a web page server115has a Uniform Resource Layer (“URL”) address. A user will specify the URL to a browser145, whereby the user will connect to the web page server115and receive the web page component120. The browser145will then interpret the web page component120to display a web page to the user.

The web page accessibility component125is a set of instructions (e.g., widget) that are added to the web page component120. It has the function of adding an accessibility layer to the web page component120. In some embodiments, the web page component120executes all of its original instructions before the web page accessibility component125executes additional instructions. The web page accessibility component125includes an accessibility module127, a usage tracker130and an accessibility content manager135. It also has a kill switch that can close all the processes or functionality associated with the web page accessibility component125.

In one embodiment, the web page accessibility component125is a piece of HTML code that is embedded before the end of the body tags of the web page component120. The body tag defines the main content of a web page that will be visible to the individual user. Thus, by placing the web page accessibility component125before the end of the body tag, the web page accessibility component125acts as a final layer of instruction that modifies the original content of the web page.

The accessibility modules127are code within the web page accessibility component125that defines how a web page is modified to make it more operable, distinguishable, navigable, and understandable to the user. For example, the increase font185accessibility module acts to increase the font of text in a web page to make it more distinguishable regardless of what the original text size of the web page is.

The usage tracker130is software on the web page accessibility component125that is capable of recording interaction of a client with a web page. The usage tracker130tabulates each time an accessibility module is used. It tracks the module used along with the time and URL address of the client user. The usage tracker130may be used to show which accessibility modules140get the most use. It may also be used to defend a web page owner from a litigation claim that the web page did not conform to regulatory standards when an individual used it. In one embodiment, the client usage tracker159on the client device122logs data of accessibility module140use and transfers, to the web page server115, the data for every time the accessibility module140is used. The data of each individual execution of an accessibility module140is linked with the time, date, and URL address of the client user.

The accessibility content manager135is a user interface that controls content of the accessibility module from the web page server115. Content and functions of the accessibility modules127may be manipulated by the accessibility content manager135. These include placement of the accessibility icon, selecting the icon image, and selecting which accessibility modules140to incorporate into the web page.

In one embodiment, variables in the accessibility content manager135are optimized to maximize use by analyzing the usage tracker130. In one implementation of this embodiment, placement of the icon position410and icon placement415variables are incrementally adjusted until the icon is in the ideal location where it is clicked by the highest percentage of client users. The icon position410and icon placement415variables may be adjusted manually or through an automated algorithm. In another implementation of this embodiment, settings of color filters167are incrementally adjusted based on the number of times color filter167accessibility modules are used. In another implementation of this embodiment, individual accessibility modules140are toggled on and off to maximize use of the other accessibility modules140.

The client device122is any computer system with a processor and memory that sends and receives data over a network. It includes a browser145, a visual display155, speakers157, a means of input158, a client usage tracker159, and accessibility modules140. The client device122may be used by any individual including those who may have a visual, audio, or mobility impairment. Accessibility modules140are executed on the client device.

The browser145is software on the client device122that directs the client device to connect to the URL of a web page server, receives the instructions that define a web page, and interprets those instructions to create the web page on the display155and speakers157of the client device. The browser145may connect to a URL automatically or a user may manually enter it.

The display155is any screen, projection, or other means of rendering patterns, images, and text commonly seen on web pages. Common displays are phone screens, tablet screens, and computer monitor screens. The browser145interprets web page component120instructions to render an image of that web page. A website can be designed to render differently based on the type of display155the client is using.

The speakers157play audio on the client device. The listen175accessibility module, for example, uses speakers to read the text from a web page. Input158on a client device is any interaction with a website that a user brings into effect. Input158devices such as keyboards, mice, touch screens, game controllers, motion sensors, and microphones are all used to interact with websites.

The client usage tracker159is a module that tabulates and records usage of the accessibility modules. In one embodiment, the usage tracker records every time an accessibility module is selected, also recording the time and the URL address of the client device122. In another embodiment, the client usage tracker159also records client device122configuration data such as IP address, browser145type and settings, operating system accessibility settings such as the read aloud voice, and any other identifying or profiling data. In another embodiment, preferred accessibility settings that were recorded by the client usage tracker159may be saved in an easy to transfer file format such as JSON or CSV. The saved file may be exported to a web page server115or imported into other client devices122. The client usage tracker159is also configured to transmit all data that it collects to a server. In one embodiment, the client usage tracker transmits data to the usage tracker130on the web page server115. Data collected by the web page server115may be analyzed to find the optimum accessibility settings for accessibility modules140, web page components120, browsers145, operating systems, and client devices122. In another embodiment, the client usage tracker159transmits data to a server that is not the web page server115. In one embodiment, data is transmitted to the host usage tracker114. The client usage tracker159may be used to improve the experience of the client user by remembering the accessibility modules140that a client selects and automatically selecting those same modules for that client's future use.

The client accessibility modules140are a set of instructions transmitted from the web page accessibility component125. The accessibility modules140, when executed, modify a website's visual and audio output to be more operable, distinguishable, navigable, and understandable. The client accessibility modules140also help a website conform to W3C Content Accessibility Guidelines (“WCAG”), which is an international standard for web content accessibility. WCAG 2.0 has four principles that the information and interface on a website should be. The four principles are perceivable, operable, understandable and robust.

The client accessibility component140includes, but is not limited to the following types of accessibility modules: disable animations162, virtual keyboard163, translation164, print mode165, remove images166, color filter167, adjust line height168, reader view169, adjust word spacing170, tooltip visible171, adjust letter spacing172, W3C Initiative173, change alignment, listen175, change title color176, reset177, change text color178, cursor filter179, keyboard navigation181, highlight titles183, increase fonts185, bold fonts187, decrease fonts189, highlight links191, increase zoom193, decrease zoom195, accessibility197, operator198, and reset font199.

The disable animations162accessibility module may control the animations of a web page to help reduce distractions to a user. Fast moving graphics, however aesthetically pleasing, may trigger undesirable stimuli for the viewer. The disable animations162accessibility module may be implemented as a toggle that, when selected by a user, deactivates or activates all animations on a web page. A toggle that deactivates the animations allows the user to focus on the text content of a web page. A user may turn animations back on using the same toggle to view the animations.

The virtual keyboard163accessibility module displays a selectable virtual keyboard on a web page. The virtual keyboard163may enable typing functionality for users that do not have a keyboard available or do not have a keyboard that is accessible due to a disability. When selected, the keys of the virtual keyboard function the same as the keys of a physical keyboard. When a physical keyboard is used, the virtual keyboard163may highlight the analogous keys of the virtual keyboard that were pressed. The keys of the virtual keyboard may be selected by various inputs such as mouse click or touch.

The translation164accessibility module allows a user to select a language that the user prefers. The language translation may enable users that do not understand a default language of displayed text on a web page to change the text to a translated version of the text. In various embodiments, the translation164accessibility module, when activated, displays a list of languages that are selectable by the user. The web page may display text in the language that is selected by the user. In an exemplary embodiment, the text of a web page is translated into multiple languages and stored in the web page. The preferred language translation may be displayed by the translation164accessibility module.

The print mode165accessibility module allows a user to print the reader view of a web page. Printing a web page gives users greater flexibility to display the web page in a format that the user prefers. For example, a user may print a web page onto paper, which may be the preferable reading format for users. In an exemplary embodiment, all accessibility modules, which have been activated by the user, are also printed. For example, a reader may use print mode165to print a web page with increased letter spacing by first activating the adjust letter spacing172accessibility module and then activating the print mode165accessibility module.

The remove images166accessibility module modifies the output of a web page to display a blank space in place of images. In an exemplary embodiment, remove images166presents an experience on a web page that is devoid of any graphical image files, allowing the viewer to focus on the text of the web page.

The color filter167changes the color scheme of a web page. The color filter167can render a web page to be more perceivable to users with visual impairments, thus conforming to principle 1, “perceivable” of the WCAG 2.0 guidelines. Different types of color filters may work better than others for certain types of visual impairments. For instance, a user with color blindness may perceive a web page more clearly with one type of color filter167than a user with blurred vision.

As shown on the buttons inFIG.6, the preferred embodiment has the following types of color filters167: monochrome, sepia, high contrast, black and yellow (WCAG Contrast), gray scale, and invert. The monochrome color filter modifies the web page to render a monochromatic color scheme, which will display the graphics on a page in one color hue. The sepia color filter executes a reddish-brown color scheme, which may help users with colorblindness better perceive a web page. The high contrast color filter toggles a high contrast color scheme to make a web page more distinguishable. The black & yellow (WCAG Contrast) color filter executes techniques to satisfy various guidelines under the WCAG 2.0—(1) Perceivable principle; specifically, guidelines: 1.4.1 Use of Color, 1.4.3 Contrast (Minimum), and 1.4.6 Contrast (Enhanced). This filter may help individuals with visual impairment and/or color-blindness. The gray scale color filter toggles the web page to a grayscale color scheme to make the page more distinguishable. The invert color filter inverts colors on the web page, making it easier for people with sensitivity to brightness and more distinguishable for people with color-blindness or low vision.

The adjust line height168accessibility module adjusts the spacing between lines of text for content on a web page. Readability may be enhanced for users who can adjust line spacing. In an exemplary embodiment, the adjust line height168accessibility module may be activated by the user clicking on buttons that increase line height and decrease line height. In an exemplary embodiment, the adjust line height168accessibility module may be split into two buttons. One button, when activated, increases the line height. The other button, when activated, decreases the line height.

The reader view169accessibility module parses the web page content to make it more readable in a format that displays images with captions and the pertinent body text in one easy to read view.

The adjust word spacing170accessibility module adjusts the spacing between words of content on a web page. In an exemplary embodiment, the adjust word spacing170accessibility module may be activated by the user clicking buttons that increase and decrease the spacing between words. Also, in an exemplary embodiment the spacing between words may be adjusted by toggling a slider that represents the relative spacing between words.

The tooltip visible171accessibility module displays all the tool tips or messages that appear when a cursor is positioned over an icon, image, hyperlink or other element on a website. It helps satisfy several guidelines under the WCAG 2.0—(1) Perceivable, (2) Operable, (3) Understandable, and (4) Robust principles and their underlying criteria. The tooltip visible171accessibility module may be combined with other functions using the operator198module such that accessibility modules140operate only on tooltips.

The adjust letter spacing172accessibility module adjusts the spacing between letters of text on a web page. Users may increase readability by adjusting the spacing between letters to a spacing with which they are most comfortable. In an exemplary embodiment, the adjust letter spacing172accessibility module may be implemented as an increase letter spacing button and a decrease letter spacing button that can be activated by a user.

The W3C Initiative173accessibility module executes an instruction to take a user to the World Wide Web Consortium's (W3C) Website content Accessibility Guidelines and review the success criteria for WCAG 2.0.

The change alignment174accessibility module allows a user to set all of the content on a web page to an alignment of their preference. Users may be more comfortable reading with a specific alignment. Allowing the user to set the alignment themselves may thus improve readability. In an exemplary embodiment, a user may set the alignment of content via buttons that represent different alignments. For example, a user may have a selection of four buttons representing the four alignment options: align center, align left, align right, and align justify.

The listen175accessibility module executes an instruction to read the web page aloud via the speaker of the device so that visually impaired individuals can decipher the content on the web page. Executing the listen module175again stops the instruction to read aloud. One implementation of the listen175accessibility module is the point and click audio translation of text on a page. In this implementation, text boxes are translated into audio speech and read aloud when they are selected. Individual text boxes may be identified by their HTML element labels. The full-page implementation automatically translates all the text on a page to be read aloud. Alternatively, it reads the individual text box that a cursor hovers over. The tab-through keyboard control gives the client user the ability to use the tab button to cycle through individual text boxes on the web page to have them read aloud. The escape button may be used to turn the listen accessibility module off and on.

The change title color176accessibility module allows a user to change the color of titles on a web page. Control over the color of titles on a web page may enhance the readability of the web page for users with sight disabilities. In an exemplary embodiment, selecting a title color button may display a color picker featuring 36 different selectable colors that allows a user to change the color of all title tags on a web page. The ability to choose a specific color allows users to quickly select a color with which they are most comfortable.

The reset177accessibility module reverts a web page back to its original state before any accessibility modules140were executed. In one embodiment where more than one accessibility module is active, the reset177module merely resets the changes made by the accessibility module that was executed last. In another embodiment where accessibility modules140operate on other accessibility modules140through the operator198module, the reset177module may be configured to reset only the accessibility modules140that are operating on other accessibility modules140.

The change text color178accessibility module allows the user to change the color of all body text on a web page. Control over the color of text on a web page may enhance the readability of the web page for users with sight disabilities. In an exemplary embodiment, a change color button displays a color picker featuring 36 different selectable colors that, when selected, change the color of all body text on web page to the selected color.

The cursor filter179accessibility module turns on a high contrast, magnified mouse, colored white or black that enables users with visual impairments to more easily identify the mouse cursor on a screen. The cursor filter179accessibility module satisfies WCAG guidelines 1.4 Distinguishable, 2.4 Navigable, and other interoperability requirements. The cursor filter179may be used in combination with the keyboard navigation181accessibility module to help users find a cursor that is lost on a screen.

The keyboard navigation181accessibility module displays the key combinations that execute accessibility modules via keystroke input rather than by selecting a button with a cursor. This module satisfies WCAG 2.0 Principle 2; specifically, guideline 2.1, which calls for all functionality of a website to be available from a keyboard. The highlight titles183accessibility module toggles a highlight color for all text tagged as a title on a web page. This module makes a web page more navigable and distinguishable. The increase fonts185accessibility module, when executed, increases the font size on a web page to up to 200% its original size without loss of content or functionality. Likewise, the decrease fonts189accessibility module, when executed, reduces the font size down to half its original size without loss of content or functionality. The increase fonts and decrease fonts accessibility modules satisfy WCAG 2.0 Principle (1) Perceivable; specifically, guideline 1.4.4 resize text and additional rules.

The bold fonts187accessibility module executes an instruction to boldface all fonts on the web page. This accessibility module meets WCAG 2.0 guideline 1.4.6 Contrast (Enhanced). The Highlight Links191accessibility module toggles a highlight color for all links on a web page. This accessibility module satisfies WCAG 2.0 guidelines: 2.4.3 Focus Order, 2.4.4 Link Purpose, 2.4.9 Link Purpose, and 3.1 Readable. It makes the website more navigable and distinguishable. The increase zoom193accessibility module magnifies a web page for easier readability. Likewise, the decrease zoom195accessibility module reduces magnification of the web page.

The accessibility197accessibility module executes an instruction to direct the browser to the URL of a dedicated accessibility web page of the website. The web page URL can be set in the accessibility content manager135. The accessibility197module satisfies WCAG guideline 3.3.5 for context-sensitive help.

The operator198accessibility module modifies the execution instructions for an accessibility module to operate on the execution of another accessibility module140rather than on the entire web page. In one example of the operator198module's execution, the bold fonts187accessibility module may be modified to operate on the highlight titles183accessibility module to toggle boldface fonts only on web page text that is tagged as a title. In another example of use, the listen175accessibility module may be modified to operate on the tooltip visible171accessibility module, whereby only the tooltips, also shown inFIG.7, are read aloud.

The reset font199accessibility module returns the font back to the original size and style. In one embodiment the reset font199accessibility module returns the fonts of the entire web page back to the original font. In other embodiments, where one accessibility module is operating on another module to modify its font, the reset font199module may be used to only return the font of the module that was operated upon.

Display filters are sequentially layered with logic to prevent multiple display filters from rendering an unusable end result. For example, only one color filter167accessibility module may be active at one time because multiple color filters167may interfere with one another to render a display that is less accessible or unusable. When any color filter167is executed, other active color filters are toggled off. Similarly, cursor filters179also toggle off any other cursor filters that are on when they are executed. The sequential layering logic allows filters that do not interfere with one another to continue executing while filters that do interfere are turned off. Sequential logic layers may be independently applied to modifications made by the operator198accessibility module. For example, the sequential logic layer may prevent the operator198module from modifying another accessibility module with more than one color filter167.

FIG.2Aillustrates a method200that may be implemented by the system inFIG.1. In various embodiments, the computer implemented accessibility system100may allow a website owner to add additional functionality to their web pages. Additional functionality may include making the web page more accessible to individuals with visual, audio, or mobile impairments by including a web page accessibility component125on the web page server115.

At step205, a host server102may receive a request to include accessibility code into a web page hosted by web page server115. In response to the request from step205, the host server102may generate the accessibility code. The request can be through any form of communication. In the preferred embodiment, the request is transmitted over the internet.

At step210, the accessibility code is generated. The accessibility code can be a piece of HTML code. In one embodiment, the HTML code is copied and transmitted to a web page server. In another embodiment, a unique HTML code is generated based on the needs of the website for which the request was made. Although HTML code is used in the envisioned embodiment, there are possible embodiments that do not use HTML code. The generated HTML code has the instructions for accessibility modules140that make web sites more accessible to individuals with impairments. In one embodiment, the HTML code includes a content management system, also shown inFIGS.3-4. At step215, the accessibility code is embedded onto existing web page code. In one embodiment, the accessibility code is embedded before the body tags of the HTML code that define the website.

FIG.2Billustrates a method218that may be implemented by the system inFIG.1for updating the accessibility code on a web page server. It may be periodically necessary to update the accessibility code for a variety of reasons including, a change in WCAG guidelines, a change in web standards such as HTML, and hardware changes. At step220, accessibility code is updated. The update can be done manually by editing the code or through an automated system.

At step225, the updated accessibility code is generated for the web page. The accessibility code can be a piece of HTML code. In one embodiment, the same code is copied for every website. In another embodiment, different code is generated based on the website' s instruction set. At step230, the updated accessibility code is pushed onto the existing website's code. The update replaces the accessibility code on the website. In one embodiment, the update is performed automatically by an independent server. In another embodiment, the update is done manually by transmitting the updated code to a web page server115and inserting the code to replace the web page accessibility component125.

Referring toFIG.2C, a method232illustrates that at step235, a host server102receives a request for an accessibility component from a web page server115. The accessibility component is any code that contains the instructions for accessibility modules140. The request can be through any form of communication including TCP-IP and email. The host server102may evaluate the request to accept or reject it. In some embodiments, the request includes a subscription and payment for an accessibility service.

At step240, the host server102receives a web page component120from a web page server115. It is intended that the host server102will generate a web page accessibility component125for the web page component120. In some embodiments, the host server102may generate a custom component based on the needs of the web page server115. At step245, the host server102transmits an accessibility component to the web page server115. The accessibility component is any code that contains the instructions for accessibility modules140.

FIG.2Dis an illustration of a method250that may be implemented by the system inFIG.1to optimize the functionality of the accessibility component through iterative steps. At step255, frequency data from the usage tracker130is analyzed to identify the accessibility module that was selected the least over a period of time. “Selected the least” means that a module was getting lower use than other modules and may be measured in any way including: measuring for the module that was clicked the least number of times, activated for the least amount of time, executed by the least number of unique individuals, any combination herein, or any other measure of the use for a module.

At step260, the module that was identified as least selected is moved to a second screen display. The second screen display includes, but is not limited to, another web page or any location away from the first screen. At step265, a second frequency data is collected and analyzed to identify a second module that is least selected. The second frequency data is collected while the first module that was selected the least has been removed to the second display screen. The second frequency data can also be evaluated to determine whether the accessibility component is better, worse, neutral, or insignificantly better than it was before the first module was removed.

At step270, the second module that is least selected is moved to the second display screen. At this point, the first module that was least selected may be moved back. Alternatively, the process may be repeated to identify a third module that is least selected. This process may be repeated any number of times with the goal of finding the ideal combination of modules, placement of modules, or any other accessibility module setting.

In one embodiment, the web browsing experience is tuned or optimized based on data collected by accessibility modules140. Accessibility module frequency data from client users may be collected by the client usage tracker159and used to modify the client's browser145settings to suit the client user's preferences. In another implementation, accessibility module frequency data from client users is collected by the usage tracker130of web page server115owners to tune or optimize the settings of a website or multiple websites. The tuning or optimization may be done through any method of data analysis including, but not limited to, machine learning algorithms.

Referring toFIGS.3-4the content management system functions to manipulate the web page accessibility component from the web page server.FIG.3shows a diagram of the content management system and the various features that can be managed.FIG.4shows a screen shot of the user interface of the content management system fromFIG.3. As shown inFIG.3, the content management system can modify the accessibility web page URL305address, the accessibility module toggles310, the icon Position320, the icon image325, and the tray position330. Nothing inFIGS.3-4is intended to limit components and settings that the content management system300can modify.

The Accessibility Web page URL305is for the dedicated accessibility page on the web page server where a user is directed when they execute the accessibility197accessibility module. Accessibility modules toggle310lists every accessibility module and places an on/off toggle next to it. Thus, the content management system may control which accessibility modules are available to the user on the client device. As the number of accessibility modules140grows, it becomes more necessary to pick some over others to implement on a web page. The accessibility modules toggle310gives web page server's115the ability to select a subset of accessibility modules to make available on a web page.

The content management system has control over icon position320. And because web pages have different content, the placement of the icon that opens functionality for the accessibility modules can be important. It is suggested that the icon be placed away from images and text that make it difficult for the visually impaired to perceive the icon. The content management system can place the icon, shown inFIG.5, at any position on the web page. Similarly, the icon image325can also be manipulated by the content management system to make it easier for users of client devices to perceive it.

The content management system also has control over the tray position330. The tray is a box that opens when the icon is selected. Within the box are buttons that represent the accessibility modules140. Placement of the tray can be set in the content management system.

The content management system may have a usage tracker counter335that tabulates the usage of each accessibility module140. In one embodiment, the usage tracker counter335displays the number of times an accessibility module is selected next to the accessibility module toggle310. This embodiment gives the users of web page servers115the usage information to toggle off accessibility modules that have little or no use.

A screen shot of the content management system user interface shown inFIG.4shows the accessibility web page URL405, icon position410, icon placement415, tray position420, widget icon selection425, and the user interface of the WCAG feature selections430-456. In the embodiment shown inFIG.4, icon position on the screen is controlled by both the icon position410, and icon placement415variables.

The keyboard navigation button430toggles the ability for a client user to execute one of the modules in the accessibility modules140to display the individual key combinations that execute other accessibility modules via keystroke input rather than by clicking a button. The high contrast button432toggles the high contrast color filter167ability for a client user to execute a high contrast color scheme to make a web page more distinguishable. The invert button434toggles another color filter167ability for a client user to execute a filter to invert the colors on a page. The tooltip visible button436toggles the ability for a client user to execute a tooltip visible171module to display all tooltips that usually only appear when a cursor is over them. The decrease fonts button438toggles the ability for a client user to execute the decrease fonts module189on the web page. The decrease zoom440button toggles the ability for a client user to execute the decrease zoom195module to reduce the magnification and shrink the web page. The reader view button442toggles the ability for a client user to execute the reader view169module that parses the page content to make it more readable in a format that displays images with captions and the pertinent body text in one easy to read view. The listen button444toggles the ability for a client user to execute the listen module175that reads an audio translation of text on the page. The sepia button446toggles the ability for a client user to execute the color filter167to create a reddish-brown color overlay for the web page. The grayscale button448toggles the ability for a client user to execute the grayscale color filter167on the web page. The highlight links button450toggles the ability for a client user to execute the highlight links191filter that highlights the color for links on a web page. The increase fonts button452toggles the ability for a client user to execute the increase fonts185module for all text on a web page. The increase zoom button454toggles the ability for a client user to execute the increase zoom193module that magnifies the entire web page. The black cursor button456toggles the ability for a client user to execute the cursor filter179module that makes the cursor larger with a high contrast black color. The accessibility button toggles the ability for a client user to execute the accessibility197module that directs them to a dedicated accessibility web page on the website. The save button460executes a function to save the accessibility web page URL405, icon position410, icon placement415, tray position420, widget icon selection425, and the WCAG feature selections430-456on the accessibility content manager page400. The function executed by the save button460may create a file in plain text format such as JSON or CSV with saved accessibility that is easily shared.

Referring toFIG.5, a screenshot of a web page500with the accessibility icon505. In the preferred embodiment, the icon is an image that denotes accessibility. The icon is placed away from any images or text that may distract the user from perceiving it. When the icon is clicked, as shown inFIG.6, it opens the tray of accessibility modules. Clicking the icon again, closes the tray.

Referring toFIG.6,FIG.6illustrates a screen shot of a web page600with a tray that is a rectangular box where buttons that execute accessibility modules140are placed. The icon606, when clicked, functions to close the tray. The Keyboard Nav button606executes the keyboard navigation181accessibility module to display the keyboard combinations, that when pressed, execute accessibility modules140. The Mono Chrome button608, Sepia button610, High Contrast button614, WCAG Contrast button618, Gray Scale button620, and Invert button624are all various color filter167accessibility modules that modify the color scheme of the web page. The white cursor626and Black Cursor630are variations of the cursor filter179accessibility module. The Hotel Accessibility button642executes the accessibility197module. The Reset Font button612executes the reset font199accessibility module. The Zoom Increase button616executes the increase zoom193accessibility module. The zoom decrease button622executes the decrease zoom195accessibility module. The Highlight Titles button628executes the highlight titles183accessibility module. The Reader Viewer button634executes the reader view169accessibility module. The Highlight Links button632executes the highlight links191accessibility module. The W3C Initiative button638executes the W3C initiative173accessibility module. The Tooltip Visible button636executes the tooltip visible171accessibility module to display tooltips that would normally require a cursor to hover over them. The Bold Fonts button640executes the bold fonts187accessibility module. The Listen button643executes the listen module175accessibility module to read text aloud. The Reset Button644executes the reset177accessibility module to revert the web page back to the original state. The Increase Fonts button646executes the increase fonts185accessibility module to increase the font size of all text. The Decrease Fonts button648executes the decrease fonts189accessibility module to lower the font size of all text.

Referring toFIG.7, a screenshot700of the tooltip visible171accessibility module as it is executed. As the Tooltip Visible button705is selected, tooltips710display on the screen, which would normally require the placement of the cursor over them to display. This module has the advantage of allowing the viewer of a web page to quickly perceive and read all tooltips without having to guess at where they are. Selecting the Tooltip Visible button705again returns the page back to normal tooltip settings that require a hovering cursor to display.

Referring toFIG.8,FIG.8a screenshot800of the highlight titles183accessibility module as it is executed. As the Highlight Titles button805is selected, all text tagged as a title810is highlighted with a different color background on the screen. In one embodiment, the Highlight Titles button805may be used in combination with the operator198accessibility module and the listen175accessibility module to instruct the page to read all titles aloud. In another embodiment, the Highlight Titles button may also be used with the operator198accessibility module and the color filters module167to highlight titles in various high contrast colors.

Referring toFIG.9,FIG.9is a screenshot900of the highlight links191accessibility module as it is being executed. As the Highlight Links button905is selected, all text910that links the user to another URL address is colorized with a different color background on the screen. This button may be used in combination with the operator198accessibility module and the listen175accessibility module to instruct the page to read all links aloud. This button may also be used in combination with the operator198accessibility module and color filter modules167to highlight links in various high contrast colors.

Referring toFIG.10,FIG.10is a screenshot1000of the keyboard navigation181accessibility module as it is executed. As the Keyboard Nav button1005is selected, key combinations that execute accessibility modules are displayed1010above their respective buttons. This button1005may be used in combination with the operator198accessibility module and the listen175accessibility module to read the keyboard combinations aloud. This button1005may also be used in combination with the operator198accessibility module and the color filter modules167to color the keyboard combinations in high contrast colors that are easy to read.

Referring toFIG.11,FIG.11is a screenshot1100of the cursor filter179accessibility module as it is executed. As the White Cursor button1105is selected, the cursor1110is larger with high contrast, making the cursor easier to see and track. This function may be used in combination with the keyboard navigation181module to type a key combination to find a cursor that is lost on the display. In one embodiment, a line is drawn from the cursor to the closest executable selection on the screen showing the client where the executable selection is. In another implementation of this embodiment, the closest executable selection can be executed by the user, allowing for users with low mobility to select objects on a screen without moving the cursor directly over them. In another implementation of this embodiment, the line can be cycled to the next closest selections to the cursor by using keyboard or other inputs.

Referring toFIG.12,FIG.12is a screenshot1200of the color filter167accessibility module as it is executed. As the WCAG contrast button1205is selected, the display color is filtered and contrast adjusted to make a web page1210more perceivable to individuals with visual impairment.

The host server102, web page server115, and client device122are forms of computing devices1302with hardware components as shown block diagram1300inFIG.13. The computing devices1302have one or more processors1305, main memory1310, storage devices1315, and network components1320. The host server102, web page server115, and client device122may all be separate computing devices1302, a single computing device1302, or computing devices1302that share one or more components.

Each computing device1302has one or more processors1305, main memory1310, storage devices1315, and one or more network components1320. The processor1305is an electronic circuit that performs calculations and basic instructions in a computing device1302. Common examples of processors include, but are not limited to, central processing units (CPU), graphics processing units (GPU), field programmable gate arrays (FPGA), and complex programmable logic devices (CPLD).

The processor1305has immediate and direct access to main memory1310. Main memory1310is often called random access memory. A processor only has access to main memory1310. Programs and applications are copied to the main memory1310before they interact with the processor1305. Many forms of main memory1310only store memory while the computing device1302is powered.

Computing devices1302may have storage1315, including, but not limited to hard disk drives, solid state drives, flash memory, floppy disk drives, and compact disks. A processor1305does not have direct access to storage1315, however storage devices1315tend to be cheaper and have more capacity than an equivalent amount of main memory1310. Web page components120and accessibility modules127will typically be kept on storage devices1315until they are needed, at which point, they will be transmitted into main memory1310.

The computing devices1302have one or more network components1320that allow them to communicate with other computing devices1302. A person skilled in the art will understand how to implement a network component1320on a computing device1302. In one embodiment, the host server102, web page server115and client device122all communicate through a TCP/IP network component1320.

Referring toFIG.14, an image1400of a graphical representation of accessibility module settings. Accessibility modules140may be configured to display selectable settings, giving the user fine control over the execution of the accessibility module. In one embodiment, shown inFIG.14, a graphical representation of selectable settings is displayed, showing the user the display modifications that the accessibility module could bring into effect. An example of a graphical representation of a selectable setting for the Font Increase button1405is shown inFIG.14. When the Font Increase button1405is selected, a display window shows text in various font sizes1410that are selectable and represent the font sizes that could be displayed on the web page by the increase fonts185accessibility module. To ease use, the currently selected setting is indicated1415in the graphical representation. A smaller abstract representation1420of the current setting may be displayed on the button.

Another implementation of a graphical representation of a selectable setting for the color filter167accessibility module is a color selector, such as a color wheel, that displays every combination of red, green, and blue colors in a compact window. For example, when a graphical representation of a color selector is applied to the Mono Chrome button608, a user may select the preferred color on the color selector to display the web page in the hue of the selected color. This gives users who perceive colors differently an improved ability to fine tune the color scheme of a web page to their preference. Other modules may make use of a color selector, such as the tooltip visible171, cursor filter179, highlight titles183, and highlight links191accessibility modules.

This description of the embodiments is not intended to be limiting, but is instead meant to illustrate the principles and concepts herein. The embodiments herein may be implemented without limitation or confinement to this disclosure. Rather, the many embodiments are intended to guide a person skilled in the art such that they may combine embodiments or derive additional embodiments consistent with this disclosure.

Referring toFIG.15, an image of a listen button1500, which executes a listen175accessibility module when selected by the client user. When selected by the client user, the listen button1505executes the listen175accessibility module, which instructs the web page to be read aloud via the speaker157of the client device122. Selecting the listen button1505again stops the listen module175from reading aloud.

Referring toFIG.16, an image of the graphical representation of the selectable setting for a color selector1600of a Mono Chrome button1605as it is displayed on a client display. In the embodiment of a color selector shown inFIG.16, a color wheel displays combinations of red, green and blue in a selectable circle. On the outside of the circle are the three primary colors: red1610, green1615, and blue1620, placed equidistantly from each other. White1625is in the middle. The outside of the color wheel displays the graduation of primary colors as they combine into one another. At the location in between the primary colors on the outside of the circle are combinations of primary colors. For example, yellow1630, is the combination of red1610and green1615. Going from the outside of the circle to the center, all colors are gradually increased until the maximum level of red1610, green1615, and blue1620is reached to produce white1625. Any color on the wheel can be selected. Once selected, a target1635indicates the location of the color selected and a color square1640displays the picked color. The picked color may be further adjusted by changing the brightness setting1645, which lightens and darkens the selected color1635while maintaining the same color hue. Once the client user selects the preferred color, the “OK” button1650may be selected to execute the monochrome color filter167accessibility module for the selected color. Selecting the “Cancel” button1655would close the color selector. A multitude of the client user's preferred colors may be saved by selecting the save color buttons1660.

Referring toFIG.17,FIG.17illustrates a screen shot of a web page1700with a rectangular tray1705placed on the left side of the page. The tray position330may be set in the content management system300by selected left for the tray position420on the content management user interface screen. The best location for the tray1705may be different for each web page based on aesthetics and accessibility.

Referring toFIG.18,FIG.18illustrates a screen shot of a web page1800with a rectangular tray1805placed on the right side of the page. A tray position330on the right side of the page may be most useful for web pages where the content focuses on the left side of the page.

Referring toFIG.19A,FIG.19Ais a screen shot1900illustrating a decrease line height button1905, which implements an adjust line height168accessibility module. In an exemplary embodiment, the decrease line height button1905provides the ability to decrease the line spacing between text up to five points in order to provide enhanced readability of all content on the web page.

As shown inFIG.19A, the decrease line height button1905is highlighted and has been selected. In an exemplary embodiment that is shown inFIG.19A, the decrease line height button1905may be selected multiple times to further decrease the spacing between lines with each selection. The two dashes in the decrease line height button1905indicate that the decrease line height button1905has been selected twice, thus decreasing the spacing between lines by two points. The spacing between lines of text1910has been decreased by two points, as directed by the user.

Referring toFIG.19B,FIG.19Bis a screen shot1950illustrating an increase line height button1955, which implements an adjust line height168accessibility module. In the exemplary embodiment that is shown inFIG.19B, the adjust line height168accessibility module is implanted as two buttons to give the user control over the spacing between lines on the web page in the screen shot1950. The decrease line height button1905and increase line height button1955allow the user to precisely adjust and experiment with line spacing to achieve a preferred line spacing for enhanced readability.

As shown by the highlighting of the increase line height button1955in the screen shot1950, the increase line height button1955has been activated by the user to increase the spacing between lines of text. The five dashes within the increase line height button1955indicate that the user has selected the increase line height button1955five times to increase the spacing between lines of text1960by five points. As such the text1960of the screen shot1950has noticeably greater spacing between lines when the increase line height button1955has been activated than when the text1910of the screen shot1900where the decrease line height button1905has been activated.

Referring toFIG.20A,FIG.20Ais a screen shot2000illustrating a decrease word spacing button2005, which implements an adjust word spacing170accessibility module. In the implementation of the adjust word spacing170accessibility module shown inFIG.20A, the adjust word spacing170accessibility module is split into two buttons, an increase word spacing button2055and a decrease word spacing button2005. In an exemplary embodiment, activating the decrease word spacing button2005incrementally decreases the spacing between whole words of text on the web page.

As shown by the highlighting of the decrease word spacing button2005in the screen shot2000, a user has activated the decrease word spacing button2005. The two dashes in the decrease word spacing button2005indicate that it was selected twice by the user to decrease the spacing between words two consecutive times. And as shown by the text2010in the screen shot2000, the spacing between whole words has been decreased.

Referring toFIG.20B,FIG.20Bis a screen shot2050illustrating an increase word spacing button2055, which implements an adjust word spacing170accessibility module. The increase word spacing button2055, like the decrease word spacing button2005, implements the adjust word spacing170accessibility module. In an exemplary embodiment, selecting the increase word spacing button2055incrementally increases the spacing between whole words of text2060on a web page.

As indicated by the highlighting of the increase word spacing button2055in the screen shot2050, the increase word spacing button2055has been selected by a user. The five dashes in the increase word spacing button2055indicate that the increase word spacing button2055has been selected five times, which incrementally increases the spacing between words five times. The increased spacing between whole words may increase the readability for users with sight disabilities. As shown in the screen shot2050ofFIG.20B, the spacing between whole words of the text2060is larger than the spacing between whole words of the text2010in the screen shot2000ofFIG.20A.

Referring toFIG.21A,FIG.21Ais a screen shot2100illustrating a decrease letter spacing button2105, which implements an adjust letter spacing172accessibility module. The ability to adjust the spacing of letters in the text of a web page to a preferred letter spacing improves readability for users with disabilities relating to sight and focus. In the exemplary embodiment shown in the screen shot2100, the adjust letter spacing172accessibility module is implemented as two buttons, a decrease letter spacing button2105and an increase letter spacing button2155. The decrease letter spacing button2105, when activated, incrementally decreases the spacing between letters of text2110.

As indicated by the highlighting on the decrease letter spacing button2105in the screen shot2100, the decrease letter spacing button2105has been activated by a user. The five dashes on the highlighted decrease letter spacing button2105indicate that the user has activated the decrease letter spacing button2105five times to decrease the space in between letters five separate times. The spaces between the letters of text2110have been thus decreased.

Referring toFIG.21B,FIG.21Bis a screen shot2150illustrating an increase letter spacing button2155, which implements the adjust letter spacing172accessibility module to incrementally increase the spacing between letters of text2160on a web page. Like the decrease letter spacing button2105, the increase letter spacing button2155implements the adjust letter spacing172accessibility module to change the spacing of letters of text2160on a web page by a set amount. When the decrease letter spacing button2105and increase letter spacing button2155are used together, a user may experiment to discover a letter spacing of text2160that the user finds most preferable.

As shown by the highlighting of the increase letter spacing button2155in the screen shot2150, the increase letter spacing button2155has been activated by the user. The five dashes on the increase letter spacing button2155indicate that it has been activated five times by a user to incrementally increase the spacing between letters of the text2160five separate times. The spacing between the letters of text2160in the screen shot2150ofFIG.21Bis thus greater than the spacing between the letters of text2110in the screen shot2100shown inFIG.21A.

Referring toFIG.22A,FIG.22Ais a screen shot2200that illustrates an implementation of the change alignment174accessibility module. The change alignment174accessibility module may change the alignment of the text2210on a web page to various alignments such as “align left”, “align right”, “align center”, and “align justify”. In an exemplary embodiment, the functions of the change alignment174accessibility module may be split between multiple buttons, each of which activates a different alignment of text. The align center button2205changes the alignment of text2210to an “align center” alignment.

As indicated by the highlighting on the align center button2205in the screen shot2200, the align center button2205has been activated by the user. The align center button2205may be configured to implement the change alignment174accessibility module to cancel the previous text alignment and activate a center alignment of text2210on the web page. As shown in the screen shot2200, the text2210has been center aligned.

Referring toFIG.22B,FIG.22Bis a screen shot2250that illustrates an implementation of the change alignment174accessibility module. The align left button2255, when activated, implements the change alignment174accessibility module to change the alignment of text2260on a web page to a left alignment. Previously activated alignments may be cancelled when the align left button2255is activated.

As shown by the highlighting of the align left button2255in the screen shot2250ofFIG.22B, the align left button2255has been activated by a user. The align left button2255may be activated through input158such as a mouse click, touch or voice command. Any previous alignment of the text2260would be cancelled when the align left button2255is activated. As shown in the screen shot2250, the text2260has been aligned to the left.

Referring toFIG.23A,FIG.23Ais a screen shot2300that illustrates an implementation of the change alignment174accessibility module. An align right button2305, when activated by a user, may implement the change alignment174accessibility module to change to the alignment of the text2310to a right alignment. Activation of the align right button2305may cancel a previous alignment of the text2310, which allows the user to experiment with the alignment to determine a preferred alignment.

As shown by the highlighting of the align right button2305in the screen shot2300ofFIG.23A, the align right button2305has been selected by a user. The user may select and activate the align right button2305by clicking, touching, or other method of input158that selects objects on a screen. The change alignment174accessibility module may change the alignment of the text2310to a right alignment, as shown in the screen shot2300ofFIG.23A.

Referring toFIG.23B,FIG.23Bis a screen shot2350the illustrates an implementation of the change alignment174accessibility module with a justified alignment. An align justify button2355, may be selected by a user to implement the change alignment174accessibility module to cancel a previous alignment of text2360on a web page and align the text to a justified alignment. The justified alignment of text adjusts the letter spacing and word spacing to align the edges of the text with the left and right margins.

As shown by the highlighting of the align justify button2355in the screen shot2350, the align justify button2355has been selected by a user to activate the change alignment174accessibility module to change the alignment of text2360. A justified alignment of text2360, where text is aligned with the left and right margins, may improve the readability of the text2360for users with various disabilities.

Referring toFIG.24,FIG.24is a screen shot2400that illustrates an implementation of the change title color176accessibility module. The ability to modify the color of text on a web page may improve readability for users. Users may select a preferred color of text or experiment with colors to determine a preferred color of text. The title color button2405implements the change title color176accessibility module to change the color of text with a title tag in a web page. Changing the color of titles allows the user to differentiate titles from body text.

As shown by the highlighting of the title color, the title color button2405has been selected by the user. In an exemplary embodiment of the change title color176accessibility module that is shown in the screen shot2400ofFIG.24, a color picker2410is displayed in response to selecting the title color button2405. A check mark indicates a color that was selected by the user. The color of titles2415in the text of the web page may change to the color that was selected by the user.

Referring toFIG.25,FIG.25is a screen shot2500that illustrates an implementation of the change text color178accessibility module. The color of text2515on a web page may impact the readability of the text2515for users with various disabilities. The ability to modify and/or experiment with the color of the text2515enables those users to change the web page into a more readable form. A text color button2505, that is selectable by the user, may implement the change text color178accessibility module.

As indicated by the highlighting of a text color button2505in the screen shot2500, the user has selected the text color button2505to change the color of text2515on a web page that is displayed. In response to the selection of the text color button2505, the change text color178accessibility module may display a color picker2510that allows a user to view and select a color of text. As indicated by the check mark in the color picker2510, the user has selected a color that will be implemented by the change text color178accessibility module to change the color of the text2515in the web page.

Referring toFIG.26,FIG.26is a screen shot2600that illustrates an implementation of the remove images166accessibility module. Images on a web page may serve a variety of purposes, but may also be distracting for users with disabilities. The ability the toggle images off and on may allow users to remove such distractions and replace them at their leisure. A remove images button2605, when selected, may activate the remove images166accessibility module to remove or replace images on a web page.

As shown by the highlighting in the screen shot2600, the remove images button2605has been selected by a user. The images have been removed to leave blank space2610, which allows the user to focus on the text or other objects of the web page. The user may select the remove images button2605again to replace the images.

Terms such as “including” and “comprising” are intended to refer to components or steps in a non-exclusive manner. All terms and claims are intended to be interpreted in the broadest manner that is consistent with the disclosure. The terms “component” and “module” do not limit features and functions to a single object or collection. They may also refer to features and functions that are distributed across many objects or collections and set in many locations.