E-mail List Archives
Re: Name, Role, Value and Labels or Instructions techniques...
From: _mallory
Date: Mar 31, 2015 2:01AM
- Next message: Patrick H. Lauke: "Re: Name, Role, Value and Labels or Instructions techniques..."
- Previous message: Graham Armfield: "Re: WordPress -- accessible share widget plugin"
- Next message in Thread: Patrick H. Lauke: "Re: Name, Role, Value and Labels or Instructions techniques..."
- Previous message in Thread: Gunderson, Jon R: "Re: Name, Role, Value and Labels or Instructions techniques..."
- View all messages in this Thread
On Mon, Mar 30, 2015 at 02:38:05PM +0000, Gunderson, Jon R wrote:
> Sean,
>
> In terms of the ARIA specification and I believe the HTML5.1 specification, the TITLE attribute will be part of the accessible name calculation, usually as a last resort if no other means is available.
>
> I feel the way you do, that when there are other "better" ways to do something (e.g. LABEL element) they should be used, but alias WCAG 2.0 is not about the "best" way, it is about "some" way to meet the accessibility requirement.
>
This whole thread makes no sense to me. If titles are inaccessible
to keyboard and speech-to-text users, how can this count as
"accessible"? Because a *screen reader* can access it?
I understand not everyone has the criteria of "must be generally
accessible" and instead need to meet specific WCAG requirements,
but I thought the whole point of WCAG was to help people build
things that worked, for *people*.
extremely horribly confused,
_mallory
- Next message: Patrick H. Lauke: "Re: Name, Role, Value and Labels or Instructions techniques..."
- Previous message: Graham Armfield: "Re: WordPress -- accessible share widget plugin"
- Next message in Thread: Patrick H. Lauke: "Re: Name, Role, Value and Labels or Instructions techniques..."
- Previous message in Thread: Gunderson, Jon R: "Re: Name, Role, Value and Labels or Instructions techniques..."
- View all messages in this Thread