Skip to content

Keyboard navigation inaccessible for sketch & Collections "Date Created" and "Date Updated" fields #3449

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

Open
Jatin24062005 opened this issue Apr 11, 2025 · 2 comments
Labels

Comments

@Jatin24062005
Copy link
Contributor

p5.js version

No response

What is your operating system?

None

Web browser and version

No response

Actual Behavior

On the Sketches/Collection page, while the headers Date Created and Date Updated are reachable using the Tab key, the actual date values for each sketch row are not focusable via keyboard navigation. This creates an accessibility barrier:

Keyboard users cannot tab to read the individual sketch date values.

The date fields are properly read by screen readers only when hovered or selected indirectly but not through keyboard focus.

These fields also lack a visible focus ring, making it harder for users who rely on visual indicators for navigation.

Image

Expected Behavior

  • Each sketch’s Date Created and Date Updated field should be reachable via keyboard (tabindex="0" or rendered as focusable elements) in both Section (Sketches & Collection).
  • These fields should include visible focus indicators.
  • Proper ARIA labels or semantic elements should be added for screen reader clarity.

Steps to reproduce

Steps:

  1. Open the "Sketches" or "Collection" page.
  2. Use the Tab key to navigate through the sketch list.
  3. Notice that while the sketch name and dropdown arrow are focusable, the Date Created and Date Updated values are not.
@karanBRAVO
Copy link
Contributor

Hey @Jatin24062005, can I work on this issue? Assign this to me :)

@Jatin24062005
Copy link
Contributor Author

@karanBRAVO You’re welcome to work on this, but I’m currently waiting for input from the maintainers, especially @raclim, since this issue might be addressed as part of the proposed GSoC project. So it could potentially be on hold for now.

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

2 participants