- From: Jonas Sicking <jonas@sicking.cc>
- Date: Fri, 22 Apr 2011 15:08:11 -0700
- To: Steve Faulkner <faulkner.steve@gmail.com>
- 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 22, 2011 at 2:25 PM, Steve Faulkner <faulkner.steve@gmail.com> wrote: > Hi Jonas > >> I wrote a patch in about 30 minutes to do so. > > Interesting, so how is this behaviour exposed to users? > > Feedback received from the NVDA developers was that they want UI in the browser. Like I said, this was a patch to the code that exposes content to AT users. It would be equally trivial to add a context menu item for all users (similar to what I believe opera does for their @longdesc implementation). In fact, we could even display a context menu item for each link if there are multiple as aria-describedby allows pointing to multiple elements, many of which could be links. > How does it affect current expected behaviour for describedby? I'm not sure what you mean by "expected"? (I seem to have different expectations of how aria-describedby should be exposed to users than many others on this list). But the patch does not affect how we expose describedby otherwise. Given that I don't know our accessibility almost at all, I don't know off the top of my head know the code that exposes aria-describedby to users. However given that it's software, anything is possible :). But I'd have to work on it a bit longer than 30 minutes to get something working. I'm willing to do such work, but this working group also has to be willing to stop thinking outside the box of "what browsers/AT vendors do today". / Jonas
Received on Friday, 22 April 2011 22:10:51 UTC