wsxover commented on issue #24688: URL: https://github.com/apache/superset/issues/24688#issuecomment-1747254184
> Libraries like react-virtualized and react-window can be configured to over-render rows so that there are some "next" and "previous" rows (not visible, but in the DOM) for screen readers. Hmm. Depending on what exactly is going on that might be sufficient. But the symptoms Graham describe above sound more like react-virtualized getting confused by the navigation events JAWS and NVDA generate (jumping around, etc.) to me. >So far as I understand, ARIA roles should be sufficient here (but maybe I'm mistaken). As [MDN](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/table_role) repeats (no less than three times): "Using a native HTML table element whenever possible is strongly encouraged." And [Caniuse](https://caniuse.com/?search=aria-role) adds "Support for ARIA is rather complex and currently is not fully supported in any browser." There's some info on JAWS support for ARIA in [JAWS-ARIA-Support.doc](https://support.freedomscientific.com/Content/Documents/Other/JAWS-ARIA-Support.doc) on Freedom Scientific's web site (note absence of any mention of tables). I haven't found similar documentation for NVDA. The [Accessibility Tree](https://developer.chrome.com/blog/full-accessibility-tree/) in Chrome DevTools may also help to figure out what JAWS' view of the faux table is (it uses the browser's accessibility API to get information about the web page). I've no direct direct data on this, but in general terms using `div+aria` sounds iffy and I wouldn't personally have bet on it working correctly. Not that tables in HTML are that great, but they're a bit more of a known quantity. Especially when you go beyond the Big 4. JAWS in particular used to have heuristics to determine whether a table is a layout table or a data table, and a special "table mode" for navigating data tables, and this is the kind of thing I would have expected to break when not using a real table element. -- 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
