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

[Bug]: List preview component should be free of axe core scan errors #33171

Closed
2 tasks done
kolaps33 opened this issue Oct 30, 2024 · 2 comments
Closed
2 tasks done

[Bug]: List preview component should be free of axe core scan errors #33171

kolaps33 opened this issue Oct 30, 2024 · 2 comments

Comments

@kolaps33
Copy link
Contributor

Component

List (Preview)

Package version

9.55.1

React version

18.3.1

Environment

System:
OS: Windows 11 10.0.22631
CPU: (22) x64 Intel(R) Core(TM) Ultra 7 165H
Memory: 40.92 GB / 63.64 GB
Browsers:
Edge: Chromium (127.0.2651.74)
Internet Explorer: 11.0.22621.3527

Current Behavior

There are errors throw by a11y insight for web tool (which use axe core as engine):
Image

Version of Accessibility insight for web:
Version 2.44.0 | Powered by axe-core 4.9.1

Expected Behavior

There should not be accessibility insight errors within the list component.

Reproduction

https://react.fluentui.dev/?path=/docs/preview-components-list--docs

Steps to reproduce

  1. Go to docsite https://react.fluentui.dev/?path=/docs/preview-components-list--docs
  2. run "FastPass" Accessibility insight for web
  3. verify the result

Are you reporting an Accessibility issue?

None

Suggested severity

Urgent - No workaround and Products/sites are affected

Products/sites affected

No response

Are you willing to submit a PR to fix?

yes

Validations

  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • The provided reproduction is a minimal reproducible example of the bug.
@smhigley
Copy link
Contributor

Yeah, the roles of List are not appropriate from an accessibility point of view. I'll take a look -- both the listbox/option version and the grid version don't look like they can support the proposed interaction & content model.

@george-cz
Copy link
Contributor

closing as duplicate of #33257

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants