W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2017

RE: Should Date pickers be treated as a Modal Dialog?

From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
Date: Thu, 16 Nov 2017 17:49:04 +0000
To: "Lovely, Brian" <Brian.Lovely@capitalone.com>, Jonathan Avila <jon.avila@levelaccess.com>, W3C WAI Interest Group <w3c-wai-ig@w3.org>
Message-ID: <MWHPR03MB31989A5AB91CFB04C5117DD6F22E0@MWHPR03MB3198.namprd03.prod.outlook.com>
"Every example of an "accessible" date picker I have looked at online does not treat the datepicker as a modal dialog. Is this because it is not a seen as a modal dialog but rather a specific task based widget? Should the datepicker container <div> take on the same characteristics as a modal such as hiding the background from screen readers when the datepicker calendar is active?"

Actually this accessible date picker is treated as a modal dialog, functionally in any rate for screen reader users. Press Escape to close the datepicker without saving.
http://whatsock.com/tsg/Coding%20Arena/ARIA%20Date%20Pickers/ARIA%20Date%20Picker%20(with%20Disabled%20Date%20Ranges%20plus%20Condense%20Year)/demo.htm

All of these datepicker variations are treated like this.

It is not necessary to hide the background functionality from screen reader users when the functionality does this automatically.



Bryan Garaventa
Accessibility Fellow
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com
415.624.2709 (o)
www.LevelAccess.com

From: Lovely, Brian [mailto:Brian.Lovely@capitalone.com]
Sent: Thursday, November 16, 2017 7:21 AM
To: Jonathan Avila <jon.avila@levelaccess.com>; W3C WAI Interest Group <w3c-wai-ig@w3.org>
Subject: RE: Should Datepickers be treated as a Modal Dialog?

If the datepicker is in the form of a modal (a widget with its own close button, and presumably atop a semi-opaque overlay) that temporarily supersedes all other activity, then it should trap focus like a modal. Otherwise, a user could accidently navigate away from the widget and become confused.

I don't see it as any different from a modal containing a small form. I would treat it as a modal dialog, including the role of dialog on the container.

Every example of an "accessible" date picker I have looked at online does not treat the datepicker as a modal dialog. Is this because it is not a seen as a modal dialog but rather a specific task based widget? Should the datepicker container <div> take on the same characteristics as a modal such as hiding the background from screen readers when the datepicker calendar is active?


________________________________

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Received on Thursday, 16 November 2017 17:49:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 6 December 2017 16:04:47 UTC