E-mail List Archives
Re: Using ARIA grids
From: Jeremy Echols
Date: Jul 24, 2020 10:45AM
- Next message: Don Mauck: "Re: Using ARIA grids"
- Previous message: glen walker: "Re: Using ARIA grids"
- Next message in Thread: Don Mauck: "Re: Using ARIA grids"
- Previous message in Thread: glen walker: "Re: Using ARIA grids"
- View all messages in this Thread
The "grid" role does not in fact specifically address the issue of a table that needs to scroll. It is one thing a grid can be programmed to do, but it isn't something that is inherently a requirement for a grid.
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen walker
Sent: Friday, July 24, 2020 09:16
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Using ARIA grids
You might have missed the purpose of my question. I wasn't trying to explain the purpose of ARIA. It sounded like you said developers thought they had to use an ARIA grid instead of a native <table> because of scrolling issues. My question was that since ARIA doesn't affect behavior, there should not be any limitation of behavior between an ARIA grid and a native <table>. I was trying to get clarification if that's what the developers thought.
Now, there might be a difference in behavior in how a screen reader surfaces a grid vs a table with regards to screen reader shortcut keys used in navigating a table. I've seen varying levels of support for role="grid"
between browser and screen reader combinations.
On Thu, Jul 23, 2020 at 3:23 PM Don Mauck < <EMAIL REMOVED> > wrote:
> My point was that they chose to use an ARIA-Grid. I'm very much aware
> of ARIA and what it is for. That was a choice the developer made not mine.
> -----Original Message-----
> From: glen walker < <EMAIL REMOVED> >
> Sent: Thursday, July 23, 2020 3:19 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Using ARIA grids
> I'm a little confused by this statement: "developers...using ARIA
> Grid controls since apparently tables do not allow for automatic scrolling".
> Using an ARIA attribute should have no effect on the behavior of an
> element. ARIA attributes are hints to assistive technology. See
> dl7l4TRcMO3qLM1dC36LKs$ which says, "Adding an ARIA role will not make
> an element look or act differently for people not using assistive
> technology. It does not change the behaviours, states and properties
> of the host element but only the native role semantics."
> That statement is talking about the role attribute specifically, but
> can be applied to aria-* attributes too.
> So when you say having an aria grid allows automatic scrolling but
> native tables do not, I don't follow why that's true.