top of page
  • Writer's pictureBrent Payne

Required ARIA attributes must be provided

At Loud Interactive, we're deep-diving into the intricacies of web accessibility, particularly focusing on the critical importance of ARIA attributes. Our latest SEO audit unearthed a significant issue that could potentially hinder the user experience for individuals relying on assistive technologies.

Let's unpack this:

The Issue Explained: Web content and applications must be accessible to everyone, including those using screen readers and other assistive technologies. One key to achieving this is through ARIA (Accessible Rich Internet Applications) attributes, which provide essential information about the state and properties of web elements. However, we've found that certain elements are missing these required ARIA attributes, leading to a gap in the communication of information to users with disabilities.

Why This Matters: The absence of required ARIA attributes can critically impact users with disabilities by not conveying the role, state, or properties of an element. This oversight can lead to confusion, reduced functionality, and an overall frustrating web experience. Given that web accessibility is not just a recommendation but a legal requirement under various legislations (including WCAG 2.1 and 2.0 standards), it's imperative to address these gaps to ensure compliance and inclusivity.

How to Correct the Issue: To bridge this gap, it's crucial to add the missing ARIA attributes to the affected elements. This involves identifying which roles your web elements are serving and ensuring they have the appropriate states or properties defined. For instance, elements with widget roles require specific attributes like aria-valuemax or aria-checked to function correctly for users with assistive technologies.

Further Resources:

  • WAI-ARIA 1.1 Specifications: Explore the WAI-ARIA 1.1 guidelines for a comprehensive understanding of required states and properties based on roles.

  • Deque University: For an in-depth exploration of ARIA roles and attributes, consider enrolling in Deque University courses (subscription required).

  • GitHub Contribution: If you're interested in contributing to the broader community, consider participating in the development of axe-core on GitHub.

Incorporating ARIA attributes correctly is not just about ticking a box for compliance; it's about fostering an inclusive digital space that welcomes all users. As we continue our journey towards better web accessibility, we encourage web developers and content creators to utilize these resources and ensure their sites are accessible to everyone.

Stay informed and ahead of accessibility challenges with Loud Interactive. Together, we can build a more inclusive web.


Recent Posts

See All


bottom of page