E-mail List Archives
Re: using "label for=" on things other than inputs
From: Jonathan Avila
Date: Feb 22, 2016 11:27AM
- Next message: Cliff Tyllick: "Re: Word/PDF accessibility guide"
- Previous message: L Snider: "Re: Word/PDF accessibility guide"
- Next message in Thread: Steve Faulkner: "Re: using "label for=" on things other than inputs"
- Previous message in Thread: Jonathan Avila: "Re: using "label for=" on things other than inputs"
- View all messages in this Thread
> I take it nobody would see a failure of 1.3.1 for using 'label for=' on read-only text, disabled input, or a button that already has an accessible name via value - correct?
In the case that the label would override the button text and provide a different accessible name a violation could occur if that new accessible name did not sufficiently label the button. For example, a button with text color had a label of "foreground". Foreground would be the accessible name unless the button was wrapped within the label such as in <label for="a1"> Foreground <button id="a1">Color</button></label>.
Jonathan
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>
703.637.8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
- Next message: Cliff Tyllick: "Re: Word/PDF accessibility guide"
- Previous message: L Snider: "Re: Word/PDF accessibility guide"
- Next message in Thread: Steve Faulkner: "Re: using "label for=" on things other than inputs"
- Previous message in Thread: Jonathan Avila: "Re: using "label for=" on things other than inputs"
- View all messages in this Thread