As I covered in Web Accessibility 101: Assistive Technologies, the text browser Lynx is particularly useful for stripping down a web site to its raw, GUI-less nature.

Why is this useful? Well, someone with a motor skill disability that prevents them from effectively using a mouse can navigate a website in Lynx solely by keyboard. Also, blind web surfers using certain refreshable Braille displays can use Lynx as their browser. There are others – disabled or not – who may have connection or hardware limitations that make graphical web browsing slow or just impractical.

Lynx strips out all graphical elements as well as JavaScript, leaving just the raw text, links and alt tags. As such, depending on the complexity or manner by which a site was constructed, a user surfing the web this way may be able to get around, or may be hopelessly barred from getting where they are trying to go.

I recently checked out my site in Lynx and was pleased to see that, overall, one can get around effectively via the arrow keys. I can’t take too much credit for that, given I’m using WordPress as the guts of this blog, but it’s at least another area of accessibility where I can set my mind at ease.

If you’re a Mac user like me, you can download Lynx right from Apple’s website. Once you install it, you can fire up Terminal, type in “lynx” and surf the web.

Otherwise, check out the Lynx site for more information.

Tags: apple, assistive technology, braille, internet software consortium, lynx, terminal

Next week, the Paciello Group — an organization that works with all manner of entities from governmental to commercial to ensure their technologies are accessible for all people — will be presenting a webinar on Flash and accessibility on Tuesday, March 31st.

There is also one on Wednesday, April 1 about PDF forms and conforming to WCAG 2.0 standards.

Both will take place at 11 a.m. Central time.

Adobe has more details in an entry on their accessibility blog entitled “Accessibility webinars on Flash and PDF.”

Related Links:

• The Paciello Group and Adobe Present WCAG 2.0 Accessibility Webinars for Flash and PDF
• Adobe’s Accessibility blog

Tags: Acrobat, adobe, flash, paciello group, PDF, WCAG

This past week, Apple released Safari 4.0 beta. With touted speed enhancements that put it ahead of the competition, the beta reportedly has even pushed Safari’s market share over the 10% hump.

As touched on in “The iPhone and Accessibility“, Apple openly demonstrates a commitment to accessibility in its products. How much they succeed will always be open for debate, but it’s certain that they treat the subject seriously.

Even though alphabetizing has more to do with it than anything else, front and center on their 150 Features page for Safari 4 is Accessibility.

New to Safari 4, according to Apple, is support of Accessible Rich Internet Applications, or ARIA. On the heels of the Web Content Accessibility Guidelines 2.0 becoming a Recommendation this past December, just last week WAI-ARIA was published as a Last Call Working Draft. WAI-ARIA takes web accessibility considerations to the next level, helping establish guidelines for dynamic content using more advanced technologies like Ajax and JavaScript. ARIA opens the door for utilizing such coding to interact with assistive technologies.

Also improved with Safari’s new beta are greater Zoom features — combining keyboard commands, Multi-Touch, and a Zoom button that can easily be added to the toolbar. The user can zoom in and out while text and imagery scale accordingly and keep the layout intact.

These, paired with Apple’s already-integrated VoiceOver screen reading feature, keyboard shortcuts, and the ability to create or download custom stylesheets for desired viewing states, make Safari 4.0 — while certainly not a perfect accessibility experience just yet — appear to be progressing respectably.

Tags: accessible rich internet applications, apple, aria, multi-touch, os x, safari, safari 4 beta, VoiceOver, W3C, wai-aria, web browsers, zoom

WebAIM recently posted results to a survey of screen reader users, conducted from December 2008 – January 2009. In Survey of Preferences of Screen Readers Users, they share very interesting results regarding the usage of screen reader technology in web navigating.

Some of the initial findings perhaps aren’t surprising. Of the 1121 participants, the vast majority (nearly 90%) use screen reader technology all of the time and because of a disability. 96% of them cited visual impairment, in most cases outright blindness.

The breakdown of screen reader usage is insightful:

• JAWS – 74%
• Windows Eyes – 23%
• NVDA – 8%
• VoiceOver – 6%

(WebAIM points out that percentages often don’t add up to 100% due to rounding, and in this case also because of the possibility of usage of multiple products)

Most of the participants utilize desktop PCs (78%), with just over half use screen readers on a laptop. Those using mobile technology with screen readers made up a much smaller 12%.

Lastly (for this post), web browser usage breaks down as follows:

• Internet Explorer 7 – 68%
• Firefox – 39%
• Internet Explorer 6 – 33%
• Safari – 6%
• Internet Explorer 8 – 2%

Amongst the nearly 7% of participants who used screen readers though were not disabled (some for evaluation purposes), Firefox usage was twice as prevalent. It was also noted that the question was not worded “primary” browser, just browser usage, and that IE8 and Safari were, essentially, write-in votes.

While none of this is exact science, the findings are all-around very interesting and offer a glimpse into the methods and practices of screen reader users.

I’ll close for now, having focused on the software and hardware findings. There are a slew of results covering browsing tendencies, from home page navigation to access keys to Flash and imagery frustrations/ease of use.

All in all, these results are well worth combing through and considering when evaluating accessibility, particularly as it relates to the visually impaired.

Tags: blindness, jaws, NVDA, screen readers, survey, visually impaired, VoiceOver, WebAIM, Windows Eyes

Admittedly, I have been and always will be an Apple devotee. With that disclaimer aside, during one of my many ventures through the Web looking for interesting web accessibility topics, I came across extensive coverage of the topic of accessibility on Apple’s website.

To cover the highlights briefly, Apple claims the iPhone has these accessibility features:

For the Visually Impaired:

• Physical buttons for commands such as sleep, ringer and home
• Zoom ability for viewing content
• Font size increasing for Mail
• Alert and ringtone customization based on audio, visual or vibration

For the Hearing Impaired:

• Support for open and closed captioning, as well as subtitles
• Using Safari, ability to use web-based instant messaging services such as Meebo
• SMS texting
• Headset options including hearing-aid induction ear loop
• Visual Voicemail feature
• TTY support (with a separate iPhone TTY Adapter)

They similarly point out some of these features — like the tactile buttons, voice dialing, and assignable ringtones — as being accessible to those with physical disabilities as well.

Furthermore, AT&T has a Text Accessibility Plan for iPhone, which offers unlimited messaging and data usage and pay-per-use voice and Visual Voicemail.

There are conflicting views, not surprisingly, on how successful Apple’s accessibility efforts with the iPhone are. Some laud Apple and AT&T for considering those with disabilities and providing growing options. Others feel that these features aren’t enough.

For example, Touchscreens, from the inability to feel buttons to supplying multiple levels of menuing, provide significant problems for those unable to see. See TechNewsWorld article “Is Technology Accessibility the New Green?.”

Again, like website accessibility, it is not always practical and feasible to make something for absolute everybody? The challenge is continuing to push the technology envelope in making cool and useful new innovations, while doing as much as possible to enable those with disabilities to enjoy the experience as well.

Does the iPhone have further to go? The answer seems to be yes, but I would say that Apple at least appears to take the subject of accessibility seriously, and all signs point to them doing better with future releases.

A sampling of differing viewpoints in the blogging world:

• Forget the iPhone: accessibility trumps trendiness from Computing Unplugged Magazine
• iPhone Accessibility: But Not For Me from ShellyBlog
• AT&T Intros iPhone Text Accessibility Plan; Phone Still Not Accessible to Blind Customers from Disability Nation

Tags: accessibility statement, apple, iphone, safari, sms, tactile buttons, text telephone, touchscreens, TTY, zoom