WebAIM - Web Accessibility In Mind

E-mail List Archives

WebAIM-Forum Digest, Vol 156, Issue 4

for

From: Jonathan Robert Pool
Date: Mar 4, 2018 12:16PM

> From: Steve Faulkner < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] "Naming Generic Landmarks" errors reported by Siteimprove extension
> Date: 3 March, 2018 at 12:13:06 PST
>
>> Yes, in this case that is an intended behavior, >and that's why I chose to
> use a title attribute.
>
> So it's information that's important enough to be displayed to mouse users
> but not to keyboard or touch users?
>
> Your intention is unclear to me.

Good question. It forces me to articulate my intention better.

In principle, I think that any user who wants to know more about a button, including what it does and what keypress(es) can substitute for it, should be able to find that out.

A hoverer gets that information. A screen-reader user does. But an unassisted keyboard navigator or touch user currently doesn't. So you're making me consider offering it somehow to those users, too. I'm wondering whether there are conventions for that, such as holding down the "?" key while the button is focal or pressing and holding the button on a touch display long enough to trigger a tooltip instead of activating the button. I think I've experienced the latter, but not the former.

Any thoughts would be appreciated.