IAccessible2 – What’s next?
Over the last three years I lead a team developing the IAccessible2 interface, defining how screen readers and a11y enabled applications interact with each other.
IAccessible2 is often called IA2. IA2 extends MSAA allowing additional capability such as full access to information about a table or the offset of the caret in a text field. This work was done as an IBM employee under the direction of Rich Schwerdtfeger, Distinguished Engineer, IBM Software Group Accessibility Architect/Strategist. My IA2 work included:
- Chairing the regularly held meetings
- Responding to issues on the IA2 list
- Updating the spec’s commentary to remove ambiguities
- Providing implementation guidance to AT and application developers
- Acting as liaison between the AT and application developers
On January 21 I was part of a large resource action at IBM, suspending further IA2 development.
I believe the IA2 work is important. The advanced accessibility provided by IBM Lotus Symphony and Mozilla’s Firefox proves the benefits of IA2. I think the work should continue. But how?
I would like to continue the IA2 work – provided an organization commits to, and funds, the IA2 effort.
I’m asking for your feedback.
Thanks, Pete
I’m sorry, Pete. This is extremely unfortunate, and it is a big setback.
I think that we could keep IA2 by continuing the momentum and have other apps adopt it. The best case for this is Webkit, if Webkit stays committed to IA2, than we have a very powerful web a11y story.
My 2c
Very sad to here that Pete, for you and Open a11y. I’ll pass the word on. Thanks for all your hard work making IA2 as solid and important as it is. Hope you can find support soon