This post originated from an RSS feed registered with .NET Buzz
by Scott Hanselman.
Original Post: Avalon, Automation and Accessibility
Feed Title: Scott Hanselman's ComputerZen.com
Feed URL: http://radio-weblogs.com/0106747/rss.xml
Feed Description: Scott Hanselman's ComputerZen.com is a .NET/WebServices/XML Weblog. I offer details of obscurities (internals of ASP.NET, WebServices, XML, etc) and best practices from real world scenarios.
Here's a great scoop by a Microsoft Insider from the bowels of the Comments on a recent
post:
We aren't advertising it as such, but, [Avalon] UI Automation is the replacement
for MSAA and it is being built by the Accessibility team at MS. When we talked
to developers such as screen reader manufacturers and application developers about
MSAA it was clear that MSAA could not stretch to cover the demands of computing that
the coming decade will bring. Especially for people with disabilities.
Given the value that testers derived from MSAA, we decided we would get far
better penetration of the accessibility framework if we achieved it through
promoting the benefit to developers, testers and the companies they work
for. That way everyone benefits.
This is welcome news, and I must say “big ups“ to MSFT for making it happen.
[Unrelated aside: I sat next to a Manager-Type for Word once on a plane and I
complemented him on Microsoft's respect for other cultures, specfically for resonable
support for EthiopianAmharic in
Word XP. Turns out the powers that be didn't REALLY care as much as he did,
but he sold the idea in another way - as a complete Unicode-ization of Word to simplify
deployment and testing. Getting all these other languages to work was a welcome
side effect, as he was an Asian language fan. He did have to make some special
effort for Amharic,
and to that I say Amessagganalehugn. Apparently this isn't
an unusual way to get things done at MSFT. I respect the effort. ]
This new UI Automation Framework will surely make testing easier, but it also opens
the door to completely new paradigms for blind or “differently-able“ individuals.
Rather than writing entirely new Shells from scratch, or (gasp) messing with Windows
Classes and walking handles(which is the Win32 equivalent to screen scraping) we'll
be able to concern ourselves with the behavior or anima of
the UI, and not it's implementation.
As an interesting side note, I've worked on Accessible websites that have to comply
with the Federal Section 508 Accessiblity standards.
It's hard. Navigating Windows itself, especially when an unexpected dialog box
or error occurs is HARD. Now, I've got bad eyes. ~20/1600 to be exact,
but I also run 19“ LCDs with 18pt Fonts and Large Icons. But, if you REALLY
want to understand what being blind and computing is like try this:
Download a trial
copy of JAWS for Windows.
It is a screen synthesizer and it will read whatever's on your screen. It's
VERY souped-up compared to the built-in Windows Accessbility Narrator.
Now, turn off the lights, close the windows, doors, and unplug your monitor.
Then, use your now-headless computer for a day.
I did this while doing some research on creating a accessible website for the blind
for a large eastern bank. Surfing the net was obnoxious. So few sites
follow the guidelines outline in the Web Accessibility
Inititive and others.
Try running your own blog or website through Bobby (a
Web accessibility software tool) and see what it says.
Previous Topic
