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

Accessibility for rich-text components #2345

Open
Tracked by #1288
jattasNI opened this issue Aug 14, 2024 · 0 comments
Open
Tracked by #1288

Accessibility for rich-text components #2345

jattasNI opened this issue Aug 14, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@jattasNI
Copy link
Contributor

🙋 Feature Request

😯 Problem to Solve

We didn't consider accessibility when building the rich text components. We should evaluate how they present in the accessibility tree and how well they work with screen readers.

One known issue with the rich text editor is captured in the Lighthouse accessibility report for the Angular example app.

ARIA input fields do not have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
Failing Elements
<div class="editor" aria-multiline="true" role="textbox" aria-disabled="false">

💁 Proposed Solution

📋 Tasks

@jattasNI jattasNI added enhancement New feature or request triage New issue that needs to be reviewed labels Aug 14, 2024
@jattasNI jattasNI removed the triage New issue that needs to be reviewed label Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

1 participant