[chrome/Edge + Jaws2022] When text area contains value, JAWS does not read the text linked to the textarea via aria-describedby.

[madhaviherle]

Summary

1. Created a basic text area

<label for="address">Label</label><br>
<Textarea name="addresstext" aria-describedby="help" id="address">test text area</textarea>
<p id="help"> Help text for text area </p>

Expected result

When tabbed to the text area, screen reader should announce the associated help text.

Actual result

JAWS 17 and 2018 do not read the help text when text area contains value. Fails in IE 11 and Chrome 73
JAWS 2018 does not read the help text even when placeholder is present in the text area in Chrome 73

Operating System and version

Windows 7

Browser and version:

IE 11 and Chrome 73

[JAWS-test]

The problem also occurs with JAWS 2019 and IE 11. It also occurs with the title attribute, i.e., the description is generally not output in textarea with text content.

[JAWS-test]

The problem also exists with JAWS 2019 in combination with Chrome and Firefox. Maybe you can change the title to make it clear that it's not limited to IE 11 and older versions of JAWS?

[stevefaulkner]

created test cases https://s.codepen.io/stevef/debug/RwbZERv, confirmed bug

[stevefaulkner]

This issue has already been filed and assigned internally: Bug 109662 - When textareas have initial default text then accessible descriptions not read in some browsers

[JAWS-test]

The problem still occurs with JAWS 2020.2008 and current version of Chrome, IE 11 and Firefox.

The following descriptions are not output as soon as textarea contains a value:

• aria-describedby
• aria-description
• aria-errormessage
• title

Furthermore the status of textarea is not output if textarea contains a value, e.g.

• aria invalid
• aria-required

@stevefaulkner Maybe you can update the internal bug 109662 according to aria-invalid, aria-required etc.

[marie450]

The problem still occurs with Jaws 2022.2202.38 both in Chrome and Edge.

Firefox seem fix.

[stevefaulkner]

thanks @marie450 I have contacted @ggordon-vispero for an update

[stevefaulkner]

Found out the internal bug had been closed as it was initially reported against IE11, It has now been re-opened with an increased priority.

[adamsamec]

The bug still persists with JAWS 2023.2209.11 BETA. And it occurs with Mozilla Firefox 105 as well.

[stevefaulkner]

Works in JAWS 2024.2310.70
test case