[Feature] Enhance Accessibility: Add ARIA Attributes to Local Content

[SisiVero]

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.

[harshsbhat]

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]

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.

[kris70lesgo]

@TimidRobot i have created a pr that fixes the issue . I would like you to review it . "Enhance accessibility by adding ARIA attributes to local content sections" #890

[TimidRobot]

This issue is now 🚧 status: blocked Blocked & therefore, not ready for work due to the complexity of implementation and the ongoing work to refactor the site to use the current Vocabulary design system.

@kris70lesgo your pull request (PR) is still under review and will be merged if the feedback is addressed.