yousoph opened a new issue, #26177:
URL: https://github.com/apache/superset/issues/26177

   Table headers are in separate table element from table content, which is 
confusing to navigate for screen readers
   
   #### How to reproduce the bug
   
   1. Create a table chart
   2. Add the chart to a dashboard 
   3. Use a screen reader to navigate to the table chart and navigate within 
the table 
   
   ### Expected results
   User should be able to understand the table headers as well as the table 
content
   https://www.w3.org/TR/WCAG22/#info-and-relationships
   
   ### Actual results
   Screen reader reads the table content but not any of the headers 
   
   
   #### Screenshots
   
   
   
   ### Environment
   
   (please complete the following information):
   
   - browser type and version:
   - superset version: `master`
   - python version: `python --version`
   - node.js version: `node -v`
   - any feature flags active:
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [ ] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [x] I have reproduced the issue with at least the latest released version 
of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   Currently, when a Table Chart is created, the table headers are added to a 
<table> element, and the rows are added to another <table> element. Using a 
single <table> HTML element to display the Table chart content should help 
address this issue 


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to