Well, I just got back from SCUBA diving in Fiji where my wife and I went diving on the Fiji Agressor II. Here is the captain's log. The vis. was great at 125 feet. We had a great shark dive at Nagali Pass where I saw the biggest green moray. Initially I thought the reef moved but it turned out to be a moray with a diameter of about 18 inches and 8-10 feet long. It felt like flashbacks of The Deep.
On Tuesday this week I was interviewed on the the Computer America Talk Show and spoke on DHTML accessibility. For those that are interested here is the link:
Craig Crossman was a great host.
Accessibility Strategy and Architecture
schwer 120000D6E4 612 Visits
schwer 120000D6E4 610 Visits
Like many in the industry I have been reviewing and helping to define what accessibility features appear in UI Automation (UIA). UIA addresses a number of gaps in Microsoft Active Accessibility (MSAA).
At a high level some of these gaps are:
Microsoft's challenge will be to move people to it. Today, accessible Windows applications are based on the use of a plethora of API and reverse engineering mechanisms. These consist of: MSAA; Proprietary COM access to an applications Document Object Model (MS Office, Corel, IE, etc.); the Java Access Bridge; graphics engine hooking to access to text, carets, and selected information, and more.
In the near term Microsoft is working to map MSAA to a single UIA API layer but due to problems with MSAA's specification implementations may vary and the end result will be that this will be unrealistic. At the moment access to UIA by an assistive technology is through managed code. This requires AT vendors to rewrite from scratch or integrate a managed extension to their assistive technology. Access to legacy applications by an assistive technology will result in a performance hit. ATs will have to communicate from a managed application across boundaries to legacy applications resulting in slower access. A positive step forward would be for Microsoft to release an unmanaged client API version for assistive technologies. Like any mature company Microsoft will be forced to support their legacy infrastructure or risk breaking the accessibility of existing applications. In short, this will be a long process.
While a significant step forward for Microsoft, there are some rather significant gaps in UIA that need to be addressed:
One of the things that would have given UIA more traction would have been to get UIA into the open source community to get more backing as a cross-platform accessibility API where we would focus on a Linux implementation. I had originally suggested this to their director earlier this year and he expressed interest resulting in this public commitment. Unfortunately, industry has yet to see a license agreement to review after months of waiting and we were forced to move on to alternatives.[Read More]