E-mail List Archives
Re: usage of Abbreviation particularly on dropdowns
From: glen walker
Date: Mar 30, 2021 9:03AM
- Next message: Jonathan Avila: "Re: The importance of landmarks to screen readers?"
- Previous message: Joe Humbert (A11y): "Re: The importance of landmarks to screen readers?"
- Next message in Thread: None
- Previous message in Thread: Ramakrishnan Subramanian: "usage of Abbreviation particularly on dropdowns"
- View all messages in this Thread
If the *label* of the dropdown widget wasn't clear that it's a state list,
then it would fail 2.4.6 but the *contents* of the dropdown list are not
affected by 2.4.6.
And even if you were testing for AAA, 3.1.4 would not apply because the
normative definition of an abbreviation (
https://www.w3.org/TR/WCAG21/#dfn-abbreviations) says it's only a problem
when "the abbreviation has not become part of the language". In this case,
state abbreviations *are* part of the language. They have been in use for
a very long time. (If we're talking about US state names.)
On Mon, Mar 29, 2021 at 10:09 PM Ramakrishnan Subramanian <
<EMAIL REMOVED> > wrote:
> Dear Members,
> I have a question on usage of Abbreviation particularly on dropdowns.
> Whether the state names given as Abbreviation in a dropdown can be
> considered a violation of WCAG SC 2.4.6? Of course, Abbreviations are
> considered violation at the (AAA) Level. But I would like to know for
> the mentioned scenario can we mark Abbreviations under 2.4.6? or is it
> an Accessibility best practice?
>
>
>
> --
>
> Thanks and Regards
> Ramakrishnan
> > > > >
- Next message: Jonathan Avila: "Re: The importance of landmarks to screen readers?"
- Previous message: Joe Humbert (A11y): "Re: The importance of landmarks to screen readers?"
- Next message in Thread: None
- Previous message in Thread: Ramakrishnan Subramanian: "usage of Abbreviation particularly on dropdowns"
- View all messages in this Thread