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.

Sign up for GitHub

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

Jump to bottom

Numbers pronunciation doesn't reflect the language of the content read #14155

Open
bdubetink opened this issue Sep 15, 2022 · 1 comment
Open

Numbers pronunciation doesn't reflect the language of the content read #14155

bdubetink opened this issue Sep 15, 2022 · 1 comment
Labels
app/chrome app/edge/anaheim MS browser, chromium based, replaces Spartan in 2019 by Anaheim. NVDA access via IA2. feature/i18n Internationalization features needs-technical-investigation A technical investigation is required to progress the issue. needs-triage p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority

Comments

@bdubetink
Copy link

We have a web page where there is texts in french and english (This is a maintenance page that is displayed when the website is under maitenance, otherwize, the website is multilingual and contain one language per page)

The html tag contain a lang attribute containing the default language (french) and the content in english on the page are surround by element with lang attribute english.

There a simplified version containing the problematic part:

<html lang="fr">
	<head>...</head>
	<body>
		<div lang="fr">
			<p>Pour les personnes malentendantes ou ayant des troubles de la parole, composez le numéro sans frais <a href="tel:1-800-268-9503" aria-label="Téléphone ATS pour malentendants. 1. 8 0 0. 2 6 8. 9 5 0 3."><span aria-hidden="false">1-800-268-9503</span><span class="hidden-text">1. 8 0 0. 2 6 8. 9 5 0 3.</span></a> à l’aide d’un appareil téléphonique (ATS).</p>
		</div>
		<div lang="en">
			<p>For hearing or speech impaired persons, call us toll-free using a telecommunication device (TTY) at <a href="tel:1-800-268-9503" aria-label="TTY hearing impaired phone. 1. 8 0 0. 2 6 8. 9 5 0 3."><span lang="en" aria-hidden="false">1-800-268-9503</span><span class="hidden-text">1. 8 0 0. 2 6 8. 9 5 0 3.</span></a>.</p>
		</div>
	</body>
</html>

Steps to reproduce:

Create a page containing multiple language and add numbers inside a section that need to be pronunce in english. <div lang="en">

Actual behavior:

The problematic part is aria-label="TTY hearing impaired phone. 1. 8 0 0. 2 6 8. 9 5 0 3." in the english div.

All the text is pronunce as english except for the number that are pronunced in french. We hear "un huit zéro zéro deux six huit neuf cinq zéro trois"

Expected behavior:

We should hear "one eight zero zero two six eight nine five zero tree" for the phone number

System configuration

Standard NVDA installation on windows downloaded here : https://www.nvaccess.org/download/

NVDA version:

2022.2.2

Windows version:

Windows 10 professional
Version 21H2
Build 19044.2006

Name and version of other software in use when reproducing the issue:

Browsers :
Chrome Version 105.0.5195.102 - french
Firefox Version 104.0.2 - french
Opera Version 90.0.4480.84 - english

Other information about your system:

Language of OS : French Canada

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

Same behavior detected with NVDA version 2022.1 installed on a different computer, but with the same OS.

If NVDA add-ons are disabled, is your problem still occurring?

There is no add-ons.

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

It seems to resolve the issue on Firefox, but the bug describe still occured in Chrome, Opera and Edge.
@seanbudd seanbudd changed the title Numbers pronunciation doesn't reflect the language of the content readed Numbers pronunciation doesn't reflect the language of the content read Sep 20, 2022
@seanbudd seanbudd added app/chrome app/edge/anaheim MS browser, chromium based, replaces Spartan in 2019 by Anaheim. NVDA access via IA2. feature/i18n Internationalization features p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority needs-technical-investigation A technical investigation is required to progress the issue. labels Sep 20, 2022
@loic-marin
Copy link

I had the exact same error in one of my last projects... I did not find any solution at the time so I had to create two distinct pages in order to separate languages explicitely.
I would be very interested to know if a solution is found.

@mitchellevan mitchellevan mentioned this issue Dec 30, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
app/chrome app/edge/anaheim MS browser, chromium based, replaces Spartan in 2019 by Anaheim. NVDA access via IA2. feature/i18n Internationalization features needs-technical-investigation A technical investigation is required to progress the issue. needs-triage p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@seanbudd @loic-marin @bdubetink