Re: Placeholder attribute an accessible name?

Hello everybody,

> The question isn't though if developers should or shouldn't. It's whether or not the behaviour of browsers to use the fallback (documented in the accessible name computation algorithm) to expose an accessible name counts as passing 4.1.2 Name, Role, Value. Nominally, I'd say it does. Whether it's good or bad practice is a separate discussion.

I completely agree when it comes to describing the status quo.

But we should consider how we can improve WCAG in the future to avoid that things that are meant to be a fallback can be a pass.

In this case the answer is stunningly obvious: Make the best way to implement an programmatical determinable text alternative an AAA criterion, solutions that would still be accessible for most people should be AA which influences many laws all over the world and make it absolutely necessary to implement some basic information.

Both - title and placeholder - should be a fail in any case and explicitly mentioned as one if they come alone. They’re not accessible to many people.

Also sighted people should be able to reach every information. More and more often I see informations that can exclusively revealed by people with assistive technology.

Most people already use a device with a touch screen and cannot access the value of the title attribute - also I sometimes find really good and even exclusive information in the value of the alt attributes.

Somehow this also should be addressed by WCAG. Ist absolutely necessary to provide programmatically determinable information that is connected with the labeled or described element - but this information must be accessible to everybody not only screenreader user.

Have a nice Sunday everybody,

Marc

Received on Sunday, 23 October 2022 10:18:42 UTC