W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2014

Re: Dialog behaviour and screen readers

From: Bryan Garaventa <bryan.garaventa@whatsock.com>
Date: Fri, 28 Mar 2014 14:03:03 -0700
Message-ID: <9F5C9659B90D404E895EEDC0F9AE584D@WAMPAS>
To: <w3c-wai-ig@w3.org>
If I may ask, can you tell me which issues you've noticed with the modal at
http://whatsock.com/tsg/Coding%20Arena/Modals/Modal%20(Internal%20Content)/demo.htm
 I'm always looking to improve the widgets.

----- Original Message ----- 
From: "Ian Sharpe" <themanxsharpy@gmail.com>
To: "'WAI Interest Group'" <w3c-wai-ig@w3.org>
Sent: Friday, March 28, 2014 1:40 PM
Subject: Dialog behaviour and screen readers


> Hi
>
> Dialogs have always been, and continue to be, an issue when using a screen
> reader, with many implementations across the wide variety of widget 
> toolkits
> of varying quality.
>
> The best implementation I've seen so far is the Jquery UI dialog at:
>
> https://jqueryui.com/dialog/#modal
>
> This works very well for the most part, reading the dialog text and only
> allowing navigation within the dialog using NVDA with FF. However, if I
> interrupt speech before NVDA has read all the text, or if I want to listen
> to the content again once the content has been read, there doesn't seem to
> be any way for me to access the content again, short of cancelling the
> dialog and triggering it again that is.
>
> Is there a reference implementation for this problem anywhere?
>
> Is it simply a case of adding tabindex="0" to the title and content of the
> dialog sited above to enable the content to be accessed again?
>
> Cheers
> Ian
>
>
> 
Received on Friday, 28 March 2014 21:03:28 UTC

This archive was generated by hypermail 2.3.1 : Friday, 28 March 2014 21:03:28 UTC