JAWS Screenreader not Reading TextArea Placeholder and InvalidText

[embrown-ibm]

Title line:

JAWS Screenreader not Reading TextArea Placeholder and InvalidText. As part of our accessibility testing using JAWS, the placeholder and the invalidText of our <TextArea> component are not being read.

Environment

Operating system
Windows 10

Browser
Firefox

Automated testing tool and ruleset

Assistive technology used to verify
JAWS 2019

Detailed description

What version of the Carbon Design System are you using?
v10.8.0

What did you expect to happen?
We expected the placeholder and invalidText would be read just as they are for the <TextInput> component.

What happened instead?
The placeholder and invalidText is read for the <TextInput> component but not the <TextArea>.

Steps to reproduce the issue

1. Add a <TextInput> to a dialog
2. Add a <TextArea> to a dialog
3. Open the dialog and attempt to read all of the text contained in it.

Additional information

[tw15egan]

According to w3, placeholder text is not meant/able to be read by screen readers (https://www.w3.org/WAI/tutorials/forms/instructions/#placeholder-text)

The invalid text not being read is a problem.

[dakahn]

Confirmed this with JAWS 2020 on Firefox latest. The validation text is accessible via screen reader, but it is not read when the error is thrown.

[embrown-ibm]

@dakahn I noticed that you added the label waiting for author's response. To what do you want me to respond? This still appears to be a problem. The problem was originally found during our 1Q Accessibility test and remained a problem during our 2Q Accessibility test. Will there be a solution to this problem soon?

[dakahn]

No response needed, just a mis-click 👍

Can't give you an ETA, but I have plans to get to some backlogged JAWS a11y work in a coming sprint soon. Stay tuned

[dakahn]

update: we're going to knock out some JAWS issues next sprint. Our sprint planning doc reflects that here
#6772