- From: James Nurthen <nurthen@adobe.com>
- Date: Tue, 18 Jun 2019 22:57:02 +0000
- To: "Gunderson, Jon R" <jongund@illinois.edu>, "public-aria-practices@w3.org" <public-aria-practices@w3.org>
- Message-ID: <1A43471F-10FB-4B0C-835A-B24A63791B20@adobe.com>
Deque’s example does not result in the keyboard appearing on iOS so IMO this would be ok. The Whatsock example does result in the keyboard appearing so IMO is not acceptable. Regards, James James Nurthen | Accessibility Engineer | Adobe | p. 415.832.2734 | c. 415.987.1918 | nurthen@adobe.com From: "Gunderson, Jon R" <jongund@illinois.edu> Date: Tuesday, June 18, 2019 at 3:15 PM To: "public-aria-practices@w3.org" <public-aria-practices@w3.org> Subject: Initial example of date picker using a menu button pattern Resent-From: <public-aria-practices@w3.org> Resent-Date: Tuesday, June 18, 2019 at 3:15 PM Link to datepicker menu button example: https://raw.githack.com/w3c/aria-practices/issue34-date-picker-examples/examples/datepicker/datepicker-menubutton.html Issues: 1. Other menu button date pickers move focus to the textbox instead of the button when a date is picked, we still want to stick with focus returning to the button? 2. Other examples: Deque: https://dequeuniversity.com/library/aria/date-pickers/sf-date-picker Whatsock (Bryan Garaventa): http://whatsock.com/tsg/Coding%20Arena/ARIA%20Date%20Pickers/ARIA%20Date%20Picker%20%28Basic%29/demo.htm Jon Gunderson, Ph.D., CPWA Coordinator of Accessible IT Group University of Illinois at Urbana/Champaign 1207 S. Oak Street Champaign, IL 61820 www: https://go.illinois.edu/jongund
Received on Tuesday, 18 June 2019 22:57:32 UTC