WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Feedback on a table sort implementation

for

From: Jeremy Echols
Date: Jun 19, 2018 11:03AM

On further reflection, I think the above-table description is going to be the best option. Adding anything I can think of to the buttons makes the speech cumbersome, and is one of those things you only need to know once. If the table's description is read (which happens in all cases of entering the table *except* tabbing to a header), it becomes a lot of unnecessary noise.

I still don't understand why tabbing into the table doesn't cause the "aria-describedby" element to be read. Is that an NVDA bug, or just standard screen reader behavior?

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Jeremy Echols
Sent: Tuesday, June 19, 2018 9:31 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Feedback on a table sort implementation

Yes, I put the information above the table. It's associated with the table via aria-describedby, but not the individual buttons. It seems to get read properly when first entering the table, though not if you tab into the table, which seems like a bug.

I think I'll go ahead and put the description on the buttons instead. It's just extra hidden magic and I'm not a big fan of that.

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen walker
Sent: Monday, June 18, 2018 2:24 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Feedback on a table sort implementation

You can certainly have it visible to everyone, although I wouldn't put it on the button label. Are you thinking of a general statement before the table that says clicking on the column headers will sort the column? If I'm an AT user and I tab through the interface, I'll miss that statement unless it's associated with the button via aria-describedby or a similar labeling.


On Mon, Jun 18, 2018 at 3:15 PM, Jeremy Echols < <EMAIL REMOVED> > wrote:

> I agree, but I am leaning toward keeping a unified experience where I
> can. It's less to maintain, less "magic" hidden in the HTML, may help
> users with cognitive disabilities, and doesn't really have to take up
> much space. Is there any accessibility-related con to having the
> information visible to everybody?
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> glen walker
> Sent: Monday, June 18, 2018 1:52 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Feedback on a table sort implementation
>
> I'm not sure the explanatory text is needed for all users. Sighted
> users have the icon on the button and the arrows are somewhat
> universally understood. But since the icons are hidden from AT,
> explanatory text is needed for AT. That can be via ARIA or a "visually-hidden" or "sr-only"
> class.
> > > archives at http://webaim.org/discussion/archives
> > > > archives at http://webaim.org/discussion/archives
> >