Re: JAWS behavior with the dialog role preventing access to dialog content

Hi James,

I never considered this as a bug (or harmful behaviour), as I've never seen
an example where document reading mode would be required. If it's a plain
alert, the user would expect the contents to be announced to them. If the
dialog contained form controls, then the user would be in interacting with
interface elements and not needing document mode. I don't have strong
opinions against the dialog being announced in document mode, but I've
never seen it as a problem.

Regards,

Gez



On 15 April 2013 21:31, James Craig <jcraig@apple.com> wrote:

> Freedom Scientific JAWS triggers "application mode" behavior when you use
> a simple dialog role, preventing access to any static content inside that
> dialog, such as a static table of results. The spec is pretty clear that
> this mode should be triggered when encountering the "application" role, but
> JAWS appears to be doing so implicitly on several of the other roles.
> Removing the dialog role causes the static content to become navigable
> again, but results in negative behavior for all screen readers (including
> JAWS) in that the user no longer knows this content is displayed in a
> dialog. Also, if a field is focused by default when the dialog is shown,
> the dialog label and description is not spoken.
>
> Do the rest of you agree that this is a "bug" or would you consider it
> outside the purview of W3C jurisdiction, since it's AT behavior rather than
> UA behavior? Do any of you know if Freedom Scientific is aware that this is
> potentially harmful behavior? Do any of you know workarounds to this
> problem?
>
> Thanks,
> James Craig
>
>
>


-- 
_____________________________
Supplement your vitamins
http://juicystudio.com
http://twitter.com/gezlemon