, 2015 10:41 AM
To: Alexander Surkov
Cc: Joseph Scheuhammer; IAccessible2 mailing list; Steve Faulkner
Subject: Re: [Accessibility-ia2] placeholder mapping
The problem with the name computation is that:
If you use it to compute a name only and then type over it you lose the hint.
... e.g
Btw, Joseph, I didn't really suggested to change GTK+ mappings :)
Oh, sorry, I didn't mean to imply that. The point was that the mapping
for placeholder for GTK (desktop) widgets is inconsistent with widgets
in webpages, and that the HTML mapping spec is not backward compatible
with that.
On 2015-04-29 7:48 AM, Alexander Surkov wrote:
I support the idea that the browser should find a best match for
accessible name and description. Btw, current version of HTML a11y
spec agrees on it [1]. After all there's backward compatibility issue
If placeholder is exposed leaving accessible
To: Joseph Scheuhammer cl...@alum.mit.edu
Cc: IAccessible2 mailing list
accessibility-...@lists.linux-foundation.org, Steve Faulkner
faulkner.st...@gmail.com
Date: 05/01/2015 09:20 AM
Subject:Re: [Accessibility-ia2] placeholder mapping
Sent
Scheuhammer cl...@alum.mit.edu
Cc: IAccessible2 mailing list
accessibility-...@lists.linux-foundation.org, Steve Faulkner
faulkner.st...@gmail.com
Date: 05/01/2015 09:20 AM
Subject: Re: [Accessibility-ia2] placeholder mapping
Sent by: accessibility-ia2-boun...@lists.linuxfoundation.org
On 29/04/2015 12:08 AM, Joseph Scheuhammer wrote:
a few questions is aria-placeholder ever to be used as fallback for
accname/description calculation?
My position is that, yes, aria-placeholder text can be used as a
fallback for a name, but the decision should be left to the AT. The
On 30/04/2015 3:16 AM, Joanmarie Diggs wrote:
It's possible to have a name and description and placeholder.
True, but it's also possible to have multiple other things which would
normally get mapped to name or description. That's why we have
precedence rules. :)
Beyond that, because the
On 04/29/2015 08:35 PM, James Teh wrote:
Fair enough. We've tried to keep IA2 and ATK fairly closely synced to
unify things/make things easier, but if you've already made this choice
for ATK,
FWIW, it was made years ago and by several developers (which I point out
simply because this isn't
Hi Rich,
Joseph, fyi: assuming Joanie and Alex agree on an object attribute,
see below.
Based on reading the rest of the email, I believe the proposal is:
When @placeholder and @aria-placeholder are both present, and
@placeholder is non-empty, the user agents MUST expose the value of
Hi Steve,
On 2015-04-28 9:44 AM, Steve Faulkner wrote:
On 28 April 2015 at 14:33, Joseph Scheuhammer cl...@alum.mit.edu
mailto:cl...@alum.mit.edu wrote:
Thus, the text above regarding @placeholder vs. @aria-placeholder
belongs in the HTML-AAM.
gotcha,
a few questions is
Hi, Joanie. I'm fine with that. I suggested this to make it easier for AT
to detect whether placeholder is valuable as a placeholder but as long as
everybody is onboard I don't really mind, especially if the it was in
WebKit for a while.
On Mon, Apr 27, 2015 at 4:22 PM, Joanmarie Diggs
...@igalia.com
To: Alexander Surkov surkov.alexan...@gmail.com
Cc: IAccessible2 mailing list
accessibility-...@lists.linux-foundation.org
Date: 04/27/2015 03:32 PM
Subject:Re: [Accessibility-ia2] placeholder mapping
Sent by:accessibility-ia2-boun...@lists.linuxfoundation.org
On 04/27/2015 05:49 PM, Steve Faulkner wrote:
On 27 April 2015 at 22:40, Richard Schwerdtfeger sch...@us.ibm.com
mailto:sch...@us.ibm.com wrote:
I want to also consider HTML5.1 native host language semantics. If
we have an HTML5 checkbox I would think that the native placeholder
On 27 April 2015 at 22:40, Richard Schwerdtfeger sch...@us.ibm.com wrote:
I want to also consider HTML5.1 native host language semantics. If we have
an HTML5 checkbox I would think that the native placeholder attribute would
win, over aria-placeholder, as that text would be visible.
Do you
accessibility-...@lists.linux-foundation.org,
accessibility-ia2-boun...@lists.linuxfoundation.org, Alexander
Surkov surkov.alexan...@gmail.com
Date: 04/27/2015 04:52 PM
Subject:Re: [Accessibility-ia2] placeholder mapping
On 27 April 2015 at 22:40, Richard Schwerdtfeger
Hi.
In Firefox HTML placeholder attribute is mapped to accessible name if label
is not provided (either native or ARIA one). Otherwise it's ignored. There
are strong opinions that placeholder needs own mapping since it's separate
concept from the accessible name and AT want to treat it special
16 matches
Mail list logo
