E-mail List Archives
Chrome 80 Bug
From: JP Jamous
Date: Mar 15, 2020 1:54PM
- Next message: Murphy, Sean: "Re: [WebAim] differentiate between the edit and read only edit fields."
- Previous message: vennila murugesan: "Sub-domain link - open in new tab or same"
- Next message in Thread: Steve Green: "Re: Chrome 80 Bug"
- Previous message in Thread: None
- View all messages in this Thread
When Chrome 80 was installed on my personal and work machines, running Win
10, I discovered that all Windows screen readers for the blind are not
reading label text that is inside a <strong> tag if a <span> tag in present
inside the <label>. When the Screen Reader user tabs through the form, only
the <span> text is announced. This was not present in any previous Chrome
versions. Here is an example:
<label for="first-name">
<strong>First Name</strong> <span>*</span>
<!-- Only the "*" is spoken. -->
</label>
<input type="text" id="first-name" required="required">
If I place the <span> before the <strong>, only the <span> text is spoken.
<label for="first-name">
<span*</span> <strong>First Name</strong
<!-- Only the "*" is spoken. -->
</label>
<input type="text" id="first-name" required="required">
If I insert the <span> inside the <strong>, then nothing is spoken.
<label for="first-name">
<strong>First Name <span>*</span></strong>
<!-- Nothing is spoken. -->
</label>
<input type="text" id="first-name" required="required">
I found this bug by accident. I have tried to figure out if it was a screen
reader bug, but all of my evaluations only failed in Chrome Version
80.0.3987.132 (Official Build) (64-bit). All 3 versions, of the markup
above, work fine with IE11, Edge, and Firefox 74.0 (64-bit) using both JAWS
2019, 2020 and NVDA 2019.1.1, 2019.3.1.
I have filed a bug with Google and was wondering if any of you have faced
this issue.
==================================================
Jean-Pierre Jamous
Principal Digital Accessibility Engineer
Jepelsy LLC
W: (952) 666-2930
M: (952) 666-2930
<EMAIL REMOVED>
"The only limitations in life are those we set for ourselves"
==================================================
- Next message: Murphy, Sean: "Re: [WebAim] differentiate between the edit and read only edit fields."
- Previous message: vennila murugesan: "Sub-domain link - open in new tab or same"
- Next message in Thread: Steve Green: "Re: Chrome 80 Bug"
- Previous message in Thread: None
- View all messages in this Thread