Web Site Accessibility Blog

Why don’t more people use assistive technology in their online research? Just because someone does not have a disability, does that mean that they cannot benefit from using assistive technology? Assistive technology, in my opinion, has the ability to help everyone.

The FireFox Browser has a free screen reader plug-in, Adobe now has screen reading technology, Jaws is somewhat affordable, but not without need. However, Jaws does offer a 20-minute demo version.

Educational research on reading comprehension research shows that people learn through a combination of three sensory factors: visual, auditory and kinesthetic. People tend to learn faster when exposed to more than a single factor, thus the curse of endless PowerPoint Presentations. Ideally, I suppose PowerPoint’s can assist learning when they are not combining charts and graphs with a droning speaker, but that’s just my opinion. People learn better when they can use all three sensory abilities, and the retention increases when they do. All people rely on these, and people largely rely on one more than the others, but can benefit from all.

So, why do people who do not need assistive technology take advantage of the assistance that is available? I wondered this the other day as I attempted to sit and read an on-line book. It was one of the most difficult experiences I have ever had, I couldn’t get past the first page. I can sit and read a book for hours, but yet I get distracted by the slightest agitation when reading online. I even realized that I really don’t fully read web pages – I skim.

However, the experience of reading the printed page is just that – an experience. The preparation and time spent reading a printed text is not the same as the reading online. For one, it is much easier for me to read a book than to read the same text online. The contrast of the text on the page is much easier to see, as well as the “horizontal� aspect of turning pages. People can see when the page ends in a book, as opposed to a web page.

So why do so many tests (Second Language education) (6th Grade reading assignment), seem to indicate the comprehension from using the web is better than the standard printed page? The results of both seem to indicate the hypertext environment, the use of images and multimedia as factors in better comprehension from web/computer learning.

In a Multimedia learning study, there is surprising results comparing reading combined with other auditory or sensory features.
When compared with the learning performance of the control group, the people in the different groups always demonstrated more learning:

• Hearing spoken text and looking at graphics – 91% more learning,
• Looking at graphics alone – 63% more,
• Reading printed text plus looking at graphics – 56% more,
• Listening to spoken text, reading text, and looking at graphics – 46% more,
• Hearing spoken text plus reading printed text – 32% more,
• Reading printed text alone – 12% more,
• Hearing spoken text alone – 7% more.

So, from looking at these results, we can see that websites can be powerful tools if they combine graphics, text and auditory assistance. People can rely on those additional factors which help them learn, but also learn from other factors, such as layout, deduction and reinforcement.

What I find interesting is that the group exposed to the spoken text and graphics had a significantly higher retention rate (91%) than those reading the text and seeing the same graphics (46%).

I think it is pretty obvious that anyone can benefit from assistive technology. Being aware of what it provides and sites can be improved to take advantage of these technologies can only help to provide a better experience for all users. Seemingly, integrating additional multimedia could also improve the sales and lead rate of a website – couldn’t it?

So, I’m going back to read this online book later today, and I’m going to use the Firefox plug in to speak the text. It’s not an official experiment or study, but I’ll let you know how it goes . . .

The Web Standards Project (WaSP) has formed the WaSP Accessibility Task Force, announced June 23rd, 2005. The goal of the Task Force is to work with accessibility organizations and software vendors to promote Web accessibility. The focus will be working to assist product manufacturers to improve standards within their products and to promote a better understanding of Web accessibility among designers and developers.

This is a great step, as many software developers must have a better understanding of the impact accessible software and Web sites can have on the Web population. Increasing the use among all users allows people to flourish in their talents, research and growth. Both Microsoft and IBM have major statements of accessibility promotion on their sites, it would be nice to see other developers take the same route, and I wish this new Task Force the best of luck.

Text Cloner Pro from Premiere Assistive Technology will be going on sale later this month, as an alternative to expensive, bundled solutions. Text Cloner is a high-speed and high detailed scanner that allows documents to be quickly scanned into a computer for screen readers to give access to low-vision users.

The high speed mode is designed to find only text and scan it quickly. This mode is especially helpful for students, researchers and those who need to review pages of documents.

A test of the Text Cloner software using a low-end Dell computer running Window-Eyes software resulted in scanning and recognition of five pages a minute with 99% accuracy. The affordability of this software and the integration will allow users to have fast access without high-priced bundled alternatives, as many assistive products tend to be. Text Cloner also avoids proprietary formats, allowing users to export text to Word or other word processing programs.

Text Cloner Pro will retail for $99.

Access for All.

On May 9th, 2005 Stevie Wonder presented two versions of his new music video, “So What the Fuss�. While a new video release is hardly headline material, this one was special. The video includes a second track which includes an audio description narrated by Busta Rhymes, for the purpose of blind or low vision people to experience a descriptive music video. Using a new video music technology, Stevie Wonder has made it possible for music fans “apply their vision to my video thanks to the descriptive technique� regardless of handicap.

In a March 2005 Associated Press news article, studies showed that 15 million Americans suffer from Macular Degeneration, a genetic defect that is the leading cause of blindness in the elderly. That number is expected to dramatically increase as the baby-boomer population ages. In addition to this startling story, there are numerous causes of vision-related disabilities. Many vision problems are not included in the typical blindness estimates as they are from other disorders, disease, and trauma or associated with other genetic causes.

Web site programmers, marketers and planners must take into account the growing awareness of these needs when they set out to plan their web sites. Simply designing a site to perform the basic functions will not suffice. Careful understanding of who will be using the site, how they operate and the necessary considerations could eliminate problems from the start and create goodwill for the company. While Web accessibility seems to be a polarizing issue, it is becoming one that will be inescapable as the internet community progresses. The majority of the US population is growing older, and recent studies have shown that failing eyesight is one of the foremost symptoms in the aging of our society.

Adhering to a few specific ideas, the question of creating an accessible website is very easy. When looking at the bigger picture, we can also see that this also fits into the realm of search engine optimization. Search engine spiders are really the most handicapped of all users that will visit your site. They cannot see images, JavaScript links are usually difficult or simply not seen, content is not viewed through a style sheet, and multimedia is not seen or heard. Colored graphs, charts and text are also not “seen�.

If your main goal is to expose your website to the greatest amount of people and have it understood by them, then the Accessibility Priority Checklist from the WAI should be your resource. The data contained in this check list could easily transform your web presence into one that is an all-inclusive platform for users. In addition, following the basic principles of this checklist can also assist your web site in gaining rankings from the search engines.

Search Engine Optimization is on the cusp of mainstream corporate thinking (i hope), and accessibility guidelines can also assist those efforts. Unique page titles, descriptive link text, page-specific metadata, sitemaps, and additional text and mark-up based elements that convey alternative information. In additional to basic optimization techniques, common sense marketing techniques also assist users to understand the information presented on a web site. Simple usability-based marketing techniques include; consistent navigation, consistent organization of information, arranging content for manageable readability, text equivalents for multimedia, common sense search functions for different skill levels, and obvious conversion points.

Sadly, however, many optimizers take advantage of elements that are used to make browsing easier for low-vision users and create a difficult experience. These elements are designed to enhance a person’s ability to learn more about the content of a page; instead they are treated to a barrage of repetitive keywords. Simply repeating keywords in links, titles and meta data in order to boost rankings can create a page that is difficult to navigate, harder to understand and almost impossible to use for users dependant upon assistive technology. Interestingly enough, these types of pages do not tend to rate highly with non-disabled users. Even users with full vision use the same elements of the page to determine value of the page. Making the effort to create well-written descriptions, links and titles can create a page that connects with the user because of the writing, but can also create additional relevance and allow access to all.

From a page design standpoint, avoid repetitive links, such as the “click here� link, which provides no information as to the destination page or content. Seeing that link outside of context provides no information. Avoid blinking text or page elements. Allow the users to control this, as repetitive blinking can potentially cause a seizure in some ailments. Also allow users to use the site and enter or control information with additional devices other than a mouse or with modified keyboards.

Planning accessibility makes sense and it not an unreasonable expectation. Careful implementation of accessibility guidelines simply creates a better website presence that can also enhance your standing in the search engines, as well as connect with the greatest majority of web users.

However, it is only video . . .

CNN is now allowing users to search video content on the web. The video content is limited-time only, as only recent segments are available. The service is pretty good and the video is very high quality.

However, there are some major accessibility hindrances. None of the video presented has subtitles, which are available when the video airs live on television. I thought the subtitles would be easily transferred to the web video, but apparently not.

To enable subtitles in Windows Media Player, if they are available: Play > Captions and Subtitles > On if Available. There are also many default languages available.

Another problem is the lack of accessibility and player controls when Microsoft’s Media Player is embedded into the page, rather than independent. WebAim studied the accessibility of multiple media players and found that embedded video has serious accessibility issues. When the player is embedded, controls are not accessible through a screen reader or through keyboard commands. When used as a stand-alone player, Windows Media Player 9 was the most accessible media player, yet all media players lose major accessibility functions when embedded.

Back to the main story, it would be nice to see subtitled content from CNN, especially knowing that these are previously broadcast stories and features. Hey – why not even present the content in an alternate text format? NPR allows users to order (what – order? – why?) transcripts of all of their broadcasts.

Adobe Reader 7 is a free download and is upgraded with a host of accessibility features. Unfortunately, they may be easily overlooked. There are few guides and even fewer people noticing the features the new Reader version brings. The features allow a greater majority of users to view documents regardless of vision or access.

The best place to start setting up Adobe Reader 7 for accessibility is the Help option in the toolbar. The last option starts the “Accessibility Setup Assistant”, which opens a help box to start options for viewing.

Screen readers are mainly used by blind or extreme low vision users, but not limited to vision accessibility. Many users with cognitive difficulties, such as Dyslexia, rely on screen readers to help them better follow the content on the screen.

Screen magnifiers are becoming more prevalent, as they not only raise the text size in web documents, but also in all applications on the computer. Screen magnifiers come in many styles, some are similar to magnifying glasses and highlight areas of content, and others “blow up” a section of the screen to the entire monitor viewing area.

Choosing all accessibility options is recommended for most users and Adobe will then move into installing the additional features.

Screen Reader
The voice option is not nearly as full featured as the JAWS, Window Eyes or other screen readers, but there are keyboard commands to provide real full page or read one page options. The Read Aloud Feature makes use of the Microsoft Sam voice, which can be quite monotonous. However, I was pleasantly surprised, as the voice contained many inflections at what seemed to be appropriate times.

It was actually easy to listen to after some minor tweaks to the pitch and rate. This can be done through the Edit > Preferences> Categories> Reading. The user also has the option to override the tagging commands contained within the document as well.

Contrast
In the Preferences> Categories> Accessibility is another great feature that increases accessibility for any user. The first allows the user to replace the document color format with a high-contrast format. Or, if the user already has a pre-defined windows color scheme to enhance readability, they can select that scheme, or set up a custom scheme. The art feature is particularly effective, as it can also render line art as a black and white image, allowing a high contrast image to be seen by anyone with color-blindness or who simply prefers to see graphs or art in a non-color format.

Reflow
Reflow is an important feature that allows readers who use large text options or screen magnifiers to view the document at a higher text size or increased document size, yet without the horizontal scrolling that is typical when increasing the document size.

Enabling reflow allows documents to be seen without horizontal scrolling. This is particularly effective for alternative devices accessing PDF’s, such as PDA’s, BlackBerry devices or Web-enabled phones.

By eliminating the horizontal scrolling, larger documents can be easily read by only a vertical scroll. The implications for this expand far beyond accessibility, as they can be used by all PDF users. There have been many times I have attempted to read PDF’s on a Palm device, only to get frustrated by getting lost in all of the cross-scrolling. Access Reflow in Adobe Reader 7 through View > Reflow. Or press Ctrl + 4.

Text Zoom
The default zoom can be set anywhere between 8% and 6400%. This is done in the Edit >Preferences > Page Display in the Magnification settings. Again, this is a feature that is helpful to any Adobe Reader user.

Multimedia
Adobe Reader 7 makes many strides in making accessibility options available, and the latest is through the multimedia options in Edit > Preferences > Multimedia. There are options to;

• show subtitles
• Play dubbed audio (when available)
• Show supplemental text captions when available
• Show audio description when available

Of course, these features are dependant upon creators to implement multimedia that includes these options.

Summary
There are many other features, such as Rich Text printing and pointers, and I am sure there will be many more to come. This is a big first step and the features are very comprehensive. As with any program, and especially in this case, users will be dependant upon the creators of the PDF documents to place accessibility features in these documents. Many of the features will help all users, not just those that rely on assistive technology.

The main issue will be getting those who create these documents to make them easier for all users, but also they need to be aware of the features that are available. Sadly, I believe that most users are not aware of the simplest things they can do to make a PDF more web-friendly and user friendly.

OK - I have to admit one of my passions is classic VW Beetles. I have to look when I hear that familiar engine hum, and if it is a convertable - ooooh! even better. I have a lot of fond childhood memories of VW Beetles. My dad had one, but he sold it when I was around 10. My dad had a friend, who owned one as well. His son and I were both the same age and went to school together. His dad was blind from diabetes and I remember when he made the news, as his hobby was repairing VW Beetle engines. He could disassemble, reassemble and install a complete Beetle engine completely by touch.

My current quest is looking for a good Beetle, preferrably a convertable, to restore, or just to have some fun. So, while looking around I found a Beetle available as part of a raffle to raise money for Multiple Sclerosis. MS is what has afflicted my father for over 20 years, so I am very supportive of many of the MS fundraisers. The actual car is a ‘58 hardtop, and raffle tickets are $15 a piece and purchased through paypal. I’m heading over to buy a couple of tickets. If someone else wins as a result of following my links, can I at least take it for a spin?

How To: PDF Accessibility
PDF’s are used in masses across the web. Many times, sites will rely on PDF’s to communicate information, which can be good for users to download and read later, however, PDF’s have major usability problems for web site marketing and accessibility.

Marketing Problem 1
The marketing problem comes from the PDF User Trap. PDF’s tend to rank very well in search engines. As a result, many users will click on the PDF, just as they click on a typical search engine result. The downside starts immediately when the user has to wait 20-30 seconds for the PDF reader to load and start-up. Delays when trying to find information can be priceless, as many users just don’t want to be bothered with waiting. However, when the PDF application starts, the user is locked in, they can’t stop it or leave.

Marketing Problem 2
The next problem comes as the user starts to look through the PDF. If it is interesting and has good content, there is no immediate way for the user to get to the company website. This is because very few PDF’s are built with hyperlinks embedded in the document. The hyperlink could be a very valuable resource for users to get to the main web site. Most users will not edit the URL field to get to the website, as they tend to rely on the back button. When a user hits the back button, they are now seeing the results page again, with your result back alongside competitive web sites. You had them at your site – but they couldn’t get any further. This is how the PDF becomes a user trap.


Accessibility Problems
For many users, PDF’s are much more frustrating than this. As PDF’s can also incorporate many images, they lack elements that web sites include, such as alt text for images, or document structure. Many screen readers are unable to handle PDF’s if they are not “properly� constructed and can cause frustration. For many users, the only option is to upgrade their assistive software, at a potential cost of hundreds of dollars.

Creating an accessible PDF is not difficult, and can be done by changing settings in the standard PDF creation, typically in Adobe. Creators can also test the accessibility of their PDF documents.

How to Create an Accessible PDF
The best means of creating an accessible PDF document is to start with a tagged source file. Starting with this, any device should be able to access the document. With accessibility, the benefit of creating accessible documents is that the documents are open to be read by multiple devices. PDA’s and phones are included in this list.

Fortunately, tagged document formats are included in Adobe programs and Microsoft Office. By “tagged,� the most basic explanation is that the document has some sort of underlying structure such as header information, text and graphic display commands and alt text. The best example of this is a web page, which has make-up language to position elements, designate text size, font style and more. To see the Tag structure of your document, select View > Navigation Tabs > Tags.

The tags create a logical order and structure to your document. Allowing the reader to follow the document as the author intended. A tagged format also allows a PDF document to be reflowed. Reflow is an important consideration for those who have to re-size the document for readability and for viewing on handheld devices. Reflow allows content to be structured for viewing without horizontal scrolling, allowing the user to only rely on the vertical scroll to see the content.

Microsoft documents embed this and will carry tagged data through PDF creation. Be sure this option is selected in the document settings set-up screen. Other programs, such as Quark, need to be converted to a PostScript file and then converting the PostScript file to a PDF in order to maintain the tagged format. Web Pages saved as a PDF must also select “Create PDF Tags� in the settings.

Tagged Documents
To create tags in current documents, it can be as easy as opening a PDF document. , From the toolbar in Acrobat 6, select Advanced > Accessibility > Add Tags to Document. Adobe will create the logical tag structure in the document, which will enable a logical flow of information and the reflow feature. You may want to review the tag structure for accuracy.

Acrobat will also allow you to check documents for accessibility compliance. There is a Full Check and a Quick Check. Don’t waste your time with the quick check, the full check doesn’t take much longer and you are better off knowing what to do to improve your documents. In the toolbar, select Accessibility > Full Check. The resulting checklist will notify you of improvements that can be made to allow for a more accessible document.

This not only allows you to better communicate with all of your web site users, but it also allows search engines to better search your documents for information and context. You can benefit, as always, by creating more accessibility options that help you market your website more effectively.

Next:

How To: Use Adobe Reader 7 accessibility options.

Eric Meyer is a person that I feel fortunate to have met. I have the privilege of speaking with him on, of all things, a panel about web standards and CSS. (I feel that he treats me with undying patience when I talk about CSS - Thanks, Eric.) Eric is one of those people that speak his mind with considerate honesty. You know what you are getting when you talk with him. The story of how we met and are speaking on the same panel is one that will someday become Internet lore.

We’ve debated a few times concerning accessibility and designers who force text size. The last report I had from Eric is that he was testing some CSS to see if users are always able to change text sizes.

I keep up with Eric’s blog and found an interesting entry yesterday. He relates an experience he had in a restaurant with someone who might be considered to have a disability. Considering my last post, and I felt this was worth posting and saying “thanks� to Eric for being one of the most straitforward people I know.

I’ve had a lot of great response to my recent article on Search Engine Watch – however, I have also had some constructive criticism of the title, “Don’t Disable Your Site for Handicapped Users.â€? Understandably, some do not like the use of the term “handicapped” or “disabled”, and view them as derogatory words.

I will take this opportunity to say that was not the original title of the article. The change was due to an editorial decision, which is common. Having studied Journalism in college, being involved in the industry and now writing frequent articles, editorial changes are the norm. Articles, stories, headlines are all subject to editorial changes. It is possible that the same article could be published under many titles, have slightly different content, and be different lengths. Basically, there are many reasons that editors change stories. Headlines are changed for a primary reason, and that is to get attention.

This leads me to my next thought. I am very familiar with the stigma of being called handicapped. I have lived with it for almost 30 years, since my father was stricken with Multiple Sclerosis. I have helped him when he was in a wheelchair, and I have been a witness to the callousness of people.

For those who may take offense at the title, I ask for your forgiveness and for liberty. There is a fine line that has to be walked in communicating the importance of this subject. While I and others do not intend to offend you, we also need to communicate the importance of accessibility to webmasters and designers who may have no familiarity or empathy. We need to communicate this in the clearest terms and descriptors as possible. If we change the language too much, the impact may be less or even worse, harder to understand.

Is there a middle ground? I’d like to know. As I talk with those who haven’t even given accessibility a second thought, it’s great to see the eureka moment when they get it. What is the best way to be understood, yet not offensive? Are we too wrapped up in terms and labels?