WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: ARIA Grid Discussion

for

From: Mohith BP
Date: Aug 5, 2018 11:33PM

Hi,

role="table" is not supported by all the major screen readers
especially older versions.
Tested around 4 months ago.
ARIA grid also has limitations with NVDA and browser combinations.

At this point working fix is what Jonathan suggested.


Thanks & Regards,
Mohith B. P.


On 8/5/18, Jonathan C. Cohn < <EMAIL REMOVED> > wrote:
> Makes sense, vut I was not able to get that to work when i tried three
> months ago.
>
> Best wishes,
>
> Jonathan Cohn
>
>> On Aug 4, 2018, at 9:33 AM, Birkir R. Gunnarsson
>> < <EMAIL REMOVED> > wrote:
>>
>> What about placing a div element around both tables, giving it a role
>> of table, then use role="presentation" on the table elements.
>> <div role="table">
>> <table role=="presentation">
>> <tr>
>> <th>heading</th>
>> </tr>
>> ...
>> </table>
>> ...
>> </div>
>> Not sure if this works but technically the element with role="table
>> now owns all the tr elements of the other two tables, so to a
>> compliant assistive technology those look like a single table.
>> I'd give it a 40/60 chance of working, but it would be an interesting
>> experiment.
>> That is, if I am understanding the problem correctly.
>>
>>
>>> On 8/3/18, Jonathan Cohn < <EMAIL REMOVED> > wrote:
>>> Ah, the wonderful floating table issues.
>>>
>>> We hide the 1column table and then have it in the main table but hidden
>>> underneath the 1 column table
>>>
>>> I hope that makes sense. Though generally a table that is that big gets
>>> very
>>> unwieldy for non screen reader users where they still have to scan back
>>> to
>>> the first column to remember what they are looking at.
>>>
>>> In a lot of cases, one can have fewer columns and then a dialog or
>>> separate
>>> window that can be brought up with all the details.
>>>
>>> Take care,
>>>
>>> Jonathan Cohn
>>> .
>>>> On Aug 3, 2018, at 3:20 PM, Jim Homme < <EMAIL REMOVED> > wrote:
>>>>
>>>> Hi,
>>>> Just when you think you don't need to see a discussion, it comes up as
>>>> a
>>>> topic in testing after it has been talked about on list.
>>>>
>>>> I'm looking for info about making ARIA grids accessible. Specifically,
>>>> to
>>>> a screen reader it looks like we have a one row table followed by the
>>>> rest
>>>> of the table in a separate table. I want to understand what the issues
>>>> are
>>>> from a developer perspective. In otherwords, if the developer says
>>>> something like "We are using this grid because it is responsive and we
>>>> don't want to turn it into a single HTML table because it will break
>>>> what
>>>> we want it to do," how do I respond and show them they can have their
>>>> cake
>>>> and eat it too?
>>>>
>>>> Thanks.
>>>>
>>>> Jim
>>>>
>>>>
>>>>
>>>> ==========
>>>> Jim Homme
>>>> Product Manager
>>>> Digital Accessibility
>>>> Bender Consulting Services
>>>> 412-787-8567
>>>> https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
>>>> People with disabilities, access job openings at
>>>> https://www.benderconsult.com/careers/job-openings
>>>>
>>>>
>>>> >>>> >>>> >>>> >>>
>>> >>> >>> >>> >>>
>>
>>
>> --
>> Work hard. Have fun. Make history.
>> >> >> >> > > > > >