Talk:IAccessible2

This is supposed to be part of a new category of Accessibility APIs. Then in "List of screen readers", or in pages about particular applications, compatibility with a given API can be specified, and readers can visit the page to learn about that particular API. I've also created an article for "Microsoft UI Automation" as information about UIA really doesn't belong in "Microsoft Active Accessibility". Snce, as far as I understand, it's a completely new API with a different licence and intended to be cross-platform, people wouldn't necessarily search for MSAA to find out about it. If we'd prefer one big fat article, a possible alternative would be to create a single article called "Accessibility API" (in the "Assistive Technology" category) and discuss the various minor/new APIs (IAccessible2, UIA, Java Access Bridge, possibly the proposed QT Bridge) under headings there, with links out to AT-SPI and MSAA. Would that be preferable? I didn't go that route initially because I can't think of much useful to say about the APIs as a group. Benjamin Hawkes-Lewis 15:52, 6 February 2007 (UTC)


 * Moving improper source reference here incase someone else can make good use of it. NipokNek 13:32, 7 February 2007 (UTC)


 * Here's another reference moved off the Article. NipokNek 14:39, 7 February 2007 (UTC)

This all seems fine, except for this reformulation: "While Project Missouri was started when the State of Massachusetts, in the process of adopting the OpenDocument format for its public records, required that the format be made accessible, IAccessible2 also includes accessibility for dynamic web applications". The reference cited for discusses web application accessibility, but doesn't discuss Project Missouri's origins or ODF at all (which was the point of the reference to Schwerdtfeger). Also it makes it sound a bit like that's all IAccessible2 is for, which isn't the case. What I was trying to highlight was that ODF and web access were two special foci. I probably didn't phrase it clearly the first time. Following the article, I've elaborated a bit on how IAccessible2 helps dynamic web acccessibility.Benjamin Hawkes-Lewis 19:23, 7 February 2007 (UTC)


 * I'll try and help out as I can as far as making it all nice and pretty, but I'm no expert on this subject. Feel free to revert anything I may do that changes the proper meaning of the text. NipokNek 21:05, 7 February 2007 (UTC)

I'm tempted to add the following to the end of goals, however in discussions I think others felt this was not sufficiently important to vendors or users. "A potential benefit of the close match of functionality between IAccessible2 on Windows and ST-API on Linux is a reduction in the burden Assistive Technology vendors will have in making their offerings available on both platforms." SteveLee 08:49, 14 February 2007 (UTC)