Conversation
|
I'm noticing this in 4.1 dashboard as well, but do we need a |
|
I think there might be some browser caching affecting where your focus goes, but for me I can
And the skip navigation button appears. Another thing that I recall noticing with NVDA is that tab will start focus on whatever is currently being read. So if you do not respond quickly enough and NVDA begins to read the navbar items, the tab key will start you after the skip navigation button. I'd be curious to know what happens if you execute the steps above with and without NVDA enabled. Besides the fact, |
Fixes #4959. Copies the same approach from the dashboard into the job composer, including giving the main section the
main-containerid, and copying css styles to keep the skip button hidden unless it has focus.