Hide Readspeaker for screen reader users

Attaching patch for composer.patches.json file.

Thank you for your investigation.
I agree with the aria-hidden due to the redundant content argument.
But disabled is not an allowed attribute for anchor elements. So I think we should go with tabindex="-1".
But the current template has an accesskey="L". I think this could be a discrepancy or?

The original state of the template come direct from the vendor documentation.

The original purpose was to hide Readspeaker from screen readers which setting tabindex=-1 won't do if using screen reader navigation (opposed to keyboard tabbing).

We landed on leaving it as is and letting screen reader users choose to ignore so as not to interfere with keyboard users.

Might be able to set this as 'won't fix' or 'works as designed'?

Maybe aria-disabled="true" is what we are looking for in this case?
aria-disabled="true" only indicates semantically the state, but it's not by function.
This would have to manually controled for custom elements but not needed here.

Do you have an opinion on this?

Ah nope, I think it's worng. I am sorry. aria-disabled does not change focusability. But it must excluded.

@mcaddz

Thank you for your feedback. I have discussed this with our partnered agency and considered your response.
I am fully with you. Our assesment was similiar to yours.
We leave it as it is. I think there is no full separation of the user groups with the differrent accessibility needs.
So let them decide on their own.

But nevertheless, thank you for bringing that up.

sunlix → closed merge request !29