WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: glen walker
Date: Oct 14, 2018 12:43PM

I tend to shy away from html that is not compliant. Even if disabled
worked on a link, it is not valid html and will fail the
https://validator.w3.org/nu validator, and thus fail WCAG 4.1.1 (maybe).

I say "maybe" fail 4.1.1 because if you go by the letter of the law, 4.1.1
doesn't say anything about invalid attributes, just about opening and
closing tags, duplicate IDs, or duplicate attributes.

On Sun, Oct 14, 2018 at 9:12 AM Patrick H. Lauke < <EMAIL REMOVED> >
wrote:

> On 14/10/2018 15:02, JP Jamous wrote:
>
> > 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.
>
> A link with the disabled attribute still gets focus and can be activated
> as normal in Firefox, Chrome, Edge using NVDA, JAWS and Narrator. The
> only browser where I've seen links with disabled="disabled" acting as
> actually disabled links is IE11 (and there the behavior is non-standard,
> as disabled is not a valid attribute for links).
>
> P
> --
> Patrick H. Lauke
>