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

[Feature] Introduce ARIA attributes to the website for accessibility #319

Open
1 task done
Murdock9803 opened this issue Jul 23, 2024 · 2 comments · May be fixed by #336
Open
1 task done

[Feature] Introduce ARIA attributes to the website for accessibility #319

Murdock9803 opened this issue Jul 23, 2024 · 2 comments · May be fixed by #336
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@Murdock9803
Copy link
Member

Murdock9803 commented Jul 23, 2024

Problem

The current code within the content of the page of the website lacks better accessibility features such as ARIA functionality - Accessibility Rich Internet Applications.

Description

By introducing these attributes, it would be easier for everyone to understand the contents on the website. Also, it will be good for screen readers too. We can include attributes such as role, aria-label, aria-hidden, etc..

Additional context

More context to WAI-ARIA

Work here should focus on the content areas of the pages, any ARIA improvements for the global header of footer should be addressed within the Vocabulary repository, as relevant Issues.

Implementation

  • I would be interested in implementing this feature.
@Murdock9803 Murdock9803 added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository labels Jul 23, 2024
@UtkershBasnet
Copy link

I'd like to work on this issue

@TimidRobot
Copy link
Member

@UtkershBasnet
Please see Contribution Guidelines — Creative Commons Open Source for how we manage issues and PRs.

We generally don't assign issues prior to resolution. Instead of asking for issues to be assigned, do the work and submit a pull request (PR). Even if multiple people submit PRs for the same issue, multiple ideas and implementations strengthen the final product.

@possumbilities possumbilities added 🏁 status: ready for work Ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Aug 16, 2024
@TimidRobot TimidRobot moved this to Backlog in WebDev Sep 10, 2024
@SisiVero SisiVero linked a pull request Oct 11, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

4 participants