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.

Sign up for GitHub

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

Jump to bottom

[Feature] FAQ Accordion not Accessible #199

Open
1 task done
Queen-codes opened this issue Oct 7, 2024 · 2 comments
Open
1 task done

[Feature] FAQ Accordion not Accessible #199

Queen-codes opened this issue Oct 7, 2024 · 2 comments
Labels
💻 aspect: code Concerns the software code in the repository 🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@Queen-codes
Copy link
Contributor

Queen-codes commented Oct 7, 2024 •
edited by TimidRobot
Loading

Problem

The FAQ section is not accessible while navigating with keyboard navigation alone. According to accessibility guidelines, all interactive elements should be fully navigable and operable using a keyboard. This is currently not the case.

Description

The FAQ section should be accessible for all users. The section needs to respond to keyboard inputs (e.g., tabbing through questions and using the enter or space keys to expand/collapse answers).

Additional Context

Implementation

  • I would be interested in implementing this feature.
@Queen-codes Queen-codes added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Oct 7, 2024
@Queen-codes Queen-codes changed the title [Feature] <Replace this with actual title> [Feature] FAQ Accordion not Accessible Oct 7, 2024
@TimidRobot TimidRobot added 🚧 status: blocked Blocked & therefore, not ready for work 🕹 aspect: interface Concerns end-users' experience with the software and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 7, 2024
@TimidRobot
Copy link
Member

🚧 status: blocked Blocked & therefore, not ready for work by:

@Queen-codes please add a comment to creativecommons/vocabulary/issues/55 about the need for accessibility in any according implementation

@Queen-codes
Copy link
Contributor Author

okay, got it. thank you @TimidRobot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💻 aspect: code Concerns the software code in the repository 🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Applications
Status: Backlog
WebDev
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TimidRobot @Queen-codes