- From: Shawn Henry <shawn@w3.org>
- Date: Wed, 11 Nov 2020 16:04:26 -0600
- To: Chidvi Lash <chidvi.gs@gmail.com>
- Cc: wai-eo-editors <wai-eo-editors@w3.org>
Hi Chidvilash, The best place to get a range of perspectives is the W3C WAI Interest Group (IG) Discussion List. You can join the mailing list and post questions by following the instructions about the Discussion List under: https://www.w3.org/WAI/about/groups/waiig/#mailinglist Best regards, ~ Shawn <http://www.w3.org/People/Shawn/> On 11-Nov-20 10:05 AM, Chidvi Lash wrote: > Hi Team, > > Could you please enlighten us with your inputs on the below issue which I am currently encountering: > > Below is a sample date picker, where I am facing challenges with the screen readers(NVDA/JAWS/Narrator) with the combination Edge Chromium and Google Chrome browsers in scan mode as the screen reader focus in not moving to the calendar icon button. > image.png > > Whenever the screen reader in on the textbox it is narrating the placeholder value(mm/dd/yyyy) and user is able to enter the value. > > when the user wants to navigate to the calendar in scan mode focus is not moving, however, using focus mode (By using Keyboard Tab Key) it is happening. Is this a WCAG violation, if so under which rule it will fall under? > > Also, when user enter the date manually using placeholder value(mm/dd/yyyy) what is the expected behavior of the screen reader in below scenario: > > After entering mm the '/' would be appended automatically in the textbox and how this will be notified to the user. > > I have already posted the same issue in Github : https://github.com/w3c/wai-intro-wcag/issues/68 <https://github.com/w3c/wai-intro-wcag/issues/68> > > Appreciate your suggestions... > > Thanks, > Chidvilash
Received on Wednesday, 11 November 2020 22:04:30 UTC