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

Axe violation for missing role on all-day event row in Week View #2714

Open
5 tasks done
malouro opened this issue Jan 22, 2025 · 0 comments
Open
5 tasks done

Axe violation for missing role on all-day event row in Week View #2714

malouro opened this issue Jan 22, 2025 · 0 comments
Labels

Comments

@malouro
Copy link
Contributor

malouro commented Jan 22, 2025

Check that this is really a bug

  • I confirm

Reproduction link

https://codesandbox.io/p/sandbox/react-big-calendar-example-forked-gv9kvv

Bug description

This may apply to other views, but I've only tested and verified within the Week view, and using the Axe DevTools extension in Chrome.

Regardless of whether there are any all-day events or not rendered in the all-day content row, the following WCAG violation is thrown when running an Axe scan on the week view of react-big-calendar:

Ensure elements with an ARIA role that require child roles contain them

Element Location: .rbc-row-content
<div class="rbc-row-content" role="row"><div class="rbc-row"></div><div class="rbc-row"></div></div>

The axe DevTools links out to this page for more information.

Any of the Storybook examples that already exist can showcase this, (but here's a sandbox where the Week view is the default view for quicker testing.](https://codesandbox.io/p/sandbox/react-big-calendar-example-forked-gv9kvv)

Let me know if any other information is needed for my issue report. Thanks!

Expected Behavior

No axe violations when running an accessibility scan

Actual Behavior

No response

react-big-calendar version

1.17.1

React version

18.2.0

Platform/Target and Browser Versions

Chrome

Validations

  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
  • Make sure this is a react-big-calendar issue and not an implementation issue

Would you like to open a PR for this bug?

  • I'm willing to open a PR
@malouro malouro added the bug label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant