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] Enhance Accessibility: Add ARIA Attributes to Local Content #831

Open
1 task
SisiVero opened this issue Oct 17, 2024 · 2 comments
Open
1 task
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@SisiVero
Copy link

SisiVero commented Oct 17, 2024

Problem

The local content within the code lack ARIA attributes to improve accessibility. While global content such as the footer and header have some ARIA attributes implemented, local content sections are missing them, which can result in inconsistent accessibility support across the page.

Description

To enhance accessibility for users with assistive technologies, ARIA attributes should be consistently applied to local content sections such as form elements, navigation within sections, and interactive components (buttons, links, etc.). This would help screen readers and other assistive technologies navigate and understand the content better, improving the user experience.

Adding ARIA attributes to local content aligns with accessibility best practices and ensures a better user experience for those using assistive technologies. This also brings consistency between the accessibility of global content (header, footer) and local content.

Alternatives

  • Continue without ARIA attributes for local content, which may lead to reduced accessibility.
  • Implement ARIA attributes only for new content, leaving existing sections as they are, but this could cause inconsistency across the site.
  • Conduct a full accessibility audit to identify missing ARIA attributes and apply them site-wide, including global and local content.

Additional context

  • [link to resources and related issues]

Implementation

  • I would be interested in implementing this feature.
@SisiVero SisiVero 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 17, 2024
@cc-open-source-bot cc-open-source-bot moved this to Triage in TimidRobot Oct 17, 2024
@TimidRobot TimidRobot changed the title [Feature]Enhance Accessibility: Add ARIA Attributes to Local Content [Feature] Enhance Accessibility: Add ARIA Attributes to Local Content Oct 21, 2024
@TimidRobot TimidRobot added help wanted Open to participation from the community 🏁 status: ready for work 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 💻 aspect: code Concerns the software code in the repository labels Oct 21, 2024
@TimidRobot TimidRobot moved this from Triage to Backlog in TimidRobot Oct 21, 2024
@TimidRobot TimidRobot moved this to Backlog in possumbilities Oct 21, 2024
@harshsbhat
Copy link

Hey, @TimidRobot I can work on this in a couple of days. Can you assign me? Since this still has a priority low I am guessing it is fine to delay it by 3-4 days

@TimidRobot
Copy link
Member

Hey, @TimidRobot I can work on this in a couple of days. Can you assign me? Since this still has a priority low I am guessing it is fine to delay it by 3-4 days

Please see Contribution Guidelines — Creative Commons Open Source for how we manage issues and pull requests (PRs).

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

For work program applicants, each can all list their own PRs on their application. It is the quality of work that is important, not whether it is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

3 participants