Example Disclosure Navigation Menu incorrectly mentions the support of Esc key as required to meet 1.4.13

[OlivierNourry]

In this example: https://www.w3.org/TR/wai-aria-practices/examples/disclosure/disclosure-navigation.html
we can read:

If a dropdown is open and focus is inside the navigation region, pressing Esc will close the dropdown. (...) Implementing this Esc behavior is necessary to meet the WCAG 2.1 1.4.13: Content on Hover or Focus criterion.

Although I fully agree that supporting the Esc key is beneficial to users, I think its justification is incorrect here. SC 1.4.13 applies to content appearing on focus, not when it's displayed after user action (a press on the top-level menu button here). Besides, this also provides a compliant method to meet SC 1.4.13, since user can press the button again to dismiss the menu, considering the focus is still on the button -- which is the scope of this SC.

Again I'm totally in favor of promoting this practice, but I think it's problematic to incorrectly invoke WCAG to make them say what they don't, in this document more than anywhere else.

My suggestion: change the article to explain the added benefit, without presenting it as a requirement as per the WCAG; and in a second time, consider pushing this #1571 into a future version of the pattern, if it's deemed worthy of it.

[mcking65]

Discussed in March 22, 2022 meeting. The task force agrees that the escape key behavior is not required by WCAG. We will modify the text accordingly.