Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Column Headers Not Announced
See original GitHub issueDescribe the bug
When navigating the calendar grid (<table>) in JAWS, the column headers are not announced. All I hear is “two zero two zero dash zero four dash zero two” (or whatever is the date in this number format).
To Reproduce Steps to reproduce the behavior:
- Go to the grid,
- Navigate between days within a week,
- Observe the screen reader does not announce the day of the week.
Expected behavior As I navigate from column to column, I should hear the column header. Specifically I should hear the day of week as I move through a week.
Screenshots I made a video, but GitHub does not allow me to embed it.
Desktop (please complete the following information):
- OS: Windows 10
- Browser Chrome
- Version 85
- JAWS 2020
Additional context Using first example at https://duetds.github.io/date-picker/
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
You are correct! It fell off my radar. Let me take a run at it tomorrow.
These are not the same issue.
#25 specifically asks for the day of the week to be added to every cell, which is too verbose for screen reader users and should only be considered as a last resort.
This issue is about getting the column headers to announce as they would for a regular table. If you do so, a column header will only be announced when a user changes columns, not rows, reducing the verbosity. Further, a screen reader user can choose to configure how the table column headers are announced overall, something they cannot do when the text is made part of every cell.
Because the outcome of correct column headers is functionally (and programmatically) not the same as that proposed in #25, I believe it is premature to close this.