WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Calendar widget Date selected status did not announced by JAWS/NVDA

for

From: Mallory
Date: Sep 8, 2017 7:08AM


Hm, I was confused-- we're using aria-current for today's date, not the
selected date.

On Fri, Sep 8, 2017, at 03:00 PM, Mallory wrote:
> This might have to do with how they're dealing with focus. One can
> either keep all the gridded elements as tabindex="-1" and use
> aria-activedescendent to set the state of the "current" day, but reading
> the spec, it looks like you could also instead combine tabindex="0" on
> the currently-focussed item and aria-selected=true (simply because it's
> focussed on, and not actually selected as in showing the date in the
> input). This would mean a roving selected state, and on some
> datepickers, this may actually be filling in that date in the input as
> focus moves.
>
> Because we have disabled days on our calendars, we couldn't see a way to
> use aria-selected to denote the currently-focussed day (the disabled
> days have to be able to receive focus as per the spec so users can
> orient) and we couldn't see aria-selected=true on an aria-disabled=true
> day making sense, so we only get aria-selected after hitting Enter.
> However this doesn't change the aria-activedescendent setting (if that's
> what's being announced), so we've tried also setting aria-current="date"
> on that element.
>
> The specs didn't really help us figure out what was the best thing to do
> in situations where there's disabled days, so we did what a lot of
> places do: made stuff up and hoped it worked. We're assuming anyone
> unable to tell the the currently-selected date from the calendar would
> go back to the text-input part anyway (where the selected date is
> displayed as a formatted string).
>
> cheers,
> Mallory
>
> On Thu, Sep 7, 2017, at 03:03 PM, Beranek, Nicholas via WebAIM-Forum
> wrote:
> > Hi Ajeesh,
> >
> > If they are setting aria-selected to "true" for the selected grid cell
> > and "false" to all the others, then that is sufficient to reveal the stat
> > programmatically. I've noticed the same behavior you mention and think we
> > should let the screen reader vendors know. I'd imagine the desired
> > behavior is to announce "selected" when the state of the component you're
> > on changes.
> >
> > Nick Beranek
> > Capital One
> >
> > > On Sep 7, 2017, at 3:03 AM, Ajeesh Thomas < <EMAIL REMOVED> > wrote:
> > >
> > > Hi All ,
> > > We come across a Calendar widget (with Grid Role) -
> > > here, User can select the Dates by using Keyboard - after Selection,
> > > instead closing the Widget -selected Date will be visually Highlighted
> > > with in the Calendar -
> > > However Screen reader is not announcing the Date selection status.
> > > Please see the behavior below.
> > > I. JAWS18 with IE 11:
> > > - Pressing Enter/Space Bar (Date visually highlighted)
> > > JAWS did not announced anything.
> > > - Using Arrow keys (over the Date visually highlighted)
> > > JAWS did not announced anything.
> > >
> > > II. VDA 2017.3 with Firefox 50:
> > > - Pressing Enter/Space Bar (Date visually highlighted) NVDA 2017.3 did
> > > not announced anything.
> > > - Using Arrow keys (over the Date visually highlighted) NVDA 2017.3
> > > announced as Highlighted date as - 'Selected.
> > > For example: On Arrow key navigation NVDA announced as 8 Sept 2017 Selected
> > > 1. Is there any Screen reader /Browser limitation to update the
> > > Date status with respect to ARIA
> > > 2. To make the Date status accessible with in Calendar widget (with
> > > Grid Role) what would be the solution
> > > Request your support in this regards.
> > >
> > >
> > >
> > >
> > > --
> > > " Have a fantastic day "ahead"
> > >
> > > Ajeesh Chacko Thomas,
> > > senior Accessibility Test Engineer,
> > > IBM India, Banglore,
> > > Mob: 0 81233 81222,Lan: 04742586821, Office: 04443423000
> > > skipe: ajeeshthomas86
> > >
> > > 'So many things are possible, as long as you don't know they are impossible.-
> > > > > > > > > > > > > > > >
> > The information contained in this e-mail is confidential and/or
> > proprietary to Capital One and/or its affiliates and may only be used
> > solely in performance of work or services for Capital One. The
> > information transmitted herewith is intended only for use by the
> > individual or entity to which it is addressed. If the reader of this
> > message is not the intended recipient, you are hereby notified that any
> > review, retransmission, dissemination, distribution, copying or other use
> > of, or taking of any action in reliance upon this information is strictly
> > prohibited. If you have received this communication in error, please
> > contact the sender and delete the material from your computer.
> > > > > > > > > > > >