WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [External Sender] Title Attribute Issue

for

From: Birkir R. Gunnarsson
Date: Aug 30, 2019 10:11AM

This basically boils down to how screen readers handle accessible description.
There is no official guidance and no obvious answer to this.
If you always treat accessible description like accessible name and
expose it in all screen reader interactions, why have an accessible
description at all?
I'm not criticizing the concept, it is often very useful, just
pointing out that communicating accessible description to screen
reader users balancing relevancy and verbosity is tricky.
Most screen readerws err on the side of announcing accessible
description either when an element is focused with the tab key or when
the element triggers application/forms mode (e.g. text inputs), if you
have your auto application/forms mode set to on it doesn't matter how
you navigate to such elements, the mode is triggered from browse mode
or tab key navigation.
As to the specific problem, if the button text should be an accessible
name and accessible in all modes, go with aria-label over the title
attribute.
If the button has a descriptive accessible name but this info is
important enough to be available in all modes, use the good ol
visually hidden text to pad the visible label. If you do, make sure to
include necessary punctuation or whitespace to avoid screen reader
pronounciation problems.



On 8/30/19, Steve Green < <EMAIL REMOVED> > wrote:
> It depends on their level of proficiency. Experienced screen reader users
> are happy to tab between fields in forms. They know they are likely to miss
> any instructions that are in the form, but it's still quicker to tab through
> and fix any errors after. By contrast, inexperienced users are more likely
> to use virtual cursor mode because they worry more about the things they
> might miss.
>
> Steve
>
>
>