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

RE: Should Datepickers be treated as a Modal Dialog?

From: SALES, TERRY LYNN <TERRYLYNN.SALES@cbp.dhs.gov>
Date: Thu, 16 Nov 2017 14:21:18 +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: <CD6739563257E640956C81ABE78DD091F53BD59D@D2ASEPREA011>
My first question would be do the date pickers in question provide an alternate entry form?  If the date can be typed in, and is keyboard accessible for that function, is the calendar portion required to be accessible?

Terry Lynn (TL) Sales
Section 508 and UI Tester
DHS/CBP/OIT/CSPD
571-468-5271 Desk
703-945-2777 B'Berry

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:21:54 UTC

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