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
{{ message }}
This repository has been archived by the owner on Aug 13, 2023. It is now read-only.
When navigating via elements, first it reads heading level 3/link + the name of the headline + the start time (whithout the date), but when navigating to the next element, it reads again heading level 3/link + just the date. Should it be all announced at once as when navigating via headings/links?
This bug is due to using display block CSS on span.TitleWrapper-sc-6oo8lp-5 jjATGt if we change display block to display inline-block, this fixes this bug, I believe we will then also need to apply width 100% to the span in question to fix the layout... Though I notice that the hover styling is now only underlining the 1st part of the h3 (the title such as 'Shirin Rana') - how can we address that? Or maybe that's ok?? Can ask UX if we can't fix that....
There is a related ZoomText bug "When using the TAB key to navigate through the feature, just the headline and start time are announced, not the date." This is also fix by changing the CSS as per above. Zoomtext should be re-tested when this has been implemented along with NVDA and all other AT.
Describe the bug
We have complicated, nested DOM elements within headings inside the radio schedule programme card.
Heading level 3s are very complex - we should simplify the DOM where possible. Current setup is this:
An issue in NVDA that may be related:
When navigating via elements, first it reads
heading level 3/link
+ the name of the headline + the start time (whithout the date), but when navigating to the next element, it reads againheading level 3/link
+ just the date. Should it be all announced at once as when navigating via headings/links?To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Testing notes
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: