Warning for Dialogues, not just new windows.

[alastc]

This is an email from Luella Benedetto to the public comments list:

---

Technique G201: Giving users advanced warning when opening a new window

Please stress the importance of this not just for new windows but the opening of dialogue boxes.

A screen reader user would have any even more difficult time perceiving a new dialogue box is open than a new tab or window. Some browsers announce when a new tab is opened but do not do so when a dialogue opens.

With a new tab or window, an experienced screen reader user might try a keyboard shortcut to switch back to the referring link, and figure out what happened. But a dialogue box would need to be closed entirely to return to the underlying web page.. Notification that a dialogue will open would be very helpful if not essential.

[detlevhfischer]

I don't think a general requirement of a warning before opening a dialog would be a useful addition to G201. A dialog should be implemented correctly, either as native element or with proper aria markup, which in both cases should ensure that it is announced when opened. Failure to do so would not fall under this Technique. I guess it is better to avoid mixing two different things (leaving the UA browser contex,t and opening content on the same page).

[mbgower]

Official Working Group response

First, note that this requirement is about changing the setting of a control, not about pages that open as a result of someone clicking a link or button. This is explicitly stated in a note in the Understanding document:

This Success Criterion covers changes in context due to changing the setting of a control. Clicking on links or buttons is activating a control, not changing the setting of that control.

Dialogues are typically triggered by button activation, not by changing the setting of a control.

Second, it's important to emphasize that G201 is an advisory technique for 3.2.2 On Input. So G201 is not "essential". The generic text which precedes all advisory techniques listed in Understanding documents notes:

Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.

Finally, as pointed out in prior comments, a dialogue is not a window. If implemented properly, the dialogue is announced, and the user is returned to their starting position after the dialogue is closed. It is a very established convention. So, much of the rationale for G201, which concerns letting the user understand how to return to their prior activity, does not apply.

Keeping those qualifications in mind, we do not believe it is appropriate to include dialogue boxes in G201 information. However, if you have an interaction where changing the setting of a control results in a dialogue opening, you must advise the user of the dynamic behaviour in advance to meet 3.2.2 On Input. Especially if user testing shows an improvement in experience, providing the information that a dialogue will open as part of that advance notice seems reasonable.

[bruce-usab]

Discussed on call 12-6, no concerns with draft response.

[mbgower]

Based on a working group review, the draft response has been updated to the official response.