# Patent

## Title
Accessibility aids for users of electronic devices

## Abstract

A screen protector is provided with tactile aids for vision-impaired users. The screen protector can be placed on the display screen of a computing device to enhance the out-of-box experience for vision-impaired users and/or guide the user during subsequent use of the device. For example, the screen protector can be configured to be tactilely-informative about how to activate accessibility features of the device and/or how to proceed with initial set-up and configuration of the device. The screen protector may include, for example, braille instructions for activating the accessibility mode and/or a raised or embossed tactile aid that identifies the location of a UI control feature that can be engaged to initiate the accessibility mode or other desired function. Once the user has engaged the accessibility mode, the user may receive verbal instructions and cues going forward so as to allow the user to successfully use the device.

## Background
RELATED APPLICATION
Specification of the Disclosure
This application claims the benefit of U.S. Provisional Application Nos. 61/689,510 and 61/689,511, both filed on Jun. 7, 2012. In addition, this application is related to U.S. application Ser. No. 13912980 filed Jun. 7, 2013 and titled “Accessibility Aids for Users of Electronic Devices.” Each of these applications is herein incorporated by reference in its entirety.


FIELD OF THE DISCLOSURE
This disclosure relates to electronic computing devices, and more particularly, to accessibility aids for users of electronic computing devices.
BACKGROUND
Electronic computing devices such as tablets, e-readers, mobile phones, smart phones and personal digital assistants (PDAs) are commonly used to provide a user with both consumable and non-consumable content. Examples of consumable content include e-books, webpages, images, videos and maps; examples of non-consumable content include menus, settings, icons, control buttons and scroll bars. Such electronic devices typically include a user interface that allows a user to interact with the device, its applications and its content. For example, the user interface may include a touch screen display and/or one or more displayed labels that correspond to hardware controls associated with the device. A touchscreen display may or may not be backlit, and may be implemented for instance with a light-emitting diode (LED) screen or an electrophoretic display.



BRIEF DESCRIPTION OF THE DRAWINGS
FIGS. 1a-b illustrate an example computing device including a screen protector configured in accordance with an embodiment of the present invention.
FIG. 1c illustrates a block diagram of the computing device of FIGS. 1a-b, configured in accordance with an embodiment of the present invention.
FIG. 1d illustrates a block diagram of a communication system including the computing device of FIGS. 1a-c, configured in accordance with an embodiment of the present invention.
FIG. 2 illustrates a screen protector configured in accordance with an embodiment of the present invention.
FIG. 3 illustrates an example computing device including a screen protector configured in accordance with another embodiment of the present invention.
FIGS. 4a-c illustrate an example computing device configured with list-based user interface mode, in accordance with an embodiment of the present invention.
FIG. 5 illustrates a method of providing special accessibility to an impaired user of a computing device, in accordance with an embodiment of the present invention.



DETAILED DESCRIPTION
A screen protector is provided with tactile aids for users with impaired vision. The screen protector can be placed on the display screen of a computing device to enhance the out-of-box experience for vision-impaired users and/or guide the user during subsequent use of the device. For example, the screen protector can be configured to be tactilely-informative about how to activate special accessibility features of the device and/or how to proceed with initial set-up and configuration of the device. The screen protector may include, for example, braille instructions for activating a special accessibility mode and/or a raised or embossed tactile aid that identifies the location of a user interface (UI) control feature that can be tapped, pressed or otherwise engaged to initiate the special accessibility mode or other desired function. In a more general sense, the tactile instructions may provide information that will facilitate use of the device. Once the user has engaged a special accessibility mode with the aid of the tactilely informative screen protector, the user may receive verbal instructions going forward so as to allow the user to successfully use the device. Other accessibility features will be apparent in light of this disclosure such as a simplified UI that provides a content list that can be parsed and aurally presented in response to a vertical dragging gesture on the touch sensitive surface of the device.
General Overview
Presently, electronic computing devices support accessibility features for users with disabilities. For example, a computing device may feature a selectable mode where the text labels on screen controls can be spoken aloud to the user. However, there still remain various unresolved problems associated with such modes. For instance, currently available accessibility techniques do not address the initial process of powering up, configuring, and enabling the accessibility features. Some existing solutions offer printed initial configuration instructions on screen protectors, but such solutions are not a workable for the vision-impaired. Other existing solutions implicate a degree of complexity effectively rendering them impractical for many users. Moreover, vision-impaired users may further struggle with finding touch screen controls in a rich user interface, which may include feature controls placed on the screen in an irregular or otherwise inconsistent fashion, or placed on sliding panels (such as the home screen of devices using the Android platform). For instance, a vision-impaired user cannot visually locate or otherwise benefit from an icon or other such user-selectable items (e.g., shortcuts to books or music, and a clock) after those icons/items variously change position on a home screen of a given computing device. Adding to the complexity, the home screen itself may be scrollable or pannable.
Thus, and in accordance with an embodiment of the present invention, a screen protector is provided with tactile aids for users with impaired vision. The screen protector can be placed on the display screen of a computing device, such as a tablet or smartphone or other mobile computing device, to enhance the out-of-box experience for vision-impaired users. For example, the screen protector can be placed on the device during the manufacturing and packaging process, and configured to be tactilely-informative about how to activate special accessibility features of the device and/or how to proceed with initial set-up and configuration of the device.
In one example embodiment, the screen protector includes braille instructions for activating a special accessibility mode that facilitates further use of the device by a person with vision impairment (e.g., blindness or diminished ability to see). In one such case, the screen protector further includes a raised or embossed arrow or other tactile aid that effectively points from the braille instruction to a location of a user interface (UI) control feature that can be tapped, pressed or otherwise engaged to initiate the special accessibility mode or other desired function. Thus, the user can read the braille message and thereby be instructed to follow the raised arrow (or other tactile locationing aid) to a location on the touch screen where the user can then initiate a specified function or mode.
For instance, the braille message may instruct the user to follow the tactile locationing aid from the braille message to a location on the device where the user can provide a press-and-hold touch or a swipe gesture at the target location designated by the tactile aid so as to engage a special accessibility mode that aurally presents subsequent instructions and guidance to the vision-impaired user. In some such cases, the braille message may further include instructions as to what type of touch or gesture must be provided to initiate the mode, such as a two-finger press-and-hold of 10 seconds, or a V-shaped gesture (for voice). Numerous engagement mechanisms can be used.
In another embodiment, the braille message may instruct the user to follow the tactile locationing aid from the braille message to a location on the device where the user can engage a physical button or other UI control feature so as to initiate the special accessibility mode. Again, the braille message may include instructions as to how the user should engage that physical UI control feature to initiate the mode, such as a press-and-hold of 5 to 10 seconds on the home button or the volume-up button, for instance. As will be appreciated in light of this disclosure, the techniques provided herein can be used to initiate other functions as well. For example, the braille message may instruct the user to follow the tactile locationing aid from the braille message to a location on the device where the user can engage a virtual or physical button so as to increase the volume or some other desired function. Likewise, the braille or otherwise tactile instructions may include information that instructs the user on, for example, how to remove the screen protector, how to turn on the device, how to connect peripheral devices such as braille keyboards or displays, or otherwise provide instruction/information that will facilitate use of the device.
In some embodiments, the location of the UI control feature to be engaged by the user can be smooth to the touch, and the tactile aid of the screen protector effectively leads to and highlights that location for the user (e.g., with a raised arrow head pointing at the location, or a raised circle or square around the location). Note that sighted users may also see the target UI control feature in some cases, while in other embodiments there may be nothing actually displayed at that location for a sighted user to see (an active touch spot that is scanned for user input but that has no corresponding visual icon or control feature). Note that the screen protector can remain on the device after initial set-up and device configuration to continue to identity the touch location of various functions (e.g., launch browser, send message, etc). Further note that the screen protector may include textual instructions for sighted users. These textual instructions may be in the same position as the tactile instructions, since they may be readable through the tactile.
In other embodiments, the location of the UI control feature of the computing device may include a raised element (and/or a depressed element, as the case may be) that allows the user to further tactilely confirm that he/she has located the proper UI control feature. The device may have a combination of smooth and/or tactile UI control features having locations identified or otherwise accentuated by tactile aids of the screen protector, in accordance with some embodiments.
In some embodiments, the UI control feature identified with tactile aid(s) may be, for example, an icon or a virtual button, a physical home or power button, a volume button, or any other virtual or physical UI control feature that can be engaged to facilitate a vision-impaired user's out-of-box experience and/or continued use of the computing device. As previously explained, no visible UI control feature is necessary, so long as the touch sensitive surface can detect the touch in the target location. Depending on the touch sensitive surface technology, the touch may be directly on the surface or hovering a short distance (e.g., a few centimeters) over the surface. In any such cases, once the vision-impaired user has engaged a special accessibility mode with the aid of the tactilely informative screen protector, the user may receive verbal instructions going forward so as to allow the user to successfully use the device. Other accessibility features will be apparent in light of this disclosure (such as a simplified list-based UI), and a given computing device may be configured with any one or a combination of such accessibility features.
For example, in some embodiments, activating the special accessibility mode causes the device to initiate a simplified UI mode of operation, where complex user interface elements are replaced with simpler ones. For example, in one such embodiment, the simplified UI mode can be initiated, configured, or otherwise triggered when the device is placed into accessibility mode, for instance when setting up the device for the first time (out-of-box), or through the device's settings controls. Alternatively, the computing device may have a separate simplified UI mode, either as a sub-mode of accessibility or as a distinct feature on its own. The simplified UI mode places information in a format which can be readily navigated by means of gesture-invoked audible prompts. In one such embodiment, content, functions, and/or other selectable items on the home screen of the user's device (or from the main panels of the device) are assembled into a one-dimensional list. In some cases, the simplified UI mode may be further configured to receive a vertical drag gesture that causes each item of the list to be aurally presented to the user as the drag gesture progresses downward. In a more general sense, the simplified UI mode can be configured to receive a parsing gesture (e.g., downward swipe gesture) that causes an item of the list to be aurally presented to the user, and a selection gesture (e.g., release of the drag gesture or a two-finger tap gesture) to select the last aurally presented item. Numerous other touch-based or other suitable parsing/selection gesture schemes will be apparent in light of this disclosure. In one specific embodiment, the location of the parsing/select gestures can be anywhere on the touch sensitive surface and need not necessarily be on or otherwise near the presented list.
Computing Device Architecture
FIGS. 1a-b illustrate an example computing device including a screen protector configured in accordance with an embodiment of the present invention. The device could be, for example, a tablet such as the NOOK® Tablet or NOOK® eReader by Barnes & Noble. In a more general sense, the device may be any electronic device having capability for displaying content to a user, such as a mobile phone or mobile computing device such as a tablet or laptop, a desktop computing system, a television, a smart display screen, or any other device having a touch screen display. As will be appreciated, the claimed invention is not intended to be limited to any particular kind or type of electronic device.
As can be seen with this example configuration, the device comprises a housing, a touch screen display, and a screen protector provided over that touch screen display. The housing includes a number of hardware features such as a grommet, a speaker, a power button, and a home button. The grommet can be used, for example, to stow or otherwise secure the device in a notebook, bag or case. The speaker can be used to aurally present content and/or instructive information (such as aurally presented prompts provided during an accessibility mode) to the user. The touch screen display can be used in conjunction with a touch-based user interface (UI). One example touch-based UI includes a quick navigation menu or tool bar having a number of user-selectable categories (e.g., Home, Library, Shop, Search, and Settings) so as to provide quick access to various features of the device. The touch-based UI may further include other features such as a status bar that includes one or more icons (e.g., a wireless network icon), a battery indicator, and a clock, to name a few examples. Other embodiments may have fewer or additional UI touch screen controls and features, or different UI touch screen controls and features altogether, depending on the target application of the device. Any such general UI controls and features can be implemented using any suitable conventional or custom technology, as will be appreciated.
The power button can be used to turn the device on and off, and may be used in conjunction with a touch-based UI control feature that allows the user to confirm a given power transition action request (e.g., such as a slide bar or tap point graphic to turn power off). The home button can be a virtual or physical press-button, and may be used in various ways. In one example embodiment, when the device is awake and in use, tapping the home button may display or otherwise present a quick navigation menu that provides quick access to various features of the device. The home button may further control other functionality, for example, if the user presses and holds the home button. For instance, an example such push-and-hold function could engage a special accessibility mode (if held for 5 to 10 seconds) or a power conservation mode (if held for greater than 10 seconds). The special accessibility mode can be invoked, for example, by a vision-impaired user to provide access to a user interface that is more user friendly, and the power conservation mode can be invoked to put the device to sleep or into an otherwise lower power consumption mode for an anticipated period of non-use. The home button may also be configured to cease an active function that is currently executing on the device, such as an accessibility mode or sub-mode thereof as variously described herein. Thus, in such an example embodiment, the home button may be associated with and control different and unrelated actions: 1) show or otherwise present the quick navigation menu; 2) exit a given mode of operation; and 3) put the device to sleep. Numerous other configurations and variations will be apparent in light of this disclosure, and the claimed invention is not intended to be limited to any particular set of virtual buttons, hardware buttons or other UI control features, or device form factor.
As can be seen, the screen protector is provided over the touch screen display and includes a number of tactile aids to assist vision-impaired users, and optionally includes textual instructions that may be useful for sighted users. As can be seen in this example embodiment, the tactile aids include three braille instructions/messages and two tactile locationing aids. One of the locationing aids tactilely identifies the location of the power button and the other locationing aid tactilely identifies the location of the home button. Note that such tactile locationing aids are particularly helpful in locating virtual UI control features that otherwise have no texture that might be detectable by touch, but can also be helpful in distinguishing between multiple physical UI control features. The screen protector will be discussed in further detail with reference to FIG. 2.
As will be appreciated, the various UI control features and sub-menus displayed to the user are implemented as UI touch screen controls in this example embodiment. Such UI touch screen controls can be programmed or otherwise configured using any number of conventional or custom technologies. In general, the touch screen translates the user touch in a given location into an electrical signal which is then received and processed by the underlying operating system (OS) and circuitry (processor, etc). Additional example details of the underlying OS and circuitry in accordance with some embodiments will be discussed in turn with reference to FIG. 1c. 
FIG. 1c illustrates a block diagram of an electronic device configured in accordance with an embodiment of the present invention. As can be seen, this example device includes a processor, memory (e.g., RAM and/or ROM for processor workspace and storage), additional storage/memory (e.g., for content), a communications module, a touch screen, and an audio module. A communications bus and interconnect is also provided to allow inter-device communication. Other typical componentry and functionality not reflected in the block diagram will be apparent (e.g., battery, co-processor, etc). Further note that although a touch screen display is provided, other embodiments may include a non-touch screen and a touch sensitive surface such as a track pad, or a touch sensitive housing configured with one or more acoustic sensors, etc. In any such cases, the touch sensitive surface is generally capable of translating a user's physical contact with the surface into an electronic signal that can be manipulated or otherwise used to trigger a specific user interface action, such as those provided herein. The principles provided herein equally apply to any such touch sensitive devices. For ease of description, examples are provided with touch screen technology.
In this example embodiment, the memory includes a number of modules stored therein that can be accessed and executed by the processor (and/or a co-processor). The modules include an operating system (OS), a user interface (UI), and a power conservation routine (Power). The modules can be implemented, for example, in any suitable programming language (e.g., C, C++, objective C, JavaScript, custom or proprietary instruction sets, etc), and encoded on the memory (any suitable non-transient machine readable medium), that when executed by the processor (and/or co-processors), carries out the functionality of the device including a UI having an accessibility mode as described herein. Other embodiments can be implemented, for instance, with gate-level logic or an application-specific integrated circuit (ASIC) or chip set or other such purpose built logic, or a microcontroller having input/output capability (e.g., inputs for receiving user inputs and outputs for directing other components) and a number of embedded routines for carrying out the device functionality. In short, the functional modules can be implemented in hardware, software, firmware, or a combination thereof.
The processor can be any suitable processor (e.g., Texas Instruments OMAP4, dual-core ARM Cortex-A9, 1.5 GHz), and may include one or more co-processors or controllers to assist in device control. In this example case, the processor receives input from the user, including input from or otherwise derived from the power button and the home button. The processor can also have a direct connection to a battery so that it can perform base level tasks even during sleep or low power modes. The memory (e.g., for processor workspace and executable file storage) can be any suitable type of memory and size (e.g., 256 or 512 Mbytes SDRAM), and in other embodiments may be implemented with non-volatile memory or a combination of non-volatile and volatile memory technologies. The storage (e.g., for storing consumable content and user files) can also be implemented with any suitable memory and size (e.g., 2 GBytes of flash memory).
The display can be implemented, for example, with a 7 to 9 inch 1920×1280 IPS LCD touchscreen touch screen, or any other suitable display and touch screen interface technology. As will be appreciated in light of this disclosure, the display may further include touch detection technology and can be any display that is configured with touch detecting technologies, whether capacitive, resistive, acoustic, active-stylus, and/or other input detecting technology. For example, in some embodiments, the screen display can be layered above input sensors, such as a capacitive sensor grid for passive touch-based input via a finger or stylus in the case of a so-called in-plane switching (IPS) panel, or an electro-magnetic resonance (EMR) sensor grid. In some embodiments, the touch sensitive display can be configured with a purely capacitive sensor, while in other embodiments the display may be configured to provide a hybrid mode that allows for both capacitive input and EMR input, for example. In still other embodiments, the touch sensitive display is configured with only an active stylus sensor. Numerous touch screen display configurations can be implemented using any number of known or proprietary screen based input detecting technologies. In any such embodiments, the display may further include a controller configured to selectively scan the touch sensitive display and/or selectively report touch inputs detected directly on or otherwise sufficiently proximate to (e.g., within a few centimeters, or otherwise sufficiently close so as to allow detection) the touch sensitive display. In one example embodiment, a touch input can be provided by a stylus or finger(s) hovering some distance above the touch sensitive surface (e.g., one to a few centimeters above the surface, or even farther, depending on the sensing technology deployed in the touch sensitive display surface), but nonetheless triggering a response at the device just as if direct contact were provided directly on the display.
The communications module can be, for instance, any suitable 802.11 b/g/n WLAN chip or chip set, which allows for connection to a local network so that content can be downloaded to the device from a remote location (e.g., content provider, etc, depending on the application of the display device). In some specific example embodiments, the device housing that contains all the various componentry measures about 7′′ to 9′′ high by about 5′′ to 6′′ wide by about 0.5′′ thick, and weighs about 7 to 8 ounces. Any number of suitable form factors can be used, depending on the target application (e.g., laptop, desktop, mobile phone, etc). The device may be smaller, for example, for smartphone and tablet applications and larger for smart computer monitor applications.
The operating system (OS) module can be implemented with any suitable OS, but in some example embodiments is implemented with Google Android OS or Linux OS or Microsoft OS or Apple OS. As will be appreciated in light of this disclosure, the techniques provided herein can be implemented on any such platforms. The power management (Power) module can be configured, for example, to automatically transition the device to a low power consumption or sleep mode after a period of non-use. A wake-up from that sleep mode can be achieved, for example, by a physical button press and/or a touch screen swipe or other action. The user interface (UI) module can be, for example, based on touch screen technology and the various example screen shots and use case scenarios shown in FIGS. 1a, 2, 3, and 4a-c, in conjunction with the accessibility mode methodologies demonstrated in FIG. 5, which will be discussed in turn. The audio module can be used in conjunction with the speaker and configured, for example, to aurally present initial configuration or use instructions or selected content, if preferred by the user (e.g., as part of a special accessibility mode suitable for vision-impaired users). Numerous commercially available text-to-speech modules can be used, such as Verbose text-to-speech software by NCH Software. In some example cases, if additional space is desired, for example, to store digital books or other content and media, storage can be expanded via a microSD card or other suitable memory expansion technology (e.g., 32 GBytes, or higher). Further note that although a touch screen display is provided, other embodiments may include a non-touch screen and a touch sensitive surface such as a track pad, or a touch sensitive housing configured with one or more acoustic sensors, etc.
FIG. 1d illustrates a block diagram of a communication system configured in accordance with an embodiment of the present invention. As can be seen, the system generally includes an electronic device (such as the one shown in FIGS. 1a-c) that is capable of communicating with an application server via a network/cloud. In this example embodiment, the electronic device may be, for example, an eBook reader, a mobile cell phone, a laptop, a tablet, desktop, or any other touch sensitive computing device. The network/cloud may be a public and/or private network, such as a private local area network operatively coupled to a wide area network such as the Internet. In this example embodiment, the server may be programmed or otherwise configured to receive content requests from a user via the device and to respond to those requests by providing the user with requested or otherwise recommended content. In some such embodiments, the server is configured to remotely provision an accessibility mode or sub-mode to the device (e.g., via JavaScript or other browser based technology configured to provision list-based content that can be aurally presented in response to a vertical drag gesture on the touch screen display). In one such case, the URL of the application server (or other location identifier associated with the server) can be brought to the user's attention via a tactile aid provided on the screen protector. Thus, when the user touches or otherwise selects the URL as directed and guided by the tactile aid, the device will issue a request to the server to issue content in a spoken or otherwise aurally presented format. In other embodiments, portions of the accessibility methodology are executed on the server and other portions of the methodology are executed on the device. Numerous server-side/client-side execution schemes can be implemented to facilitate a content selecting mode in accordance with an embodiment, as will be apparent in light of this disclosure.
Screen Protector
FIG. 2 illustrates a screen protector configured in accordance with an embodiment of the present invention. As can be seen, the screen protector is configured with a number of tactile aids including instructions or messages in braille and embossed or raised graphics. As can be seen in this example case, the graphics include an arrow pointing from a given braille message to the power switch on the side of the device. In one such example case, the braille message might be, for instance, “Power switch is located here—follow raised arrow.” The graphics also include a raised line provided from another given braille message to a circle around the home button. In one such example case, the braille message might be, for instance, “press and hold for 10 seconds the home button within the raised circle at the end of this line to enter special accessibility mode.” Numerous other tactile aids will be apparent in light of this disclosure (e.g., a single line or multiple lines and arrow-heads/circles/squares pointing to or otherwise identifying the location of device features, such as volume controls, headphone jacks, or other aids).
As will be further appreciated, the braille messages may include any type of helpful instructions or information that may improve the user experience of a vision-impaired user of the device. For instance, a given braille message may include instructions on how to remove the screen protector, how to turn on the device, how to activate special accessibility features of the device, how to connect peripheral devices such as braille keyboards or displays, how to initiate aural presentation of device configuration routine, how to access the quick launch menu of the device so as to access the control settings or other feature, how to access technical support, how to access forums suitable for similarly situated users (e.g., a blog or forum developed by and for vision-impaired users), etc. As can be further seen, such an enhanced screen protector may also include textual instructions for sighted users. In one such embodiment, these textual instructions may be in the same position as the tactile instructions, since they may be readable through the tactile aids.
The screen protector can be implemented with any number of suitable materials, such as clear plastic film or velum or any material upon which tactile aids can be embossed or otherwise provisioned (e.g., paper, cardboard, foil, rigid plastic, glass, metal, ceramic, etc). The screen protector may be left attached to the device, or may be removed/disposable once the user has used the protector to learn about the accessibility mode of the device. In the disposable case, the user can peel-off or otherwise remove and discard the screen protector, in accordance with some embodiments. The screen protector may be transparent, but need not be, depending on the type of users anticipated. In any such cases, conventional embossing and/or printing techniques can be used to impart the tactile aids to the screen protector (e.g., pressure-based imprinting, vacuum-based imprinting, lithography, injection molding, etching, laser printing for braille, etc). The screen protector can then be fixed to or otherwise secured on the display of the device. Note that, in some cases, the protector can be applied to the display screen early in the manufacturing process, so as to protect the display during subsequent manufacturing processes. Alternatively, the protector can be applied to the display screen at the end of manufacturing process prior to packaging. Alternatively, the protector can be purchased or otherwise acquired separately from the device and applied to the screen post-purchase of the device.
FIG. 3 depicts an embodiment wherein the screen protector with tactile aids covers only a portion of the screen and allows the user to have access to the rest of the display. Such an embodiment may be useful, for example, for configurations where the user can enter the accessibility mode by pressing and holding a virtual home button or icon (e.g., as directed by the braille message and wherein the virtual home button or icon is within a raised circle or square at the end of a raised line from that runs from the braille message to the location of the virtual button/icon, such as shown in the example of FIG. 3), and still directly access the touch screen so as to provide touches and gestures to interact with the device. In one such case, once the accessibility mode is invoked, the location of the touches/gestures on the touch screen can be independent of the location of the content or other items being selected. In other words, the user need not have to see the selectable elements to make selections or otherwise interact with the device.
For instance, once invoked the accessibility mode of the device may be programmed or otherwise configured to provide all of the content and other user-selectable items on the home screen or panels, or some sub-set thereof based on for example user-selection or configuration, in a one-dimensional list. Subsequently, any drag gestures, taps, or other touches received anywhere on (or sufficiently proximate to) the touch screen can be used to cause the device to aurally present each item on the list in sequential order so that the presented item can be selected by the user. For example, the accessibility mode of the device may be configured to, in response to a vertical drag gesture (anywhere on touch screen), cause each item on the list to be aurally presented in sequence (e.g., from top to bottom), and in response to a subsequent screen tap (anywhere on touch screen) after a given aural presentation, cause selection of that aurally presented item. In this way, the user need not be able to see the content (or even the list) on the home screen or panels (or other user screens). Rather, once the accessibility mode is activated, the user can interact with the device via the simplified list-based UI and receive aural instructions and prompts to facilitate use of device and make content selections and otherwise direct the device by screen taps when appropriate, in accordance with an embodiment of the present invention. Additional details of a simplified UI will be provided with further reference to FIGS. 4a-c and 5.
Numerous other configurations of screen protectors that partially cover the underlying display screen will be apparent in light of this disclosure. For instance, in another embodiment, the screen protector may be configured with various tactile aids as variously discussed herein and also include an elongated cut-out or window where swipe and tap gestures can be provided. In one such example embodiment, once in the accessibility mode, the scan controller of the device can be configured to only scan and/or report touches that are provided in that window. Such selective scanning/reporting can be used to save on battery power, which is particularly helpful for mobile devices. Note that the gesture window may also be associated with a braille message that explains its purpose, and is effectively tactile in nature due to the detectable edge defining the perimeter of the window.
Simplified UI
FIGS. 4a-c illustrate an example computing device configured with a simplified UI mode that includes a list-based selection mechanism, in accordance with an embodiment of the present invention. Note that the previous discussion with respect to FIGS. 1a-c is equally applicable here, although note that the simplified UI mode need not be used in conjunction with the screen protector. This simplified UI mode can be used to assist users with access and use of an electronic device, by effectively replacing complex user interface elements with simpler ones, and in one specific example case, by placing information in a list format which can be readily navigated by means of gesture-invoked audible prompts. In one embodiment, the simplified UI mode can be initiated, configured, or triggered, in response to the device being placed into the special accessibility mode as directed by the screen protector (e.g., “press and hold point at end of raised arrow to invoke accessibility mode”), for example, when setting up the device for the first time (out-of-box), or through the device's control settings. Alternatively, the simplified UI mode may be a sub-mode of the special accessibility mode, or a distinct feature that can be provided independently of any other modes or features of the device. To this end and as will be appreciated in light of this disclosure, the simplified UI has a usefulness that is independent of the screen protector.
As can be seen, FIG. 4a illustrates an example home screen of the device that includes multiple application icons and other items arranged in a random pattern on the screen. The application icons may include, for instance, an email application icon, a phone application icon, a settings icon, a game icon, and/or any other icons that can be tapped or otherwise selected to launch a corresponding application or function. Some examples of other items include, for instance, shortcuts to books or music or other consumable content, and a clock shown at the top right. Adding to the complexity of this UI arrangement is that the home screen may be scrollable or pannable, or include multiple panels that can be navigated with horizontal swiping or flicking gestures. For a vision-impaired user, such randomness and lack of consistent presentation can significantly impede or otherwise preclude use of the device. A user with cognitive disability may experience a similar disadvantage.
FIG. 4b illustrates an example simplified UI mode that includes a one-dimensional list that can be more easily navigated and interacted with, in accordance with an embodiment of the present invention. As can be seen, the one-dimensional list includes the various application icons and other items that were randomly positioned on the home screen shown in FIG. 4a. The simplified UI mode is programmed or otherwise configured to present these randomly icons/items in list format. In one such embodiment, the simplified UI mode is further configured to, in response to a user's swipe or tap on the touch screen, aurally present each item on the list in a sequential fashion.
For example, in response to a first downward vertical swipe gesture the simplified UI mode can be configured to aurally present “Application 1”, and in response to a second downward vertical swipe the simplified UI mode can be configured to aurally present “Application 2”, and so on. Should the user wish to select the aurally presented item, the user can provide a screen tap. Thus, the user can use swipes to effectively navigate to the desired item on the list, and then select that item with a tap. The user can thus launch applications and access content as desired.
As previously explained, once the simplified UI mode is invoked, the location of the touches/gestures on the touch screen can be independent of the location of the content or other items being selected. In other words, the user need not have to see the selectable elements to make selections or otherwise interact with the presented list. For instance, and as shown in FIG. 4c, a downward swipe gesture can be provided directly on or close to the list, but can also be provided elsewhere on the screen (such as the lower right corner, as further shown in FIG. 4c). To this end, the simplified UI mode can be configured to, once invoked, direct the display controller to only report specific gestures that are used for navigating the list and making selections, or to exit the simplified UI mode, in accordance with an embodiment. Alternatively, the simplified UI mode can be configured to allow all contacts to be reported, but to respond to only the specific gestures allowed (e.g., downward two finger swipe to parse list via sequential aural presentation one item at a time, and two finger tap to select last aurally presented item of the list) and ignore all other touches. Such selective touch response may further enhance the user experience.
As will be appreciated in light of this disclosure, different gestures or touches by the user can be used to invoke different responses by the simplified UI mode. For example, note that the time is provided in a somewhat separate fashion from the rest of the listed items. In one such embodiment, in response to a two-finger downward vertical swipe gesture the simplified UI mode can be configured to aurally present the current time (e.g., “the time is 7:43 am”), and in response to a one-finger downward vertical swipe gesture the simplified UI mode can be configured to aurally present each item in the list in a sequential fashion as previously explained. Also, the selection of an aurally presented item can be made, for instance, with a two-finger tap, so as to distinguish a list-item selection gesture from some other command (such as a global “go-back” one-finger tap command). Numerous other such touch-based navigation schemes can be used.
In some embodiments, the simplified UI mode can be used in conjunction with a screen protector as previously described, wherein the list of selectable items can be presented within a cut-out or window of the screen protector. As previously explained, the scan controller of the device's display assembly can be configured to only scan and/or report touches that are provided within that window. Alternatively, or in addition, the screen protector may direct a vision-impaired user on how to invoke the simplified UI mode, so as to facilitate use of that device by the user.
In some embodiments, panning can be disabled in the simplified UI mode as can any panel-based navigation involving multiple screens, and all or a subset of items that would have been visually presented on those various screens are presented in list form as depicted in FIG. 4b (contrasted with FIG. 4a for a random home screen). In some cases, the user may select the items to be provided in the list and/or the list may include a number of default or otherwise hard-coded items that are automatically put in the list. For instance, during initial configuration, the simplified UI mode (or other accessibility mode) can be configured to aurally present a master list of available items to the user and the user can add any aurally presented item to the list by saying “yes” or “add to list” (or some other comparable voice command), or by tapping the touch screen twice or with a 2-finger tap. Conversely, excluding items from the list can be done, for instance, by saying, “no” or a 1-finger tap.
In some embodiments, the simplified UI mode is further configured to prioritize the list based on user-selection patterns and historical usage. Thus, items that are more frequently selected by the user can be moved toward the top of the list and items that are less frequently selected by the user can be moved toward the bottom of the list. Usage statistics can be maintained, for instance, in one or more variables/counters maintained by the simplified UI mode.
In some cases, audible navigation may be activated separately, and need not be configured in all embodiments. For instance, the simplified UI mode having a list-based interface with or without an audible navigation feature may be helpful to sighted users with cognitive impairments. If audio feedback is enabled, a user may move one or more fingers down the list to hear each item aurally presented in turn. For example, in one embodiment, the name of a listed application can be aurally presented to the user, the title and/or description of listed consumable content can be aurally presented to the user, or in the case of a listed informational function such as a time function or a temperature function, the current time of day or the temperature can be aurally presented to the user. For content items, a snippet may be provided to the user, such as 10 seconds of a listed music file or playlist or the first few sentences of an eBook. Alternatively, or in addition, non-verbal sounds can be used, for example, so long as the user can associate those sounds with a listed piece of content or application or other selectable item of the list.
As will be appreciated, the simplified UI mode can be applied across a wide range of applications in a similar fashion, thus enhancing accessibility across the device experience. Note that the device may or may not include a screen protector, such as the one shown in FIGS. 1a, 2 or 3, although any suitable screen protector configuration having tactile aids embossed thereon can be used. If the screen protector is included, it may be left on the device for longer term use or removed after, for instance, initial configuration of the computing device, as previously explained.
Methodology
FIG. 5 illustrates a method of providing special accessibility to an impaired user of a computing device, in accordance with another embodiment of the present invention. This example methodology may be implemented, for instance, by the UI module of the touch sensitive device shown in FIG. 1c, or the touch sensitive device shown in FIG. 1d (e.g., with the UI provisioned to the client by the server). To this end, the UI can be implemented in software, hardware, firmware, or any combination thereof, as will be appreciated in light of this disclosure.
As can be seen, the method may be used in conjunction with a screen protector configured with tactile aids, but may also be used independently of (and without) such a screen protector. As can be further seen, this example embodiment includes sensing a user's input by a touch sensitive surface. In general, any touch sensitive device may be used to detect contact with it by one or more fingers and/or styluses. As soon as the user begins to drag or otherwise move the contact points, the UI code (and/or hardware) can assume a drag gesture has been engaged and track the path of each contact point with respect to any fixed point within the touch surface until the user stops engaging the touch sensitive surface. The release point can also be captured by the UI as it may be used to commit the action started when the user pressed on the touch sensitive surface. In a similar fashion, if the user releases hold without moving the contact point, a press or press-and-hold command may be assumed depending on the amount of time the user was continually pressing on the touch sensitive surface. These main detections can be used in various ways to implement UI functionality. In still other embodiments, an accessibility mode configured with a list-based presentation that can be aurally presented to the user as described herein can be used on a system that includes any type of user input mechanism, such as a mouse, joystick, or other suitable user input device, wherein input provided by the given input device causes a detectable and actionable signal that can be used to invoke and/or otherwise direct the methodology.
In this example case, the method includes detecting 501 user contact at the touch sensitive interface. In general, the touch monitoring is effectively continuous. The method continues with determining 503 if the contact indicates that the accessibility mode is desired. As previously explained, the touch that invokes the accessibility mode can be provided, for example at a specific location on the touch screen and/or on a specific UI control feature. In some such embodiments, that specific location may be highlighted by tactile aids of a screen protector that further includes a braille message to the user explaining how to invoke the accessibility mode. In any case, the determining 503 may include selectively scanning and reporting touches (direct or otherwise sufficiently proximate) at that location. Further recall that the location may be visually identified with a marker (e.g., icon or switch) or not.
If it is determined that the accessibility mode is not desired, the method continues with reviewing 504 the contact for some other UI request. However, if it is determined that the accessibility mode is desired, the method continues with activating 505 the accessibility mode to direct initial configuration of device. Thus, a special mode of operation is invoked to allow an impaired user to continue use of the device. The user may be, for instance, vision-impaired and/or cognitive-impaired. In some example embodiments, this accessibility mode of operation is configured to aurally present information and choices to the user during initial configuration of the device, thereby providing an enhanced out-of-box experience for the impaired user. As will be appreciated in light of this disclosure, the accessibility mode may further include (or alternatively include) a simplified user interface that is more accommodating of the user's impairment.
The method of this example embodiment continues with determining 507 if a list-based user interface mode should be initiated. In some example cases, if the user has provided the initial touch (or other user input) at 503, then this list-based UI mode can be automatically invoked as part of the overall accessibility mode. In other embodiments, the list-based UI mode is invoked separately or not at all, if so desired. For instance, in some example embodiments, the methodology comprises invoking an accessibility mode in response to receiving user input as directed via a tactically-enhanced screen protector, without providing any list-based UI mode of operation.
If it is determined at 507 that a list-based user interface mode should not be initiated, then the methodology concludes and continues to monitor for other touches (or other user input). On the other hand, if it is determined at 507 that a list-based user interface mode should be initiated, then the methodology continues with disabling 509 panning and/or panel-based UI functionality. As previously explained, navigating a pannable or multi-screen UI presents a particular challenge to some users, so disabling or otherwise removing such functionality from consideration allows for that user to continue using the device in the context of a positive user experience.
The method continues with presenting 511 selectable content in list-form. As previously explained, the content included in the list may be user-configurable and/or hard-coded, and may further be prioritized based on usage history associated with a given user. Note that different users of the same device may have different usage statistics, so in some such embodiments, a user account can be established so as to allow the accessibility mode to distinguish between users.
The method continues with aurally presenting 513 each item on list in a sequential fashion and in response to a parsing gesture (e.g., vertical drag gesture or three finger tap), and selecting 515 an aurally presented item in response to a selection gesture (e.g., upon release of vertical drag gesture or two finger tap). Numerous parsing and selection gesture schemes can be used as will be appreciated in light of this disclosure. As previously explained, the aural presentation may include, for instance, the name of a listed application (e.g., “word processor” or “email”), or the title and author and/or a snippet of listed consumable content (e.g., “The Catcher in the Rye, J. D. Salinger: ‘If you really want to hear about it, the first thing you'll probably want to know is where I was born, and what my lousy childhood was like, and how my parents were occupied and all before they had me, and all that David Copperfield kind of crap, but I don't feel like going into it, if you want to know the truth’), or the result/output of a listed function (e.g., enunciation of current time or temperature). After a selection is made, the methodology may repeat as desired.
Numerous variations will be apparent in light of this disclosure. For instance, one example embodiment provides an accessibility system. The system includes a screen protector for protecting a display screen of a computing device and having one or more tactile aids configured to facilitate use of the computing device by a vision-impaired user. In some cases, the one or more tactile aids include a braille message. In some such cases, the braille message includes information on how to remove the screen protector from the computing device. In some cases, the braille message includes information on how to turn on the computing device. In some cases, the braille message includes information on how to activate accessibility features of the computing device. In some cases, the braille message includes information on how to connect peripheral devices that will assist the vision-impaired user in use of the device. In some cases, the one or more tactile aids include a raised directional element that identifies a location of a user interface control feature of the device. In one such case, the raised directional element includes a raised line that runs from proximate to a braille message to a location of a user interface control feature of the device. In some cases, the screen protector further includes printed instructions for sighted users that are readable through the one or more tactile aids. In some cases, the screen protector is removable from the computing device. In some cases, the screen protector is configured to only cover a portion of the display screen of the computing device. In some cases, the one or more tactile aids of the screen protector tactilely indicate how to activate accessibility features of the computing device. In one such case, the system further includes the computing device, wherein the accessibility features of the computing device include a simplified user interface mode that presents selectable content in a list format, wherein that selectable content is presented in a non-list format when the device is not in the simplified user interface mode. In some such cases, the simplified user interface mode is further configured to aurally present items in the list in response to a user swipe gesture. In some cases, the simplified user interface mode is further configured to disable panning. In some cases, the selectable content in list format comprises user-defined items.
Another embodiment of the present invention provides a system. In this example case, the system includes a mobile computing device having a display screen, and a screen protector disposed on and for protecting the display screen and having one or more tactile aids configured to facilitate use of the computing device by a vision-impaired user. In one such example case, the one or more tactile aids include a braille message and a raised directional element that identifies a location of a user interface control feature of the device, and wherein the braille message includes information on how to at least one of remove the screen protector from the computing device, turn on the computing device, activate accessibility features of the computing device, and/or connect peripheral devices that will assist the vision-impaired user in use of the device.
Another embodiment of the present invention provides a system. In this example case, the system includes a mobile computing device having a touch screen display and configured with accessibility features including a simplified user interface mode that presents selectable content in a list format, wherein that selectable content is presented in a non-list format when the device is not in the simplified user interface mode. The system further includes a screen protector disposed on and for protecting the display and having one or more tactile aids configured to tactilely indicate how to activate accessibility features of the computing device when setting the device up for the first time, wherein the one or more tactile aids include a braille message and a raised line that runs from proximate to the braille message to a location of a user interface control feature of the device. In some cases, the simplified user interface mode is further configured to aurally present items in the list in response to a user swipe gesture on the display.
The foregoing description of the embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto.

## Claims

1. An accessibility system, comprising:
a screen protector for protecting a display screen of a computing device and having one or more tactile aids configured to facilitate use of the computing device by a vision-impaired user;
wherein the one or more tactile aids include a braille message, the message including information on how to at least one of:
remove the screen protector from the computing device;
turn on the computing device;
activate accessibility features of the computing device, the accessibility features intended to assist visually-impaired users; and
connect peripheral devices that will assist the vision-impaired user in use of the device; and

wherein the one or more tactile aids further include a raised directional element that runs from proximate to the braille message to a location associated with a user interface control feature of the device.

2. The system of claim 1 wherein the braille message includes information on how to remove the screen protector from the computing device.

3. The system of claim 1 wherein the braille message includes information on how to turn on the computing device.

4. The system of claim 1 wherein the braille message includes information on how to activate accessibility features of the computing device.

5. The system of claim 1 wherein the braille message includes information on how to connect peripheral devices that will assist the vision-impaired user in use of the device.

6. The system of claim 1 wherein the raised directional element that identifies a location of a user interface control feature of the device comprises an arrow.

7. The system of claim 6 wherein the raised directional element includes a raised line that runs from proximate to a braille message to a location of a user interface control feature of the device.

8. The system of claim 1 wherein the screen protector further includes printed instructions for sighted users that are readable through the one or more tactile aids.

9. The system of claim 1 wherein the screen protector is removable from the computing device.

10. The system of claim 1 wherein the screen protector is configured to only cover a portion of the display screen of the computing device.

11. The system of claim 1 further comprising the computing device, wherein the accessibility features of the computing device include a simplified user interface mode that presents selectable content in a list format, wherein that selectable content is presented in a non-list format when the device is not in the simplified user interface mode.

12. The system of claim 11 wherein the simplified user interface mode is further configured to aurally present items in the list in response to a user swipe gesture.

13. The system of claim 11 wherein the simplified user interface mode is further configured to disable panning.

14. The system of claim 11 wherein the selectable content in list format comprises user-defined items.

15. A system, comprising:
a mobile computing device having a display screen; and
a screen protector disposed on and for protecting the display screen and having one or more tactile aids configured to facilitate use of the computing device by a vision-impaired user;
wherein the one or more tactile aids include a braille message, the message including information on how to at least one of:
activate accessibility features of the computing device, the accessibility features intended to assist visually-impaired users; and
connect peripheral devices that will assist the vision-impaired user in use of the device; and

wherein the one or more tactile aids further include a raised directional element that runs from proximate to the braille message to a location associated with a user interface control feature of the device.

16. The system of claim 15 wherein the braille message further includes information on how to at least one of remove the screen protector from the computing device, and turn on the computing device.

17. A system, comprising:
a mobile computing device having a touch screen display and configured with accessibility features including a simplified user interface mode that presents selectable content in a list format, wherein that selectable content is presented in a non-list format when the device is not in the simplified user interface mode; and
a screen protector disposed on and for protecting the display and having one or more tactile aids configured to tactilely indicate how to activate accessibility features of the computing device when setting the device up for the first time, wherein the one or more tactile aids include a braille message and a raised line that runs from proximate to the braille message to a location of a user interface control feature of the device.

18. The system of claim 17 wherein the simplified user interface mode is further configured to aurally present items in the list in response to a user swipe gesture on the display.

19. The system of claim 17 wherein the braille message includes information on how to at least one of:
remove the screen protector from the computing device;
locate a specified user interface control feature of the computing device;
activate accessibility features of the computing device; and
connect peripheral devices that will assist the vision-impaired user in use of the device.