Sailesh writes:
> Developers tasked with making content accessible should not
ordinarily delve into the depths of the accessible name computation
algorithm and rely on less preferred fallback mechanisms to compute a
name for an element.
+100!!!
JF
On Sat, Oct 22, 2022 at 8:22 AM Sailesh Panchang <sailesh.panchang@deque.com>
wrote:
> The HTML spec cannot be clearer and more explicit when it says:
> "The placeholder attribute represents a short hint (a word or short
> phrase) intended to aid the user with data entry when the control has
> no value. ... The placeholder attribute should not be used as an
> alternative to a label."
> The accessibility naming rules list attributes by order of
> preference. The items that occur later in the list are less preferred
> and simply meant as a fallback for AT users to help their users when
> good markup is absent.
> Developers tasked with making content accessible should not
> ordinarily delve into the depths of the accessible name computation
> algorithm and rely on less preferred fallback mechanisms to compute a
> name for an element.
> Thanks,
> --
> Sailesh Panchang
> Customer Success Strategist and Principal Accessibility Consultant
> Deque Systems Inc
> 381 Elden Street, Suite 2000, Herndon,
> VA 20170
> Mobile: 571-344-1765
>
--
*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |
"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"