E-mail List Archives
Re: Tried to make it accessible; now it doesn't look good
From: JP Jamous
Date: Oct 14, 2018 8:02AM
- Next message: Patrick H. Lauke: "Re: Tried to make it accessible; now it doesn't look good"
- Previous message: Mark Rogers: "Re: Tried to make it accessible; now it doesn't look good"
- Next message in Thread: Patrick H. Lauke: "Re: Tried to make it accessible; now it doesn't look good"
- Previous message in Thread: Mark Rogers: "Re: Tried to make it accessible; now it doesn't look good"
- View all messages in this Thread
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
--------------------
- Next message: Patrick H. Lauke: "Re: Tried to make it accessible; now it doesn't look good"
- Previous message: Mark Rogers: "Re: Tried to make it accessible; now it doesn't look good"
- Next message in Thread: Patrick H. Lauke: "Re: Tried to make it accessible; now it doesn't look good"
- Previous message in Thread: Mark Rogers: "Re: Tried to make it accessible; now it doesn't look good"
- View all messages in this Thread