Consider this article your one-stop shop for all things IAccessible. Below is a summary of the most important topics under my accessibility category.
New to Accessibility? So was I three years ago. Get caught-up by reading my MSDN whitepaper on Testing for Accessibility. Also, remember that Accessibility isn’t a feature. Just like localization, globalization, security, performance, and so forth, it is a standard that must be addressed.
MSAA / IAccessible
If you want your feature to be accessible, you’ll need to implement IAccessible.
Must Read: Explanation of each of the IAccessible Properties
Must Read: Which Control-Types Support Which Properties
Must Read: How To Really Support MSAA Names
Commonly Asked Questions regarding Invisible, Offscreen and Unavailable States
Which Properties Must Be Localized
Must Read: MSAA / IAccessible Samples
Fiona, one of the devs on my team VSCore, has put together a really nice sample on how to implement IAccessible for a Custom Push Button http://blogs.msdn.com/saraford/archive/2004/06/18/159730.aspx
Must Read: MSAA Testing Tools
Have you ever used AccExplorer or Inspect and wondered whether the information presented was correct? Have you ever wanted to know which controls really need Names, Keyboard Shortcuts, Descriptions, and so forth? It’s time to MsaaVerify! MsaaVerify will verify 9 Microsoft Active Accessibility properties for 10 Microsoft Active Accessibility Role types.
Updated! How To Really Do Screen Reader Testing.
In the past, I’ve focused on testing MSAA Properties. Now we’re ready to take screen reading testing to the next level by adding Events into the algorithm. It is not only essential that a control support the correct MSAA properties, but it is also essential that the control fire the right event for these properties.
Updated! Role-Based Testing Strategy for Verifying Microsoft Active Accessibility
This paper contains of my thoughts regarding MSAA testing. Consider this the grand specification for MsaaVerify. Provided i had enough time, this is everything i wanted to implement in MsaaVerify. Hopefully someone out there will find this useful and can put it to use.
As demo’ed at CSUN, these macros allow users to tweak the Visual Studio .NET 2003 IDE by easily increasing and decreasing font size, toggling colors in the editor to pure black on white (or vice versa), and maximizing tool windows.
Bugs to look out for
A listing of unpopular bugs given to me by an Assistive Technology Vendor
What the High Underline Letters Checkbox Actually Does
Why Radio Buttons don’t resize
Channel 9 Video
My Channel 9 Interview on Accessibility and Visual Studio
more at http://blogs.msdn.com/saraford/archive/2004/04/30/123993.aspx
Presenting at CSUN
Blogging and Accessibility Presentation