Skip to content

Accessibility focus border missing on Settings components. #3448

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 · 0 comments · May be fixed by #3474
Open

Accessibility focus border missing on Settings components. #3448

Jatin24062005 opened this issue Apr 11, 2025 · 0 comments · May be fixed by #3474
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

In the p5.js Web Editor Settings, several interactive UI components across both General Settings and Accessibility tabs do not show a visible focus ring (blue outline) when navigating using the keyboard (e.g., Tab key).
Affected components:
General Settings tab:

  • Autosave
  • Autoclose Brackets and Quotes
  • Autocomplete Hinter

Accessibility tab:

  • Line numbers toggle
  • Lint warning sound options (On, Off, Preview)
  • Plain-text and Table-text checkboxes for Accessible canvas

Image

Image

Expected Behavior

All interactive elements (toggles, buttons, checkboxes, etc.) should have a visible focus indicator to support keyboard users and other accessible users.

Steps to reproduce

Steps:

  • Open the p5.js Web Editor
  • Open the Settings (gear icon)
  • Press Tab to navigate through the controls

Notice that while some elements like the Text Size buttons show a blue focus ring, others (listed above) show no visible indication of focus

// Paste your code here :)

@yugalkaushik yugalkaushik linked a pull request May 4, 2025 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant