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 does not announce aria-describedby or aria-required when contenteditable="true" elements have content #643

Open
greypants opened this issue Jun 9, 2022 · 1 comment

Comments

@greypants
Copy link

greypants commented Jun 9, 2022

Summary

JAWS does not announce aria-describedby or aria-required when contenteditable="true" when the container has content.

Works with an empty element (label, description, and required are read):

<label id="label">My Label</label>
<div 
  role="textbox" 
  contenteditable="true" 
  tabindex="0" 
  aria-labelledby="label" 
  aria-describedby="description" 
  aria-required="true">
</div>
<p id="description">My description</p>

Fails when text content is present (only label is read):

<label id="label">My Label</label>
<div 
   role="textbox" 
  contenteditable="true" 
  tabindex="0" 
  aria-labelledby="label" 
  aria-describedby="description" 
  aria-required="true">
    Some content
</div>
<p id="description">My description</p>
  1. Go to https://codepen.io/greypants/pen/LYQgqLm?editors=1100
  2. Tab through the examples, and note what JAWS reads

Expected result

All examples should read the label, description, and required status when the textbox is focused.

Actual result

Examples 4 and 5 do not read the description or required status.

Example

https://codepen.io/greypants/pen/LYQgqLm?editors=1100

Additional Information

The behavior works properly on the other screen readers I'm testing:

  • VoiceOver/Safari/Mac OS 12
  • NVDA/Edge/Windows 10

JAWS version and build number

2022.2202.38 LIM

Operating System and version

Windows 10 (via Parallels desktop VM on Mac OS 12.3.1)

Browser and version:

Microsoft Edge 100.0.1185.39

@JAWS-test
Copy link

The cause seems to be the same as with textarea. JAWS treats both elements the same, see #484 and #201

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

2 participants