344539 - Use EMBEDS relation on top accessible object to point to content area

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Aaron Leventhal]

It's difficult for an AT to find the content area quickly. This will become a really big problem in Firefox 3 because of roc's ongoing work to remove HWNDs.

We should expose the content area for an nsRootAccessible via the EMBEDS relation.

Comment 1

[Aaron Leventhal]

Attachment: Use RELATION_EMBEDS to expose content area, which is more stable than using HWND window class

Roc, this will help alleviate my concern about the HWNDless future, by providing the screen reader an API they can start using to find the content area.

Comment 2

[Aaron Leventhal]

Attachment: Same patch but with a comment

Comment 3

[Robert O'Callahan (:roc) (email my personal email if necessary)]

How can we assume that there is only one content area? It would be easy to write a XUL application where this isn't true.

Comment 4

[Aaron Leventhal]

Good question. I realized that, and relations can support more than one target, but we don't support that yet. For now I want to get this working for the main case. I'd like to file a separate bug on handling multiple targets in a relation and fix this then.

Comment 5

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Comment on attachment 229140 [details] [diff] [review]
Same patch but with a comment

okay then...

Comment 6

[Mike Connor [:mconnor]]

Comment on attachment 229140 [details] [diff] [review]
Same patch but with a comment

a=mconnor on behalf of drivers for checkin by Wednesday, July 19th