Accessibility issues with links

[Francois-XavierLa]

The link texts in newsletters’ callback actions are often not relevant (Learn more, Discover, Click here, Buy...).

Unfortunately, the link component doesn't allow users to add an aria-label attribute to make them accessible to users with disabilities.

Is there a way to create a custom link component?

By default, the editor should allow adding aria attributes to avoid accessibility issues. How can we report this need to the Adobe team for it to be addressed?

[Craig_Thonis · Accepted solution]

Hi Francois-Xavier. Please reach out to Campaign Support to report the issue and they will work to address the issue.

Regards,

Craig

[MeitMedia]

Hi @Francois-XavierLa ,

Adobe Campaign Classic's link component does indeed lack the flexibility to add an aria-label attribute directly, which can create accessibility issues for users relying on screen readers. However, there are a few approaches you can play with if it works for you:

• Custom HTML Links: You can manually insert HTML code with the aria-label attribute in your newsletters. Instead of using the default link component, you would use a custom HTML block to define the link, like so:

<a href="https://example.com" aria-label="Detailed description of the link action">Learn more</a>

         This approach might provide you with full control over the link structure and ensures it meets accessibility standards.

• Scripted Components: If you're working with custom scripting in Adobe Campaign Classic, you can create a scripted component that allows users to input both the visible text and the aria-label. This requires some development work to integrate the component into your template.

To have this issue formally addressed by Adobe, you can submit a feature request through the Adobe Experience Cloud support portal or reach out to your Adobe Customer Success Manager (CSM) if you have one. When submitting the request, it's crucial to emphasize the importance of accessibility and how the lack of aria-label support in the link component affects compliance with accessibility standards (e.g., WCAG 2.1). Providing real-world examples and detailing the impact on users with disabilities will strengthen your case and could expedite the implementation of this feature.

Best regards,

MEIT MEDIA (https://www.meitmedia.com)

Find us on LinkedIn

Contact Us: infomeitmedia@gmail.com

[Francois-XavierLa]

Thank you for the help. I'll explore the "Scripted Components" option, as the newsletter contributors don't have technical profiles and don't work with HTML.

[aggabhi]

Thanks @MeitMedia  for your help, helped me in my solution