- From: Kelly Childs <kelly@schoolwebmasters.com>
- Date: Mon, 4 Dec 2017 05:44:31 -0800
- To: Bryan Garaventa <bryan.garaventa@levelaccess.com>
- Cc: Steve Green <steve.green@testpartners.co.uk>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <CABt6Ly-aY4eEi0FTeBWZ4jXKHhUVTuV9vZjqavkWytRiYpZ5SA@mail.gmail.com>
Thanks so much for the feedback! On Fri, Dec 1, 2017 at 10:57 PM, Bryan Garaventa < bryan.garaventa@levelaccess.com> wrote: > Hi, > > I’m actually the one who programmed all of the WhatSock widgets archived > here > > https://github.com/accdc/tsg > > (Along with everything else on WhatSock and all of the accessible repos at > https://github.com/accdc?tab=repositories ) > > > > My point in saying this is that I am totally blind, and all of these > technologies are intentionally designed to be supported in the most common > screen reader and browser combinations which is where I do my testing for > all of these things. Also, I am perfectly happy to fix any issues that > people do encounter, or explain further when there are breakdowns in levels > of support in some assistive technologies if applicable. > > > > So if you could please list all of the accessibility issues that you are > encountering with the WhatSock datepicker, such as the following, I would > appreciate it. > > http://whatsock.com/tsg/Coding%20Arena/ARIA%20Date%20Pickers/ARIA%20Date% > 20Picker%20(with%20Disabled%20Date%20Ranges)/demo.htm > > > > I have tested this successfully across IE11, Firefox, and Chrome using > JAWS 12 through 18 on Win 7 through 10, as well as the latest versions of > NVDA going back three years in the same combinations, plus iOS VoiceOver in > Safari on both the iPad and iPhone for touch device support. This too has > been tested successfully by sighted Dragon users with voice commands to > ensure accessibility there as well using standard voiced keyboard commands > as expected. > > > > It’s always possible that I may have missed something, so please let me > know which issues you are having difficulty with and I’ll be happy to > provide more info or update the widget accordingly. > > > > Best wishes, > > Bryan > > > > > > Bryan Garaventa > > Accessibility Fellow > > Level Access, Inc. > > Bryan.Garaventa@LevelAccess.com > > 415.624.2709 <(415)%20624-2709> (o) > > www.LevelAccess.com > > > > *From:* Steve Green [mailto:steve.green@testpartners.co.uk] > *Sent:* Friday, December 01, 2017 5:35 PM > *To:* w3c-wai-ig@w3.org > *Subject:* RE: Accessible Interactive Calendar recommendations > > > > As I commented on Dennis’s article, most of those are totally inaccessible > (at least for screen reader users) and there are issues with the only two > that are usable at all. In fact, the more I test them, the more issues I > find. > > > > I have tested lots of other date pickers too, but none are any better. > Right now, my view is that there are none that you can just pick up and > use, and most are not even fixable. The Deque and Whatsock ones might be > fixable but I certainly don’t have the skills to do that. > > > > The problem is compounded by the fact that their behaviour varies greatly > depending on not only which screen reader mode you navigate with inside the > date picker (i.e. forms mode or virtual cursor mode), but it can also vary > depending on how you entered the date picker (i.e. whether you tabbed in or > used the arrow keys). There are a surprising number of variations that need > to be tested. > > > > I have no doubt that some of the erroneous behaviours are caused by bugs > in the assistive technologies rather than by incorrect coding, but my view > is that developers have a responsibility to provide solutions that work > with the currently available assistive technologies. It’s not satisfactory > to say the code is fine because it would work with bug-free assistive > technologies that don’t actually exist yet. > > > > Steve Green > > Managing Director > > Test Partners Ltd > > > > > > *From:* Jennifer Sutton [mailto:jsuttondc@gmail.com <jsuttondc@gmail.com>] > > *Sent:* 01 December 2017 23:33 > *To:* w3c-wai-ig <w3c-wai-ig@w3.org> > *Subject:* Re: Accessible Interactive Calendar recommendations > > > > WAI folks: > > > > Here's a collection of date-pickers that Dennis Lembree put together at > one time. Hope it helps/gets you pointed in the right direction. See: > > > > http://www.webaxe.org/accessible-date-pickers/ > > > > If folks have more to recommend, feel free to comment on his post (and > here, too, of course). > > > > And for good measure, here's an article from Smashing Magazine that's > about these, generally, rather than being accessibility-centric: > > > > https://www.smashingmagazine.com/2017/07/designing-perfect- > date-time-picker/ > > > > I double-checked Heydon Pickering's Inclusive components site, which lots > of folks seem to be enjoying of late, but he hasn't worked on this > component, yet: > > https://inclusive-components.design > > > > Best, > > Jennifer > > > > On 12/1/2017 10:42 AM, Kelly Childs wrote: > > Hi All, > > > > Does anyone have a full accessible interactive calendar they recommend? > > > > Thanks! > > > > -- > > *Kelly Childs* > > *ADA Compliance & Graphic Support Manager* > > > > 888.750.4556 <(888)%20750-4556>, option 7 > > > > [image: Visit School Webmasters Social Sites] > <http://www.schoolwebmasters.com/Contact_Us> > > > > > -- *Kelly Childs* *ADA Compliance & Graphic Support Manager* 888.750.4556, option 7 [image: Visit School Webmasters Social Sites] <http://www.schoolwebmasters.com/Contact_Us>
Received on Monday, 4 December 2017 13:45:15 UTC