E-mail List Archives
Re: Turning in/off inaccessible feature
From: Todd Magnusson
Date: Sep 16, 2019 4:47PM
- Next message: glen walker: "Re: Turning in/off inaccessible feature"
- Previous message: Sailesh Panchang: "Re: Turning in/off inaccessible feature"
- Next message in Thread: glen walker: "Re: Turning in/off inaccessible feature"
- Previous message in Thread: Sailesh Panchang: "Re: Turning in/off inaccessible feature"
- View all messages in this Thread
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
- Next message: glen walker: "Re: Turning in/off inaccessible feature"
- Previous message: Sailesh Panchang: "Re: Turning in/off inaccessible feature"
- Next message in Thread: glen walker: "Re: Turning in/off inaccessible feature"
- Previous message in Thread: Sailesh Panchang: "Re: Turning in/off inaccessible feature"
- View all messages in this Thread