Skip to content
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

JAWS doesn't announce change of language for content inside button tags #340

Open
brooksienoodlesoup opened this issue Nov 6, 2019 · 4 comments

Comments

@brooksienoodlesoup
Copy link

brooksienoodlesoup commented Nov 6, 2019

Summary

For button labels that are provided by the content that falls between the opening and closing button element tags, designated changes of language are not announced by JAWS using the default Eloquence voice.

Expected result

I expected JAWS to announce the button label using two different accents - English for "Start /" and Spanish for "Iniciar."

Actual result

JAWS read all of the button label in an English accent.

Example

Example code:

<html lang="en">
..
<button>Start /<span lang="es"> Iniciar</span></button>
..
</html>

Additional Information

JAWS version and build number

2019.1909.28 ILM

Operating System and version

Windows 7

Browser and version:

Firefox 70.0.1

@JAWS-test
Copy link

Related: w3c/accname#56

@JAWS-test
Copy link

The problem also occurs in Chrome and IE 11. In general, the lang attribute in JAWS only works reliably with texts, not with interactive elements.

In the button example, a distinction must be made between tab navigation and arrow navigation. Is different from browser to browser, sometimes correct, but never correct for every navigation method.

It is interesting to note that in Firefox and IE 11 the output of the button depends on whether the language change takes place at the beginning or not at the beginning.

<button>Start /<span lang="es"> Iniciar</span></button>

is output with English pronunciation, but

<button><span lang="es"> Iniciar</span> / Start </button>

is output with Spanish pronunciation.

As long as the many problems with the output of language changes in JAWS are not fixed, language changes should be avoided as much as possible.

@dfarough
Copy link

dfarough commented Nov 8, 2019

another situation where this occurs is for field sets.
I notice that the legend of a fieldset will be spoken in English even though the lang is set to fr
try the following code.

fieldset.txt

@JAWS-test
Copy link

another situation where this occurs is for field sets.

I have already reported this error in #233 . Basically the following applies: The language change of interactive elements often does not work and should be avoided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants