- From: Henri Sivonen <hsivonen@iki.fi>
- Date: Fri, 29 Apr 2011 16:24:34 +0300
- To: Steve Faulkner <faulkner.steve@gmail.com>
- Cc: 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, 2011-04-22 at 20:22 +0100, Steve Faulkner wrote: > Hi again, it may also be useful to review the aria implementation > guide: > > 5.6.1. Name and Description > http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_nd What's the rationale for prescribing implementation that loses the structure of the content pointed to by aria-describedby and flattens it into a string? Does a "description" have to be crammed into an accessibility API that only takes a plain text string? Is there no way to connect a "description" semantic to a structured subtree in the existing accessibility APIs? -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/
Received on Friday, 29 April 2011 13:25:11 UTC