You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Column groups are poorly supported in many common screen reader/browser combinations. Column spans aren't announced, and column group headers can be associated with the wrong headers and cells.
There's no way to provide a caption, summary, or accessible name for tables
Column resizing isn't possible using a keyboard
Row groups use purely visual cues to associate rows with row groups, and can be confusing to navigate for non-visual users
Custom cell click actions aren't accessible to keyboard users
Sortable column headers don't have very obvious focus indicators
Sortable column headers always include the word "sort" in their accessible names, and are more verbose than necessary
Tables are read as clickable by NVDA for some reason, although not by JAWS (possibly more of an htmlwidgets issue)
Past issues
There's no way to mark cells as row headers without using rownames (hard for tibbles especially). Fixed in 0.2.3.9000
Cells in the rownames column aren't marked up as row headers. Fixed in 0.2.3.9000
When searching or filtering a table, changes to the table aren't announced by assistive technologies. Fixed in 0.2.3.9000, but only for tables with pagination and page info shown.
Row group expand buttons are incorrectly labeled as "expand details" and "collapse details". Fixed in 0.2.3.9000
Row expand buttons have dynamic accessible labels, which may be confusing and/or inconsistently announced. Fixed in 0.2.3.9000
Row selection checkboxes and radio buttons have dynamic accessible labels, which may be confusing and/or inconsistently announced. Fixed in 0.2.3.9000
Tables with vertical or horizontal scrolling can't be scrolled using a keyboard in many cases. Fixed in 0.2.3.9000
The text was updated successfully, but these errors were encountered:
Known accessibility issues as of reactable 0.3.0
Past issues
The text was updated successfully, but these errors were encountered: