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

Text situated in a Sidebar component can have screen reader issues #6999

Open
1 task done
elvis-iacobescu-sage opened this issue Oct 4, 2024 · 1 comment · May be fixed by #7052
Open
1 task done

Text situated in a Sidebar component can have screen reader issues #6999

elvis-iacobescu-sage opened this issue Oct 4, 2024 · 1 comment · May be fixed by #7052

Comments

@elvis-iacobescu-sage
Copy link

Description

I am trying to make content accessible to screen readers by tabbing. the sidebar has no buttons only texts and .

Reproduction

https://stackblitz.com/edit/parsium-carbon-starter-euvanf?file=index.html,src%2FApp.tsx

Steps to reproduce

  • open sidebar
  • Tabb with NVMA started
  • NVMA does not read content

JIRA ticket numbers (Sage only)

No response

Suggested solution

No response

Carbon version

142.9.0

Design tokens version

No response

Relevant browsers

Firefox, Chrome, Safari, Microsoft Edge, Other

Relevant OSs

Windows

Additional context

No response

Confidentiality

  • I confirm there is no confidential or commercially sensitive information included.
@elvis-iacobescu-sage elvis-iacobescu-sage added Bug triage Triage Required labels Oct 4, 2024
@nineteen88
Copy link
Contributor

FE-6839

@nineteen88 nineteen88 changed the title Sidebar component has accesibility proablems. Text situated in a Sidebar component can have screen reader issues Oct 8, 2024
tomdavies73 added a commit that referenced this issue Nov 1, 2024
…bbable

When any of the components' content containers overflow and contain no interactive
elements, the container will be added to the tabbing order and can be focused via
keyboard navigation to ensure their contents are accessible

fix #6999
tomdavies73 added a commit that referenced this issue Nov 1, 2024
…bbable

When any of the components' content containers overflow and contain no interactive
elements, the container will be added to the tabbing order and can be focused via
keyboard navigation to ensure their contents are accessible

fix #6999
tomdavies73 added a commit that referenced this issue Nov 7, 2024
…bbable

When any of the components' content containers overflow and contain no interactive
elements, the container will be added to the tabbing order and can be focused via
keyboard navigation to ensure their contents are accessible

fix #6999
tomdavies73 added a commit that referenced this issue Nov 12, 2024
…bbable

When any of the components' content containers overflow and contain no interactive
elements, the container will be added to the tabbing order and can be focused via
keyboard navigation to ensure their contents are accessible

fix #6999
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants