E-mail List Archives
Re: Turning in/off inaccessible feature
From: glen walker
Date: Sep 16, 2019 5:06PM
- Next message: Birkir R. Gunnarsson: "Re: Question on a caption for Accessible Tables with Navigation"
- Previous message: Todd Magnusson: "Re: Turning in/off inaccessible feature"
- Next message in Thread: Mallory: "Re: Turning in/off inaccessible feature"
- Previous message in Thread: Todd Magnusson: "Re: Turning in/off inaccessible feature"
- View all messages in this Thread
The "hacking" comment and using the roles was not specifying roles on
elements that had the role already. When you specify role="presentation"
on a table, all rows and cells lose their identities. When you're hacking
two separate tables to appear as one table, you have to reapply the
appropriate roles to the <tr> and <td> elements.
On Mon, Sep 16, 2019 at 4:47 PM Todd Magnusson < <EMAIL REMOVED> > wrote:
> Hopefully I'm understanding the context accurately, throwing in my two
> cents in on the below comment "You can hack the heck out of it with ARIA",
> my advise would be to not reapply roles on elements with the role already.
> I've had interesting results with NVDA reading tables under those
> circumstances. I understand the reasoning of course (lets say you change
> the display model in CSS to let's say 'display: grid', but want to keep the
> table semantics.)
>
>
>
- Next message: Birkir R. Gunnarsson: "Re: Question on a caption for Accessible Tables with Navigation"
- Previous message: Todd Magnusson: "Re: Turning in/off inaccessible feature"
- Next message in Thread: Mallory: "Re: Turning in/off inaccessible feature"
- Previous message in Thread: Todd Magnusson: "Re: Turning in/off inaccessible feature"
- View all messages in this Thread