W3C home > Mailing lists > Public > wai-xtech@w3.org > September 2012

RE: role=dialog and nested rich HTML content

From: Schnabel, Stefan <stefan.schnabel@sap.com>
Date: Thu, 6 Sep 2012 12:56:28 +0200
To: Steve Faulkner <faulkner.steve@gmail.com>, W3C WAI-XTECH <wai-xtech@w3.org>
CC: Alexander Surkov <surkov.alexander@gmail.com>, James Teh <jamie@nvaccess.org>
Message-ID: <8EA44C66E2911C4AB21558F4720695DC60CA60E6E5@DEWDFECCR01.wdf.sap.corp>

I understand from your post that the automatic mode switch from "application mode" to "document mode" is buggy with AT. Can you give examples?

I've heard that many users are used to do mode switching manually for they don't trust the automatic switching mechanisms or do not know them.
What happens/changes if you explicitly switch modes in AT (as possible e.g. in NVDA, Jaws) by respective command?

Best Regards

-----Original Message-----
From: Steve Faulkner [mailto:faulkner.steve@gmail.com] 
Sent: Donnerstag, 6. September 2012 12:26
Cc: Alexander Surkov; James Teh
Subject: role=dialog and nested rich HTML content

HI all,

I have been testing the ARIA role=dialog and have been finding poor
support in AT for rich content inside dialog containers.
Many use for dialog like structures in modern web pages include rich
web content that should be interacted with using the virtual cursor.
I thought that nesting a container with role=document would provide an
indiectaion to AT that they should switch to virtual cursor mode, but
have found that this is not handled well.

example code:

<div role="dialog>

<div role="document">
HTML content


Any ideas on why or how this can be remedied?

with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
HTML5: Techniques for providing useful text alternatives -
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Thursday, 6 September 2012 10:57:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:51:46 UTC