WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Turning in/off inaccessible feature

for

From: Todd Magnusson
Date: Sep 16, 2019 4:47PM

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.)

Also, I'd advise against floating headers, at least in mobile. iOS VoiceOver has huge focus management issues with fixed or absolute content in my own experience. Even in desktop, focus management for JAWS and NVDA has to be JavaScript assisted in certain scenarios.

- Todd

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Birkir R. Gunnarsson
Sent: Monday, September 16, 2019 7:36 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Turning in/off inaccessible feature

You can hack the heck out of it with ARIA.
role="table"
role="row"
role="rowheader"
role="columnheader"
role="cell"

You can probably somehow fit these over your table in pinned mode, but I think if there is a single button with clear wording about functionality that you wouldn't have to.



On 9/15/19, Jonathan Cohn < <EMAIL REMOVED> > wrote:
> I would agree, but we found no good way of doing this with HTML and
> CSS without a miserable hack of actually having two or three tables
> and using CSS z index to slide the true data under the table headers.
> When the button to turn on accessibility is checked, the entire thing
> is replaced with a single table that follows accessibility best practices.
> If CSS / HTML tables had a way to mark certain columns as floating
> when scrolling, or if clients would allow only tables that fit on
> screen, then this mess could be avoided.
>
> Best wishes,
>
> Jonathan Cohn
>
>
>
>> On Sep 13, 2019, at 5:50 PM, Lucy GRECO < <EMAIL REMOVED> > wrote:
>>
>> Having the ability to turn off the column might be useful for more
>> people than just screen reader users however it really goes against
>> my instinct to come up with an alternative format just for screen
>> reader users
>>
>> On Fri, Sep 13, 2019, 2:36 PM glen walker < <EMAIL REMOVED> > wrote:
>>
>>> I'm guessing the pinning of the column effectively takes that column
>>> out of the table so that you can scroll the rest of it. I tried
>>> playing with a simple example to visually hide the table column but
>>> leave it in the table but my 5 min attempts didn't work. But I
>>> think the idea is worth pursuing. I also tried the headers
>>> attribute on the <td> but didn't have much luck with that either.
>>> But as mentioned, it was a quick test and only tried NVDA on
>>> firefox.
>>> >>> >>> archives at http://webaim.org/discussion/archives
>>> >>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >
> > > archives at http://webaim.org/discussion/archives
> >


--
Work hard. Have fun. Make history.