-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Links with contextual screen-reader content not being read correctly #29
Comments
This happens with Chrome, but not IE. Firefox does announce the text correctly, but when navigating by character using the arrow buttons, you discover there is no space. Perhaps it is time to replace the ‘Change’ link with an ARIA label instead?
…Sent from my iPhone
On 8 Jun 2020, at 6:06 pm, Adam Liptrot ***@***.***> wrote:
JAWS in particular will merge the visible and hidden copy from a change link and then mis-pronounce the result, for example instead of "Change first name" it will say "Changefirst name". This also shows up in the dialog listing links.
Placing the space inside or outside the visually-hidden copy does not seem to make any difference to how the phrase is spoken or displayed.
One solution is to move from the current code:
Change<span class="visually-hidden"> first name</span>
to one which keeps the phrasing together:
<span aria-hidden="true">Change</span><span class="visually-hidden">Change first name</span>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
JAWSThe space between the visible and hidden copy in the change links is not being preserved with JAWS which means the “Change” and the first word of the hidden copy are being merged together and so mispronounced. Voiceover iOSIn Voiceover on iOS the span in the middle of the accessible name means that if a user is navigating by links they hear:
Android TalkBackWith Android TalkBack when a user is navigating normally by swiping the effect is the same as with VO navigating by links
do this
|
Reported to GDS on alphagov/govuk-frontend#1643 |
GDS have filed bugs with JAWS and NVDA around the honouring of spaces alphagov/govuk-frontend#1643 (comment) |
Update - I can't hear the merging of content anymore in JAWS (tested 2019, 2020, 2021), although the space is still missing in the dialog. |
Interesting possibility, that using a capital letter for the first word of the hidden copy might result in the non-honouring of the space to be negated by the screen-reader pronunciation of camelcased text eg ChangeName where the screen-reader will read out the words as individual words due to the casing. |
That sounds sensible as that's how it's supposed to work for hashtags. |
Fixed with Jaws 2024 |
JAWS in particular will merge the visible and hidden copy from a change link and then mis-pronounce the result, for example instead of "Change first name" it will say "Changefirst name". This also shows up in the dialog listing links.
Placing the space inside or outside the visually-hidden copy does not seem to make any difference to how the phrase is spoken or displayed.
One solution is to move from the current code:
Change<span class="visually-hidden"> first name</span>
to one which keeps the phrasing together:
<span aria-hidden="true">Change</span><span class="visually-hidden">Change first name</span>
The text was updated successfully, but these errors were encountered: