E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 3 (In chronological order)

From: Brian Lovely
Date: Mon, Jun 03 2019 11:19AM
Subject: Calendar VS Table Navigation
No previous message | Next message →

If you have a datepicker where the calendar portion is built out of a
table, does the calendar need to be navigable with table keyboard
shortcuts? Is ii considered accessible if the dates are simply navigated
with the virtual cursor (arrow key), and the standard table keyboard
shortcuts are ineffective?

--
*Brian Lovely*
Capital One Digital Accessibility
804.389.1064

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.

From: Steve Green
Date: Mon, Jun 03 2019 11:55AM
Subject: Re: Calendar VS Table Navigation
← Previous message | Next message →

That depends on what you mean by "accessible". It may well be WCAG-compliant (as long as the role is not conveyed as being a table), but you would need to do user testing to find out whether it is an acceptable user experience in practice. My experience of user testing is that participants usually have difficulty with date pickers, especially ones that use "application mode". If possible, allow people to type the date because that is much faster and user friendly.

Steve Green
Managing Director
Test Partners Ltd

From: Mallory
Date: Mon, Jun 03 2019 3:17PM
Subject: Re: Calendar VS Table Navigation
← Previous message | No next message

We've never been able to keep the table semantics even if we used a
table because we'd follow the aria grid pattern. Which basically undoes
all the table goodness. This includes the table headers (our day names)
not being available for days. Back to stuffing full day/date names into
a steaming pile of aria.

I agree with have a date input-- by that I mean not type="date". Those
suck keyboard and Dragon-wise. As a user, I'd rather have a plain text
input who takes whatever I throw at it and uses Postel's Law to accept
dates I put in, within reason. The calendar part is nice for seeing things
like: which day is that date? Is it a weekday or weekend? Date ranges
like with flights.

cheers,
Mallory

On Mon, Jun 3, 2019, at 7:55 PM, Steve Green wrote:
> That depends on what you mean by "accessible". It may well be
> WCAG-compliant (as long as the role is not conveyed as being a table),
> but you would need to do user testing to find out whether it is an
> acceptable user experience in practice. My experience of user testing
> is that participants usually have difficulty with date pickers,
> especially ones that use "application mode". If possible, allow people
> to type the date because that is much faster and user friendly.
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
>
>