Add ARIA Label to Teaser Component and all CORE Components missing it | Community
Skip to main content
Level 2
October 17, 2025
Investigating

Add ARIA Label to Teaser Component and all CORE Components missing it

  • October 17, 2025
  • 2 replies
  • 101 views
Request for Feature Enhancement (RFE) Summary: AEM Core components should have common and generic features, including accessibility. It appears that ARIA Attributes are not implemented in AEM Core Components

Teaser Component
Looking at AEM's teaser component documentation, which showcases screenshots from author, the only accessibility field Adobe have is for the "alt" property.

• Teaser Component (https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/wcm-components/teaser)

When I look at Adobe example output (the Markup tabs under each section) and look at the sections with anchor links, I do not see any ARIA attributes either.

• AEM Core Components - Example Output - Teaser Component (https://aemcomponents.dev/content/core-components-examples/library/core-content/teaser.html)

Button Component
On the other hand, looking at AEM's button component documentation, Adobe DO provide an aria-label field for authoring.

• Button Component (https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/wcm-components/button)

When I look at Adobe example output and look at the anchor links here, I still do not see any ARIA attributes.

• AEM Core Components - Example Output - Button Component (https://aemcomponents.dev/content/core-components-examples/library/core-content/button.html)

My Conclusion
I think that AEM put in the ARIA support for the button as a way to resolve common accessibility issues with HTML buttons, but Adobe has no broader solution for accessibility.

I am requesting Adobe to add properties required for Accessibility to the AEM Core Components
Use-case: Accessibility
Current/Experienced Behavior: No capability to add ARIA
Improved/Expected Behavior: Able to author ARIA label
Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS
Customer-name/Organization name: Lexmark, a Xerox Subsidiary
Screenshot (if applicable):  
Code package (if applicable):  

2 replies

kautuk_sahni
Community Manager
Community Manager
March 11, 2026

Thanks for proposing this idea. This has been reported to the engineering under the internal reference SITES-41723. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.

Kautuk Sahni
kautuk_sahni
Community Manager
Community Manager
March 11, 2026
NewInvestigating
Kautuk Sahni