- From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- Date: Fri, 29 Apr 2011 15:07:03 +0100
- To: Henri Sivonen <hsivonen@iki.fi>
- Cc: Steve Faulkner <faulkner.steve@gmail.com>, Jonas Sicking <jonas@sicking.cc>, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Michael Cooper <cooper@w3.org>, Joseph Scheuhammer <clown@alum.mit.edu>, W3C WAI-XTECH <wai-xtech@w3.org>, HTMLwg <public-html@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, David Bolter <dbolter@mozilla.com>
On Fri, Apr 29, 2011 at 2:24 PM, Henri Sivonen <hsivonen@iki.fi> wrote: > Is there no way to connect a "description" semantic to a structured > subtree in the existing accessibility APIs? Where possible, that's already required: http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_relations See especially this note: "Note that aria-describedby may reference structured or interactive information where users would want to be able to navigate to different sections of content. User agents MAY provide a way for the user to navigate to structured information referenced by aria-describedby and assistive technology SHOULD provide such a method." Judging from the mapping document, MSAA+UI Express and Apple Accessibility API do not support a described-by relationship between two objects in the accessibility tree, and so here the mapping falls back to filling a string property only. I don't have the expertise to say whether this correctly reflects underlying limitations in the APIs. I can't see any non-custom way to express meta-hierarchical relationships between objects in the Apple Accessibility API. -- Benjamin Hawkes-Lewis
Received on Friday, 29 April 2011 14:15:20 UTC