WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Tried to make it accessible; now it doesn't look good

for

From: JP Jamous
Date: Oct 14, 2018 8:02AM

Ah got your point now Glen. I misunderstood you pal.

I find the disabled="disabled" attribute to be interesting. Many folks refer
to it as deprecated or not semantically correct, yet it does work in all
browsers and ATs that I have tested.

I do agree with you Glen that if you want to disable a link, why include it
in the first place on the page. Set display: none; and when you want it to
appear set display: inline; That way both sighted and AT users benefit from
it.

In my humble opinion, having it there in the tab order disabled is extra
navigation overhead for screen reader users and keyboard only users.

Anyways, I am a big fan of Keep It Simple. The simpler the layout is, the
better the user experience. That is a part of inclusive design in a way,
where the UI works to the benefit of all users not just one type of users.



--------------------
JP Jamous
Senior Digital Accessibility Engineer
E-Mail Me |Join My LinkedIn Network
--------------------


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen
walker
Sent: Saturday, October 13, 2018 6:48 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Tried to make it accessible; now it doesn't look good

JP, yes, sorry I forgot to include that.

In addition to tabindex="-1", you either need to aria hide it or override
the keyboard handler to not let a selection navigate the link.

Setting aria-hidden="true" is the easy way to hide it so that JAWS will not
get to it. But if you still want it in the accessibility tree, and have it
announced disabled/inactive (aria-disabled="true"), then you'd need a
keyboard handler to filter out the events.

You can't set disabled="disabled" on a link because it's not valid html.
http://webaim.org/discussion/archives