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

RE: Should Datepickers be treated as a Modal Dialog?

From: Jim Homme <jhomme@benderconsult.com>
Date: Thu, 16 Nov 2017 14:21:47 +0000
To: "Bolena, Zachary" <Zachary.Bolena@Schwab.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
CC: W3C WAI Interest Group <w3c-wai-ig@w3.org>
Message-ID: <MWHPR0601MB3785345289B76CBB7970479DDB2E0@MWHPR0601MB3785.namprd06.prod.outlook.com>
It may be this way because the screen reader user has to do nothing special to see the surrounding content, and any instructions in the date picker.



Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,

From: Bolena, Zachary [mailto:Zachary.Bolena@Schwab.com]
Sent: Thursday, November 16, 2017 8:55 AM
To: w3c-wai-ig@w3.org
Cc: W3C WAI Interest Group <w3c-wai-ig@w3.org>
Subject: Should Datepickers be treated as a Modal Dialog?

Hello All,

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?

Thank you,
Zachary Bolena
Senior Manager of Accessibility for User Experience
Charles Schwab & Co., Inc.

“Great innovators fall in love with the problem, not the solution.”

NOTICE: All email sent to or from the Charles Schwab corporate email system is subject to archiving, monitoring and/or review by Schwab personnel.
Received on Thursday, 16 November 2017 14:22:13 UTC

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