Does text next to images meet alt-text requirements?

431
5
02-16-2026 07:11 AM
JeffreyThompson2
MVP Frequent Contributor

I have an application built in Experience Builder 1.11 with a set of filters. Each filter has an icon and text. My automated accessibility checker is flagging the icons for not having alt-text which isn't something I can add. Legally speaking, am I meeting the alt-text requirements anyway as the images are directly associated with text explaining them? 

JeffreyThompson2_0-1771254230032.png

 

GIS Developer
City of Arlington, Texas
5 Replies
Ed_
by MVP Regular Contributor
MVP Regular Contributor

Is this for ADA compliance?

Question | Analyze | Visualize
0 Kudos
JeffreyThompson2
MVP Frequent Contributor

Yes, ADA compliance within the United States. We are required to meet WCAG 2.1 standards to be in compliance.

GIS Developer
City of Arlington, Texas
0 Kudos
Ed_
by MVP Regular Contributor
MVP Regular Contributor

I guess it's becoming mandatory for every state now and getting deadlines.

Question | Analyze | Visualize
0 Kudos
CathyAlmberg
Occasional Contributor

From: Monica Ayala Diaz MAyalaDiaz@palmcoastgov.com
Sent: Tuesday, February 17, 2026 8:37 AM
Subject: Re: Esri Community: Daily Digest

Actually, the answer is yes because ExpB doesn't let you add alt-text except to the main widget in this case. So this would be a limitation of the ESRI ExpB application and would be flagged as such.

0 Kudos
fdeters
Frequent Contributor

It's hard to say for certain without seeing the code. But if an automated accessibility checker is flagging it, it's probably violating WCAG. Specifically, SC 1.1.1 Non-text Content specifies that decorative images (like your icons) need to be "implemented in a way that it can be ignored by assistive technology."

If you had full control over the code here, the best thing to do would be to hide the icons from assistive technology altogether by either marking them with `alt=""` or `aria-hidden="true"`. Unfortunately, this seems like an Esri-side bug. I would recommend reporting it to them.

It's also worth noting that even though this bug isn't under your control, the ADA Title II expansion rule specifies that jurisdictions are still required to meet WCAG 2.1 AA even if a third party provides the service:

The rule applies to web content that a state or local government provides or makes available. This includes when a state or local government has an arrangement with someone else who provides or makes available web content for them.

The good news is that this is a relatively low-impact WCAG violation. It might be a little annoying and initially confusing for a non-sighted user, but it's not obscuring information and there's a pattern that people will likely catch on to.

 

P.S. I am not a lawyer!

0 Kudos