1
APPARATUS AND METHODS FOR
FILTERING CONTENT BASED ON
ACCESSIBILITY TO A USER
TECHNICAL FIELD 5
The present invention is directed to an improved computer system. More particularly, the present invention provides apparatus and methods for filtering content based on accessibility to a user. 1°
DESCRIPTION OF RELATED ART
Recently there has been increased emphasis on designing Internet Web pages and content such that the content is 15 accessible to persons having special needs, such as those having a handicap or disability. While there is an increased emphasis on the need to make content accessible, the reality is that much of the content still available over the Internet is not accessible to persons having special needs. 20
In an effort to identify Web content that is and is not accessible to persons having special needs, the Center for Applied Special Technology (CAST) has developed a software application entitled BobbyTM. The BobbyTM software may be used to evaluate a Web page to determine if the Web page meets criteria that are based on accessibility guidelines promulgated by the World Wide Web Consortium. If BobbyTM determines that a Web page meets the accessibility criteria, the Web page administrator is permitted to add a 3Q Bobby approved icon to the Web page to indicate to handicapped or disabled persons that the Web page is accessible to them.
While BobbyTM provides a mechanism for evaluating Web pages, a user is not aware of whether a Web page is 35 Bobby approved until after the user retrieves the Web page. In fact, BobbyTM approved Web pages are a minority when taking into consideration all of the Web pages accessible via the Internet. Thus, since a user is not able to determine a priori that a Web site is handicapped accessible, i.e. 4Q BobbyTM approved, it is much more likely that a user will retrieve a Web page that is not handicapped accessible.
Moreover, if a handicapped person wishes to perform a search of Internet Web pages for a particular subject of interest, the results of the search will contain a majority of, 45 if not all, handicapped inaccessible Web sites and only a minority of handicapped accessible Web determine which of the Web sites returned in the search results are handicapped accessible. Therefore, it would be beneficial to have apparatus and methods for filtering content based on whether or 50 not the content is accessible to persons having special needs.
SUMMARY OF THE INVENTION
The present invention provides apparatus and methods for 55 filtering content based on the accessibility of the content to a user. The apparatus and method make use of an evaluation tool that evaluates requested content for accessibility to users having special needs, such as handicapped or disabled users. The results of the evaluation are then compared to a 60 user's designation of a required accessibility level to determine if the content is accessible to the user. If the results of the evaluation indicate that the content meets the user's required accessibility level, the content is provided to the user. If the evaluation indicates that the content does not 65 meet the user's required accessibility level, the content is not provided to the user or a not accessible indicator is appended
to the content. In a further embodiment, the content may be modified to make the content accessible to the user.
BRIEF DESCRIPTION OF THE DRAWINGS
The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
FIG. 1A is an exemplary block diagram illustrating a network data processing system according to one embodiment of the present invention;
FIG. IB is an exemplary block diagram illustrating a network data processing system according to two other alternative embodiments of the present invention;
FIG. 2 is an exemplary block diagram illustrating a server device according to one embodiment of the present invention;
FIG. 3 is an exemplary block diagram illustrating a client device according to one embodiment of the present invention;
FIG. 4 is an exemplary block diagram illustrating data flow according to one embodiment of the present invention;
FIG. 5 is an exemplary block diagram illustrating an interaction of components of the elements shown in FIG. 4;
FIG. 6 is a flowchart outlining an exemplary operation of the present invention; and
FIG. 7 is a flowchart outlining an exemplary operation of the present invention according to an alternative embodiment.
DETAILED DESCRIPTION OF THE
PREFERRED EMBODIMENT
With reference now to the figures, FIG. 1A depicts a pictorial representation of a network of data processing systems in which the present invention may be implemented. Network data processing system 100 is a network of computers in which the present invention may be implemented. Network data processing system 100 contains a network 102, which is the medium used to provide communications links between various devices and computers connected together within network data processing system 100. Network 102 may include connections, such as wire, wireless communication links, or fiber optic cables.
In the depicted example, content provider servers 108-112 are connected to network 102 along with personalized accessibility evaluation provider 106. In addition, client device 104 is also connected to network 102. The client device 104 may be, for example, a personal computer, network computer, personal digital assistant, portable computing device, or the like. In the depicted example, content provider servers 108-112 provide data, such as files, web pages, operating system images, and applications to client device 104. Client device 104 is a client to content provider servers 108-112. Network data processing system 100 may include additional servers, clients, service providers and other devices not shown.
In the depicted example, network data processing system 100 is the Internet with network 102 representing a worldwide collection of networks and gateways that use the TCP/IP suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host comput3
ers, consisting of thousands of commercial, government, educational and other computer systems that route data and messages. Of course, network data processing system 100 also may be implemented as a number of different types of networks, such as for example, an intranet, a local area 5 network (LAN), or a wide area network (WAN). FIG. 1A is intended as an example, and not as an architectural limitation for the present invention.
The personalized accessibility evaluation provider 106, as will be described in more detail hereafter, provides a filtering l o mechanism by which content received from content provider servers 108-112 is checked for objectionable content before being forwarded to client device 104. The personalized accessibility evaluation provider 106 may be implemented, for example, on a proxy server to which the client device 104 15 is logged on (as shown), may be implemented as an application on the client device 104, or as a network-resident service implemented by a proxy that resides on a service provider's premises through which content provider servers 108-112 are accessed, or the like. 20
In the case of the personalized accessibility evaluation provider 106 being implemented on the client device 104, the personalized accessibility evaluation provider 106 may be a stand alone software application, a portion of a web browser application, a plug-in to a web browser application, 25 or the like. For purposes of illustration, it will be assumed in the following description that personalized accessibility evaluation provider 106 is implemented on a proxy server. The proxy server is present between the client device and the content provider server, and may either be a proxy server 30 accessed by the client device or may be a reverse proxy of a content provider through which access to the content provider servers 108-112 is obtained, as shown in FIG. IB.
Proxy servers are generally known in the art and are available for common Internet services. For example, an 35 HTTP proxy is used for Web access, and an SMTP proxy is used for e-mail. Proxy servers generally employ network address translation (NAT), which presents one organizationwide IP address to the Internet. The proxy server funnels all user requests to the Internet and fans responses back out to 40 the appropriate users. Proxies may also cache Web pages, so that the next request can be obtained locally.
Referring to FIG. 2, a block diagram of a data processing system that may be implemented as a server, such as content provider server 108-112 or a proxy server on which the 45 personalized accessibility evaluation provider 106 may be resident, is depicted in accordance with a preferred embodiment of the present invention. Data processing system 200 may be a symmetric multiprocessor (SMP) system including a plurality of processors 202 and 204 connected to system 50 bus 206. Alternatively, a single processor system may be employed. Also connected to system bus 206 is memory controller/cache 208, which provides an interface to local memory 209. I/O bus bridge 210 is connected to system bus 206 and provides an interface to I/O bus 212. Memory 55 controller/cache 208 and I/O bus bridge 210 may be integrated as depicted.
Peripheral component interconnect (PCI) bus bridge 214 connected to I/O bus 212 provides an interface to PCI local bus 216. A number of modems may be connected to PCI bus 60 216. Typical PCI bus implementations will support four PCI expansion slots or add-in connectors. Communications links to network computers 108-112 in FIGS. 1A and IB may be provided through modem 218 and network adapter 220 connected to PCI local bus 216 through add-in boards. 65
Additional PCI bus bridges 222 and 224 provide interfaces for additional PCI buses 226 and 228, from which
4
additional modems or network adapters may be supported. In this manner, data processing system 200 allows connections to multiple network computers. A memory-mapped graphics adapter 230 and hard disk 232 may also be connected to I/O bus 212 as depicted, either directly or indirectly.
Those of ordinary skill in the art will appreciate that the hardware depicted in FIG. 2 may vary. For example, other peripheral devices, such as optical disk drives and the like, also may be used in addition to or in place of the hardware depicted. The depicted example is not meant to imply architectural limitations with respect to the present invention.
The data processing system depicted in FIG. 2 may be, for example, an IBM RISC/System 6000 system, a product of International Business Machines Corporation in Armonk, N.Y., running the Advanced Interactive Executive (AIX) operating system.
With reference now to FIG. 3, a block diagram illustrating a data processing system is depicted in which the present invention may be implemented. Data processing system 300 is an example of a client computer, such as client device 104 in FIGS. 1A and IB. Data processing system 300 employs a peripheral component interconnect (PCI) local bus architecture. Although the depicted example employs a PCI bus, other bus architectures such as Accelerated Graphics Port (AGP) and Industry Standard Architecture (ISA) may be used. Processor 302 and main memory 304 are connected to PCI local bus 306 through PCI bridge 308. PCI bridge 308 also may include an integrated memory controller and cache memory for processor 302. Additional connections to PCI local bus 306 may be made through direct component interconnection or through add-in boards. In the depicted example, local area network (LAN) adapter 310, SCSI host bus adapter 312, and expansion bus interface 314 are connected to PCI local bus 306 by direct component connection. In contrast, audio adapter 316, graphics adapter 318, and audio/video adapter 319 are connected to PCI local bus 306 by add-in boards inserted into expansion slots.
Expansion bus interface 314 provides a connection for a keyboard and mouse adapter 320, modem 322, and additional memory 324. Small computer system interface (SCSI) host bus adapter 312 provides a connection for hard disk drive 326, tape drive 328, and CD-ROM drive 330. Typical PCI local bus implementations will support three or four PCI expansion slots or add-in connectors.
An operating system runs on processor 302 and is used to coordinate and provide control of various components within data processing system 300 in FIG. 3. The operating system may be a commercially available operating system, such as Windows 2000, which is available from Microsoft Corporation. An object oriented programming system such as Java may run in conjunction with the operating system and provide calls to the operating system from Java programs or applications executing on data processing system 300. "Java" is a trademark of Sun Microsystems, Inc. Instructions for the operating system, the object-oriented operating system, and applications or programs are located on storage devices, such as hard disk drive 326, and may be loaded into main memory 304 for execution by processor 302.
Those of ordinary skill in the art will appreciate that the hardware in FIG. 3 may vary depending on the implementation. Other internal hardware or peripheral devices, such as flash ROM (or equivalent nonvolatile memory) or optical disk drives and the like, may be used in addition to or in
5
place of the hardware depicted in FIG. 3. Also, the processes of the present invention may be applied to a multiprocessor data processing system.
As another example, data processing system 300 may be a stand-alone system configured to be bootable without 5 relying on some type of network communication interface, whether or not data processing system 300 comprises some type of network communication interface. As a further example, data processing system 300 may be a Personal Digital Assistant (PDA) device, which is configured with ROM and/or flash ROM in order to provide non-volatile memory for storing operating system files and/or usergenerated data.
The depicted example in FIG. 3 and above-described 15 examples are not meant to imply architectural limitations. For example, data processing system 300 also may be a notebook computer or hand held computer in addition to taking the form of a PDA. Data processing system 300 also may be a kiosk or a Web appliance. 20
FIG. 4 is an exemplary block diagram illustrating the data flow according to the present invention. As shown in FIG. 4, the client device 410 sends content requests to the personalized accessibility evaluation provider 420 and receives filtered content from the personalized accessibility evalua- 25 tion provider 420. The term "content" as it is used in the present description is intended to mean any electronic information that is retrievable and able to be provided to a client device. Thus, "content" may be Web pages, including Web pages generated using Hypertext Markup Language 30 (HTML), Wireless Markup Language (WML), and the like, applications, images, and the like. In the following exemplary embodiments, "content" will be assumed to be HTML Web pages. The term "filtered content" as it is used herein, is intended to mean content that has been evaluated for 35 accessibility and compared to user designated accessibility requirements.
The personalized accessibility evaluation provider 420 forwards content requests from the client device 410 to the 4Q content provider servers 440-460 and receives requested content from the content provider servers 440-460. The personalized accessibility evaluation provider 420 further retrieves user profile information from user profile database 430 for use in filtering the requested content received from 45 the content provider servers 440-460, as described hereafter.
With the present invention, the client device 410 issues requests for content to one or more of content provider servers 440-460 in a manner generally known in the art. For example, a user of client device 410 may enter a Uniform 50 Resource Locator (URL) associated with a Web page resident on content provider server 440 into a web browser application on the client device 410. The entry of the URL into the web browser application causes the Web browser application to transmit a request for the Web page associated 55 with the URL via a communication link to the personalized accessibility evaluation provider 420. The content request from the client device 410 is routed through the personalized accessibility evaluation provider 420 which acts as a proxy server for the client device 410. 60
Alternatively, the client device 410 may enter a search request using a search engine, such as those provided by YahooTM or HotBotTM. The search engine may be resident on the personalized accessibility evaluation provider 420 and may search content providers that have been registered with 65 or tracked by the search engine. Searching the content providers may include, for example, searching a locally
6
stored version of the content provider web page, searching a locally stored version of an abstract of the content provider, or the like.
In either case, content is obtained, either from the content provider server 440-460 or from a locally stored copy of the content from the content provider server 440-460. The personalized accessibility evaluation provider 420 then evaluates the obtained content to determine a level of accessibility for the content.
The level of accessibility may be defined, for example, as a level of accessibility for handicapped individuals or individuals having special accessibility needs. For example, the level of accessibility may be an organization of guidelines, such as those defined by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium standards body, as described in the Web Content Accessibility Guidelines, Techniques for WCAG, available from www.w3c.org, and which are hereby incorporated by reference. Thus, for example, the accessibility levels may be one or more organizations of the following current WAI guidelines:
(1) Provide alternative text for all images;
(2) Provide alternative text for each APPLET;
(3) Provide alternative content for each OBJECT;
(4) Provide alternative text for all image-type buttons in forms;
(5) If the submit button is used as an image map, use separate buttons for each active region;
(6) ALT text >150 characters, consider providing a separate description;
(7) Have a descriptive (D) link in addition to LONGDESC;
(8) If an image conveys important information beyond what is in its alternative text, provide an extended description;
(9) All audio files have transcripts;
(10) ASCII art is avoided;
(11) Provide a synchronized textual transcript for the audio in videos;
(12) Provide text links for all server-side image map hotspots;
(13) Provide both a description and a synchronized caption for video information;
(14) Provide visual notification and transcripts of sounds that are played automatically;
(15) Avoid Client-side image map {0} that does not contain a link {1} elsewhere on the page;
(16) If a color is used to convey information, make sure the information is also represented another way;
(17) Foreground and background colors contrast sufficiently with each other;
(18) Where it's possible to mark up content (for example mathematical equations) instead of using images, use a markup language (such as MathML);
(19) Make sure the document validates to formal published grammars;
(20) Style sheets should be used to control layout and presentation wherever possible;
(21) Use relative sizing and positioning (% values) rather than absolute (pixels);
(22) Make sure that headings are nested properly;
(23) Use header elements in the proper sequence and not for bold text;
(24) Only use list elements for actual lists, not formatting;
(25) Use Q and BLOCKQUOTE for quotations, not indentation;
(26) Mark up quotations with the Q and BLOCKQUOTE elements;
(27) Identify any changes in the document's language;
(28) Use the ABBR and ACRONYM elements to denote and expand abbreviations and acronyms;
(29) Identify the language of the text;
(30) For tables not used for layout (for example, a spreadsheet), identify headers for the table rows and columns; 5
(31) If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship;
(32) Avoid using tables to format text documents in columns unless the table can be linearized; 10
(33) If a table is used for layout only, do not use structural markup to achieve formatting effects;
(34) Provide a summary and caption for tables;
(35) Provide abbreviations for long row or column labels;
(36) Be sure pages are readable and usable if style sheets are 15 ignored;
(37) Ensure that descriptions of dynamic content are updated with changes in content;
(38) Each FRAME must reference an HTML file;
(39) Provide alternative content for each SCRIPT that con- 20 veys important information or functionality;
(40) Make sure pages are still usable if programmatic objects do not function;
(41) Make sure event handlers do not require use of a mouse;
(42) Provide a NOFRAMES section when using FRAMEs; 25
(43) Ensure that dynamic content is accessible or provides an alternate presentation or page;
(44) Make sure programmatic objects do not cause the screen to flicker;
(45) Avoid blinking text created with the BLINK element; 30
(46) Avoid scrolling text created with the MARQUEE element;
(47) Avoid using movement in images where possible;
(48) Do not cause a page to refresh automatically;
(49) Do not cause a page to redirect to a new URL; 35
(50) Provide accessible alternatives to the information in scripts, applets, or objects;
(51) Use a client-side image map instead of a server-side image map;
(52) Ensure that all elements that have their own interface 40 are operable without a mouse;
(53) Specify a logical tab order among form controls, links and objects;
(54) Consider adding keyboard shortcuts to frequently used links;
(55) Consider furnishing keyboard shortcuts for form elements;
(56) Do not use pop-up windows or change the active window unless the user is aware this is happening;
(57) If scripts create pop-up windows or change the active window, ensure that the user is aware this is happening;
(58) Ensure that labels of all form controls are placed immediately before the control;
(59) Provided a linear text alternative for tables that lay out 55 content in parallel, word-wrapped columns;
(60) Include default, place-holding characters in edit boxes and text areas;
(61) Separate adjacent links with more than whitespace;
(62) Use the latest technology specification available when- 60 ever possible;
(63) Avoid use of deprecated language features if possible;
(64) Allow users to customize their experience of the web page;
(65) If a page accessible cannot be made accessible, con- 65 struct an alternate accessible version;
(66) Give each frame a title;
(67) Add a description to a frame if the TITLE does not describe its contents;
(68) Group long lists of selections into a hierarchy;
(69) Group related form controls and label each group;
(70) Group related elements when possible;
(71) Explicitly associate form controls and their labels with the LABEL element;
(72) Create link phrases that make sense when read out of context;
(73) Add a descriptive title to links when needed;
(74) Do not use the same link phrase more than once when the links point to different URLs;
(75) Use metadata to add computer-understandable information about the page;
(76) Offer a site map or table of contents, and provide a description of the general layout of the site, the access features used, and how to use them;
(77) Use a clear, consistent navigation structure;
(78) Offer navigation bars for easy access to the navigation structure;
(79) Group related links;
(80) Provide a link at the beginning of a group of related links to bypass the group;
(81) Offer different types of searches for different skill levels and preferences;
(82) Place distinguishing information at the beginning of headings, paragraphs, lists, etc.;
(83) Provide metadata that identifies this document's location in a collection;
(84) If ASCII art is present, provide a means to skip over it;
(85) Use the simplest and most straight-forward language that is possible;
(86) Use icons or graphics (with accessible alternatives) to facilitate comprehension of the page; and
(87) Create a consistent style of presentation between pages. The mechanism for evaluating the accessibility level of
the received content may be, for example, a device that analyzes the content for the occurrence, or lack thereof, of accessibility criteria generated based on, for example, the above accessibility guidelines. For example, the mechanism for evaluating the accessibility level may be the BobbyTM software available from CAST at www.cast.org/bobby/.
BobbyTM is a Web-based tool that analyzes Web pages for their accessibility to people with disabilities. CAST offers BobbyTM as a free public service. With the BobbyTM software, a user may enter a Uniform Resource Locator (URL) of a Web page that BobbyTM is to analyze. The BobbyTM software evaluates the Web page associated with the entered URL and generates a report indicating any accessibility and browser compatibility errors found in the Web page. Once a Web page meets accessibility requirements for at least one accessibility level, the Web page is allowed to display a BobbyTM approved symbol. Of course, other content evaluation devices, either now known or later developed, may be used without departing from the spirit and scope of the present invention.
Thus, the content received by the personalized accessibility evaluation provider 420 is evaluated using an evaluation tool to determine a level of accessibility. The evaluation may make use of a tool, such as BobbyTM to perform the evaluation of the received content. The result of the evaluation of the received content is an indicator of an accessibility level of the received content which is then compared to a required accessibility level identified in a user profile retrieved by the personalized accessibility evaluation provider 420 from a user profile database 430.
For example, a disabled user may register with the personalized accessibility evaluation provider 420 and establish
|
