Re: First draft of aria-modal in ARIA 1.1 ED. (Was: aria-modal (Was: @inert and @aria-inert for disambiguating modal states))

I think I'm good with requirements on the whole however I would change a
wording slightly.

"until the modal dialog loses focus" I'm not sure whether we should
describe the "dialog focus" term, I meant to specify that it means the
focus is at the element or inside its subtree.

"When a modal element is displayed, assistive technologies should navigate
to the element unless focus has explicitly been set elsewhere." AT should
always follow focus, so if modal dialog is displayed but the focus has not
been moved into the dialog then it doesn't seem reasonable to move the user
forcibly to the dialog.

"Assistive technologies may limit navigation to the modal element's
contents." could be clarified so that it's advised to limit navigation to
the modal element within its context document. So if modal dialog is
displayed in a tab document then the user shouldn't be restricted in
switching to another tab.

"When a modal element is displayed, authors must ensure the interface can
be controlled using only decendants of the modal element. In other words,
if a modal dialog has a close button, the button should be a descendant of
the dialog." I'm not sure I see the need of it, is it about that aria-owns
is not applicable to build the dialogs? If so then it makes sense to state
that explicitly.

Thanks.
Alexander.


On Mon, Nov 10, 2014 at 5:15 AM, James Craig <jcraig@apple.com> wrote:

> I've added aria-modal to the ARIA 1.1 editor's draft:
> http://rawgit.com/w3c/aria/master/aria/aria.html#aria-modal
> aria-modal (property)§
>
> Indicates whether an element is modal when displayed.
>
> The aria-modal attribute is used to indicate that the presence of a
> "modal" element precludes usage of other content on the page. For example,
> when a modal dialog is displayed, it is expected that the user's
> interaction is limited to the contents of the dialog, until the modal
> dialog loses focus or is no longer displayed.
>
> When a modal element is displayed, assistive technologies should navigate
> to the element unless focus has explicitly been set elsewhere. Assistive
> technologies may limit navigation to the modal element's contents. If
> focus moves to an element outside the modal element, assistive technologies should
> not limit navigation to to the modal element.
>
> When a modal element is displayed, authors must ensure the interface can
> be controlled using only decendants of the modal element. In other words,
> if a modal dialog has a close button, the button should be a descendant of
> the dialog. When a modal element is displayed, authors should mark all
> other contents as inert (such as "inert subtrees" in HTML) if the ability
> to do so exists in the host language.
>