WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Is use of <label> and title redundant?

for

From: Sailesh Panchang
Date: Nov 19, 2012 9:39AM

>ARIA also states that ARIA roles override native roles, which is what is
>implemented in browsers.
Yes I have noted that too and a link with role=button is exposed as a button.
So then is there a disconnect in the ARIA specs? I mean is the
recommendation not in sync with the intent?
Sailesh


On 11/19/12, Steve Faulkner < <EMAIL REMOVED> > wrote:
> Hi Sailesh,
>
>>I think I had previously expressed my concern about the logic stated in
>>HTML to Platform Accessibility APIs Implementation Guide.
>
> the API guide only reflects what is implemented in browsers in this regard.
>
> The API mappings and algorithms are distinct from the advice in ARIA about
> what authors should do.
>
> ARIA also states that ARIA roles override native roles, which is what is
> implemented in browsers.
>
> example:
>
> <button role=checkbox> is exposed as a checkbox not a button.
>
> whether authors are advised to do this is a different matter.
>
> regards
> Steve
>
>
>
> On 19 November 2012 15:18, Sailesh Panchang
> < <EMAIL REMOVED> >wrote:
>
>> Steve,
>> I think I had previously expressed my concern about the logic stated in
>> HTML to Platform Accessibility APIs Implementation Guide.
>> I see that the algorithm accords a higher order to ARIA attributesand
>> not the native HTML elements / attributes.
>> This is contrary to what the Intro to ARIA advises : use ARIA only
>> where native technology features are absent or inadequate.
>> So why should standard INPUT type=text with a proper LABEL with for-id
>> association be trumped by aria-labelledby attribute?
>>
>> One should use aria-labelledby in situations like a custom form
>> control that will not support LABEL with for-id technique.
>> Or, where multiple labels need to be associated with a form control
>> and browser/ATs do not support that well / uniformly.
>>
>> I agree ARIA attributes are very useful (as stated above) to relate
>> visually available content on the page with other elements like form
>> controls on the page.
>> But I do not see the benefit of placing off-screen content and, say,
>> using aria-describedby to relate that text to a form control as its
>> accessible-description when the good old title accomplishes the same.
>> And then according aria-describedby a higher status than the title.
>> Anyway the off-screen text is not available to non AT-users.
>> The title is at least available to mouse users besides AT users.
>> Thanks and regards,
>> Sailesh Panchang
>> www.deque.com
>>
>> Tel 703-225-0380 ext 105
>>
>>
>>
>>
>>
>>
>> On 11/19/12, Steve Faulkner < <EMAIL REMOVED> > wrote:
>> >>Sure, but if there's another completely valid, easy way to label an
>> > element that is not as buggy--namely, using a label!--why not use that
>> > method?
>> >
>> > I have encountered buggy screen reader behaviour with hidden label
>> elements
>> > in past. in the end you pick what you think works best.
>> >
>> > regards
>> > steve
>> >
>> > On 19 November 2012 14:42, GILLENWATER, ZOE M < <EMAIL REMOVED> > wrote:
>> >
>> >> Sure, but if there's another completely valid, easy way to label an
>> >> element that is not as buggy--namely, using a label!--why not use that
>> >> method?
>> >>
>> >> Zoe
>> >>
>> >> Zoe Gillenwater
>> >> Web Accessibility Technical Architect
>> >> AT&T Consumer Digital Experience
>> >>
>> >> o: 919-241-4083
>> >> e: <EMAIL REMOVED>
>> >>
>> >> 4625 Creekstone Dr | Durham, NC 27703
>> >>
>> >> This email and any files transmitted with it are AT&T property, are
>> >> confidential, and are intended solely for the use of the individual or
>> >> entity to whom this email is addressed. If you are not one of the
>> >> named
>> >> recipient(s) or otherwise have reason to believe that you have
>> >> received
>> >> this message in error, please notify the sender and delete this
>> >> message
>> >> immediately from your computer. Any other uses, retention,
>> >> dissemination,
>> >> forwarding, printing, or copying of this email is strictly prohibited.
>> >>
>> >>
>> >>