WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Is using aria-label to add alternative text - but no alt attribute still a WCAG fail?

for

From: L Snider
Date: Aug 27, 2024 6:56AM

My view is this, if you can do an alt, you have to do it. Reason is not
just for people who use screen readers, but also those of us with very poor
internet connections who can't view images because of the dial up speeds
(many still have these speeds or are on poor data). If not, then a label. I
go past WCAG, as it never considered poor internet connections in my view.

Cheers

Lisa

On Mon, Aug 26, 2024 at 2:29 PM Sailesh Panchang < <EMAIL REMOVED> >
wrote:

> Every documented technique generally states the situations it is suited
> for.
> So yes, one can assign a title attribute for every form control on the
> website and it will not result in a WCAG failure technically.
> But not using the label-for technique (H44) where a visible label is
> present will disadvantage some users who may need a larger clickable region
> in some situations. The aria-label or aria-labelledby will pass too but
> again that is not the situations for which these techniques are designed
> for.
> So also with alt for an image. Unless there are special circumstances that
> warrant the use of an aria-label for an HTML IMG element, the alt is the
> way to go.
> Where an element is exposed as an image with role attribute, one can use
> the aria-label to assign it a name for instance.
> The issue therefore is that accessibility consultants should point out
> situations where a technique is used inappropriately and point to the
> technique that makes most sense.
> Using ARIA is often done in order to appear fashionable, impress a boss etc
> or simply because the developer is uninformed without realizing the effect
> on end users. It also makes dev work more taxing especially for
> maintenance.
> I have seen lots of situations where aria-label is used to name links using
> redundant verbose text painful for SR users by overriding visible link
> text that is perfectly apt. Or, aria label to expose both column header and
> row header in a static data table in place of TH for row/column headers.
> Thanks
> Sailesh Panchang | +1 (571) 344-1765
> Technical Solutions Architect
>
> Email: <EMAIL REMOVED>
> Deque Systems Inc | - Accessibility for Good | www.deque.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Sat, Aug 24, 2024 at 5:35 PM Kevin Prince <
> <EMAIL REMOVED> >
> wrote:
>
> > It's not a compliance failure if the information is provided in alternate
> > means, and it is clear. So alt="" and an aria label would neet that.
> > It's horrible though ????
> >
> > Kevin Prince
> > Accessibility Consultant
> > Access Advisors
> >
> > Phone: +64212220638
> > Web: https://accessadvisors.nz/
> >
> >
> > If you have any access needs why not join our research panel where you
> can
> > be paid to help improve digital accessibility in New Zealand.
> > I work flexibly and am sending this message now because it suits my work
> > schedule. However I don't expect that you will read, respond to or action
> > it outside of your regular working hours.
> >