WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Should NVDA announce "table" when it encounters CSS display:table ?

for

From: Farough, David (CFP/PSC)
Date: Apr 28, 2021 9:16AM

We currently have an application which uses display table.
We have recently noticed that this can modify the groupings of radio buttons. Jaws and NVDA will, when focussing on a radio button, speak the control but report it's position
as being "1 of 1" instead of it's Propper position within the group.

This behaviour occurs in Firefox 89 and Microsoft Edge
This does not occur in Firefox though.
We are hoping that using the presentation role on the div will correct this.

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen walker
Sent: Wednesday, April 21, 2021 3:01 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Should NVDA announce "table" when it encounters CSS display:table ?

Thanks, Jonathan. I was about to mention that. This isn't a page with "traditional" layout tables that use <table> elements for pure layout purposes. This is a page that is using CSS display:table. There are no table semantics in the html and there are no ARIA roles specified on the page. I was surprised NVDA+Chrome announced it as a table.

I know the opposite is typically surfaced. If I have a real <table> element and I apply display:block or display:inline or almost anything that changes it from the default display:table that the screen reader no longer thinks the table is a table anymore.


On Wed, Apr 21, 2021 at 10:20 AM Jonathan Cohn < <EMAIL REMOVED> > wrote:

> Is there some confusion here going on between <table> HTML designs
> that are only used for layout and CSS tables?
>
> The original posting specifically mentioned table in the style, not
> the HTML.
> Apparently, NVDA recognizes the CSS table, but does not further
> process it.
> Traditionally, layout tables are HTML elements s <table>, <tr>, <th?,
> <tbody> that have no <th? elements, or are quite small.
>
> No wonder, screen reader users with no HTML understanding get
> confused, most don't care as long as it reads sensibly.
> Jonathan
>
> > > archives at http://webaim.org/discussion/archives
> >