RE: Should Datepickers be treated as a Modal Dialog?

This is good to know (deleted content from ARIA practices). Thanks for sharing!

Best,
Poornima.

From: Matt King [mailto:a11ythinker@gmail.com]
Sent: Thursday, November 16, 2017 8:37 PM
To: 'Bolena, Zachary' <Zachary.Bolena@Schwab.com>; Subramanian, Poornima (PCL) <psubramanian@hagroup.com>; w3c-wai-ig@w3.org
Cc: 'W3C WAI Interest Group' <w3c-wai-ig@w3.org>
Subject: RE: Should Datepickers be treated as a Modal Dialog?

When making a11y decisions, please don't' reference content deleted from the ARIA authoring Practices.

The file in our repo at:
https://rawgit.com/w3c/aria-practices/master/aria-practices-DeletedSectionsArchive.html
contains content that was deleted and we kept it on hand only because it contains some useful fragments. But, that file contains content that has significant errors and some guidance that is not recognized as good practice by the ARIA working group.

We will eventually remove that file completely.

Thanks,
Matt King

From: Bolena, Zachary [mailto:Zachary.Bolena@Schwab.com]
Sent: Thursday, November 16, 2017 6:59 AM
To: Subramanian, Poornima (PCL) <psubramanian@hagroup.com<mailto:psubramanian@hagroup.com>>; w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Cc: W3C WAI Interest Group <w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>>
Subject: RE: Should Datepickers be treated as a Modal Dialog?

Hi Poornima,

I guess this would be considered a dialog non-modal as it is described as:

"A dialog is a small application window that sits above the application and is designed to interrupt the current processing of an application in order to prompt the user to enter information or require a response"

(https://rawgit.com/w3c/aria-practices/master/aria-practices-DeletedSectionsArchive.html#dialog_nonmodal)

The content addressing the dialog non-modal on this page seems to be similar to a modal dialog except hiding the background content does not seem to be addressed. Perhaps it does not apply so it was not addressed.

I see that this is currently being drafted so I will address it on the  github thread (Draft Dialog (non-Modal) design pattern  #59<https://github.com/w3c/aria-practices/issues/59>).


Thank you,
Zach Bolena

From: Subramanian, Poornima (PCL) [mailto:psubramanian@hagroup.com]
Sent: Thursday, November 16, 2017 8:43 AM
To: Bolena, Zachary; w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Cc: W3C WAI Interest Group
Subject: RE: Should Datepickers be treated as a Modal Dialog?

If you see the ARIA patterns, there are two different widgets: Modal dialog, Non-modal dialog.

http://www.w3.org/TR/wai-aria-practices-1.1/#dialog_nonmodal<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_TR_wai-2Daria-2Dpractices-2D1.1_-23dialog-5Fnonmodal&d=DwMFAg&c=Ezx-H5PgBrUMEEvxgJuTQRYrd-4D8l8I18qkZZzJQbo&r=gfIcoH9AOzWzA6hyAsR7zIoc3exAOSNc5ep43e0oO18&m=BaS3kals7uI8wt0Kh0Pde80KOpxORN8_EcM0J_0XsRU&s=3Dsk3rIIMEu7Qz_Drh3iUtM-EF9fRmv_S9zVHebSOD8&e=>

This Non-modal dialog does not fade out the background content (contrast to what modal does). I think it is of no harm to code the date pickers as non-modal dialog where the keyboard navigation is possible to the background content while date picker is open.

It is important that the date picker widget is easy to interpret announcing its Name, Role, State, Value along with instructions.

Best,
Poornima.

From: Bolena, Zachary [mailto:Zachary.Bolena@Schwab.com]
Sent: Thursday, November 16, 2017 8:55 AM
To: w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Cc: W3C WAI Interest Group <w3c-wai-ig@w3.org<mailto: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.


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.symanteccloud.com&d=DwMFAg&c=Ezx-H5PgBrUMEEvxgJuTQRYrd-4D8l8I18qkZZzJQbo&r=gfIcoH9AOzWzA6hyAsR7zIoc3exAOSNc5ep43e0oO18&m=BaS3kals7uI8wt0Kh0Pde80KOpxORN8_EcM0J_0XsRU&s=0Tcv9nJYPoHsYU4va3TLgc8ltvmOinFdRZLcKhK-T64&e=>
______________________________________________________________________
The information contained in this email and any attachment may be confidential and/or legally privileged and has been sent for the sole use of the intended recipient. If you are not an intended recipient, you are not authorized to review, use, disclose or copy any of its contents. If you have received this email in error please reply to the sender and destroy all copies of the message. Thank you.

To the extent that the matters contained in this email relate to services being provided by Princess Cruises and/or Holland America Line (together "HA Group") to Carnival Australia/P&O Cruises Australia, HA Group is providing these services under the terms of a Services Agreement between HA Group and Carnival Australia.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________