- From: Kalpeshkumar Jain <kalpeshjain89@gmail.com>
- Date: Wed, 7 Jul 2021 15:53:07 +0530
- To: Jan Hellbusch <jan@hellbusch.de>
- Cc: w3c-wai-ig@w3.org
- Message-ID: <CACPo1Zj2Cz5XoFXvVmRu_L3iHL7PuWk_kz5MxAaZTZrOkYbjhQ@mail.gmail.com>
Thanks for the response. Its clear to me upon reading it again :). I guess I got lost in the verbosity of the content. Please consider this thread as resolved and closed. Appreciate your help and thanks again. Thanks, Kalpeshkumar Jain On Wed, 7 Jul, 2021, 12:57 Jan Hellbusch, <jan@hellbusch.de> wrote: > > The definition of changes of context > > <https://www.w3.org/WAI/WCAG21/Understanding/on-input.html#dfn-changes > > -of-context> states 'moving focus to a different component' is one of > the examples of change of context. > > > > Does that mean opening a modal window is a change of context? > > If yes then how do we comply with 3.2.2 (informing the user ahead of > time)? > > No, since activating a button to open a modal dialog window is not input. > > If you are using a button to open the dialog window, you can use <button > aria-haspopup="dialog">do something</button> to indicate to a screen reader > user that there will be an overlay. > > Typical applicability of 3.2.2 would be an input field or selecting an > option in a <select> when keyboard focus changes during input/selection. > > Jan > > > -- > Hellbusch Accessibility Consulting > Chemnitzer Str. 50, 44139 Dortmund > Tel.: +49 (231) 58054815 Mobil: +49 (163) 3369925 > -- > Accessibility-Consulting seit 2000 > > Leistungen, Bücher, Artikel: https://www.barrierefreies-webdesign.de > Blog: https://www.hellbusch.de > > > > >
Received on Wednesday, 7 July 2021 10:28:09 UTC