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
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 agree Steve?
Rich Schwerdtfeger
From: Joanmarie Diggs
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
Joseph, fyi: assuming Joanie and Alex agree on an object attribute, see
below.
Rich
Rich Schwerdtfeger
From: Steve Faulkner faulkner.st...@gmail.com
To: Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc: Joanmarie Diggs jdi...@igalia.com, IAccessible2 mailing list
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
