Simon818 commented on issue #24688: URL: https://github.com/apache/superset/issues/24688#issuecomment-1748026758
> The fix would require @bvaughn to figure out the events triggered by JAWS/NVDA and use those... I can't speak to JAWS but when you have the option "Automatically set system focus to focusable elements" disabled. NVDA doesn't generate events at all. it is possible for NVDA's virtual cursor to be on a section of the page that isn't visually visible. I don't know a way around this besides simply rendering all rows in the DOM. I am also a bit skeptical about fudging an entire table structure with ARIA but I have technically seen it done in a way that is readable with NVDA, so i'm not going to definitively say it's impractical. My understanding is that when ARIA roles are defined properly, the controls should "look" like their given ARIA role and the screen reader may not even be able to tell the difference between that and native controls. The main problem I can foresee with tables is the complexity of maintaining the table itself, the headers, the rows, and the cells and having the ARIA line up well enough for screen readers to read them; however, if the framework claims to tak e care of that we could at least test to see whether screen readers play nice with the tale as long as all rows are rendered. It seems like a reasonable initial step. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
