WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Time-out modal with alertdialog


From: Sean Keegan
Date: Jul 6, 2015 11:41PM

Hi Mike,

Yes, I agree that it is unlikely that the screen-reader user would be
working in the say-all mode for a web application. It's possible that the
individual could be rechecking the entire page via say-all, but I agree
with you that it would not be a common situation (it took me two days to
figure out how to replicate the situation). Unfortunately, this was
identified as an issue in an external review and is on a "must be
addressed" list.

I am going to try Bryan's suggestions to see if there is any effect on the
delay between when the event is triggered and when it is reported by the
screen-reader. Even though NVDA does report the time out event, there is
still a 40 second delay and I do think it may be something to keep in mind
when setting the time period by which a user can provide a response.

Take care,

> From: "Moore,Michael (HHSC)" < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Mon, 6 Jul 2015 13:33:45 +0000
> Subject: Re: [WebAIM] Time-out modal with alertdialog
> This is very likely because both screen readers are reading from a virtual
> buffer when in say all mode. The screen reader is going to read to the end
> of the buffer before adding any more content. The good news is that I have
> not observed any actual screen reader users working with a web application
> in say-all mode.
> Mike Moore
> Accessibility Coordinator
> Texas Health and Human Services Commission
> Civil Rights Office
> (512) 438-3431 (Office)
> (512) 574-0091 (Cell)