universal web design

Jump to 	Content  Jump to Navigation  Jump to Section Info
A survey of Web accessibility and usability

Accessible [Google] Search Engine

Search engines are likely the most powerful tool on the Web, but, as touched on in the Diagnostics section, popular Web search sites rank near the bottom in the accessibility tests. Several guest speakers to our Comp 190 class echoed this and demonstrated using JAWS how slow and aggravating it is to try to analyze search results and find useful information from currently available search engines. Visually, sites such as Google and Yahoo suffice, but their content arrangement and extraneous information wreak havoc on screen readers.

Complaints about Google

In response to these complaints, I set out to design a new prototype version of Google and propose some ideas that can be abstracted for search engines in general that may enhance the user experience for visually impaired individuals.

Disclaimer: This simulation does not reflect the opinions of Google.com or any of its affiliates. The graphics and search results used in this demo are for demonstration purposes only and belong to Google.com.

Proposed Solutions

Full redesign with XHTML/CSS. The first step was to re-engineer the existing Google site, give it a slightly improved appearance, and code the entire layout of the search results screen in compliant XHTML and CSS.

User preferences and data hiding. The first of two key features is customizeable user preferences. By using some relatively CSS conventions, the redesigned site can hide content -- both visually and for screen readers -- and thus allow the user to pick what he/she wants to view on the screen. On one extreme, the user can choose to display all the existing content that Google currently displays on its results screen. On the opposite extreme, one can remove everything but the primary link to the search result and the query box.

Embedded "jump links" to facilitate transportation and orientation. The other key feature, as illustrated in the redesigned Google schematic (Powerpoint), are the hidden links and targets that I embedded in the page to help the visually impaired user orient himself and move around on the page. I placed three embedded bookmarks on the page (shown as the red circles) -- one at the query box, one at the top of the search results, and one at the preferences panel. Then, at strategic locations, I placed hidden "jump links" (shown in green) in the form of 1 x 1 transparent GIFs (so the sighted user cannot see them, but the screen reader picks them up and reads the associated <alt> text):

The Prototype: Accessi-Google

So, without further ado, check out the Accessi-Google demo, which is hosted by Ibiblio. The data hiding is accomplished using very simple scripting, which, if coupled with cookies, would allow the user to set his own preferences and persistently use the accessible version of Google in the manner he so chooses.

Benefits, Tradeoffs, Conclusions

It is hard to understand the benefits of this re-engineered search engine without actually exploring it using a screen-reader. If anything, the site is more visually appealing, and the customizeable preferences make for a better user experience, regardless of disabilities. Other benefits include the following:

In order to pull this off, I had to throw in some items -- namely, the hidden "jump links" -- that some may consider junk that perverts the structural integrity of the HTML document. Again, as with the other prototypes, the site when viewed in non-compliant browsers like Netscape 4- reverts to a black-and-white page that does not look as good as the original Google site -- a fact that would likely prevent Google from adopting such changes for fear of losing those users.

Overall, I think this search engine design is a winner, but there is an inherent flaw. I pulled it off in a day and did not have time to consult with users who are visually impaired. My ideas came from a sound set of assumptions and observations, but this does not mean the result will be useful or easy to understand. By now VI users are probably quite used to navigating treacherous search engines, so convincing them to learn a new system -- even if it were designed with their needs in mind -- would be difficult. Nevertheless, I plan to continue working on it and submitting the proposal to a contact the Comp 190 professor has at Google, who may interested in my work.

Validate this page for CSS compliance  Validate this page for XHTML compliance  Validate this page for Section 504 compliance

In this Section

Demo of my new version of the Google search engine, demonstrating the various design features that may significantly improve the experience of the user that is trying to process search results using a screen-reader.

Project Vitals

Author: Greg Lanier
This site was originally created as a course project for Comp190 Enabling Technologies, given by Professor Gary Bishop at the University of North Carolina at Chapel Hill.
UNC : course : prof

Switch: v1 : v2

© 2003 Use but don't abuse