Re: Should Datepickers be treated as a Modal Dialog?

It is my understanding that if there is an area for the user to input the
date, that the calendar would not need to be acessible. Although, going the
extra mile to making it accessible would be ideal.

On Thu, Nov 16, 2017 at 6:31 AM SALES, TERRY LYNN <
TERRYLYNN.SALES@cbp.dhs.gov> wrote:

> 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.
>
>
>