WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Hidden text more robust than title?

for

From: Birkir R. Gunnarsson
Date: Jul 14, 2017 9:10PM

This is the dilemma we are always facing though.
Should we recommend that things are coded to standards, and file bugs
when an assistive technology application does not make it useful, or
should we code it around the behaviors of those applications to ensure
the best experience for the end users.

Obviously, the answer is basically both, but I think too often we
relent, ask developers to code around the application bugs, and then
fail to file bugs to have things corrected (myself included, I don't
file nearly enough bugs).
Our job is not only to make developers code around assistive
technology bugs, it is to encourage assistive technology vendors to
fix those bugs so that accessibility can become easier, simpler and
more cost effective.



On 7/14/17, Ryan E. Benson < <EMAIL REMOVED> > wrote:
>> That being said, I think the title attribute is the better way to go here.
>
> I have to disagree here. If you have <a href=-- title=-open a new
> window->text</a> Zoom Text will either only announce 'open a new window
> link-, or 'text open a new window link- on the beginner/verbose mode.
>
> --
> Ryan E. Benson
>
> From: Birkir R. Gunnarsson
> Sent: Friday, July 14, 2017 15:55
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Hidden text more robust than title?
>
> Exactly what Jon said.
>
> The title attribute is a valid source of accessible name, but is not
> persistent visible label.
> It could only be used to provide an accessible name to form fields
> visually identified by an adjacent field or part of a
> multi-part-input, or as a source of accessible name for a link or
> button identified visually with an icon.
>
> That being said, I think the title attribute is the better way to go here.
> You don't have to provide this info (unless you do with an icon) so it
> is supplementary to the link purpose. That is what the title attribute
> is intended for.
> If you place too much information into the linktext itself it becomes
> cumbersome and confusing.
> Also it is very bad pactice (not that you suggested it) to put hidden
> text wih instructions before the link text.
>
>
>
> On 7/14/17, Jonathan Avila < <EMAIL REMOVED> > wrote:
>>> It becomes a problem when we use it for a text input in place of an
>>> accessible name.
>>
>> The title attribute can be used as the accessible name for an input as
>> long
>> as it's accessibility supported. It has been very well support
>> historically
>> but I haven't confirmed its support on mobile recently.
>>
>> The accessible name calculation can be found here:
>> https://www.w3.org/TR/html-aam-1.0/#input-type-text-input-type-password-input-type-search-input-type-tel-input-type-url-and-textarea-element
>>
>> It would not however serve as a visible label for an input that was not
>> otherwise labelled because it is only available on mouse hover in most
>> browsers.
>>
>> Jonathan
>>
>> Jonathan Avila
>> Chief Accessibility Officer
>> Level Access, inc. (formerly SSB BART Group, inc.)
>> (703) 637-8957
>> <EMAIL REMOVED>
>> Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
>> Looking to boost your accessibility knowledge? Check out our free
>> webinars!
>>
>> The information contained in this transmission may be attorney privileged
>> and/or confidential information intended for the use of the individual or
>> entity named above. If the reader of this message is not the intended
>> recipient, you are hereby notified that any use, dissemination,
>> distribution
>> or copying of this communication is strictly prohibited.
>>
>>