I like this idea of the AT being able to always ask for placeholder value but then making the decisions about how to present this information, to me that’s a similar hack to looking to the left/top/right of a form field for associated labels (it’s hardly full proof but is critical when nothing else is available).
The use cases that come to mind are: 1. First encountering the input field 2. Typing something in, but then needing to know the label, (was that first or last name?) 3. Encountering the input field with something typed in, (the first name field now has Sina typed in it, but the user needs to know what the placeholder was because there’s no label). I’m putting the various edge cases of typing something in, then erasing completely, all under #2. In all of these cases, as long as the AT can query and receive the placeholder text, is it not up to the AT whether to include this as part of the name or description of the field? it seems that the needed functionality is to always be able to query the placeholder text, not just when it is visible. Take care, Sina President, Prime Access Consulting, Inc. Twitter: @SinaBahram Company Website: http://www.pac.bz Personal Website: http://www.sinabahram.com Blog: http://blog.sinabahram.com From: [email protected] [mailto:[email protected]] On Behalf Of Richard Schwerdtfeger Sent: Friday, May 01, 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. a placeholder value of MMDDYY. The AT can always ask for the placeholder value. Rich Rich Schwerdtfeger Alexander Surkov ---05/01/2015 09:20:36 AM---So it seems like we all agree to introduce placeholder object attribute in IAccessible2. IA2 spec do From: Alexander Surkov <[email protected]> To: Joseph Scheuhammer <[email protected]> Cc: IAccessible2 mailing list <[email protected]>, Steve Faulkner <[email protected]> Date: 05/01/2015 09:20 AM Subject: Re: [Accessibility-ia2] placeholder mapping Sent by: [email protected] _____ So it seems like we all agree to introduce placeholder object attribute in IAccessible2. IA2 spec doesn't define markup mappings so it doesn't have to say about HTML5 placeholder and ARIA aria-placeholder attributes. Anyway, it doesn't prevent us from discussing it here :) So are there benefits in changing of current HTML5 placeholder mappings into accessible name and description? Btw, Joseph, I didn't really suggested to change GTK+ mappings :) On Thu, Apr 30, 2015 at 12:05 PM, Joseph Scheuhammer <[email protected] <mailto:[email protected]> > wrote: 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 name blank. [1] http://rawgit.com/w3c/aria/master/html-aam/html-aam.html#input-type-text-input-type-password-input-type-search-input-type-tel-input-type-email-input-type-url-and-textarea-element-accessible-name-calculation That's not backward compatible with the GNOME desktop (GTK+), where placeholder text is not mapped to an empty accessible name. Thus, there is now a mismatch between desktop widgets and widgets within a web page, on one desktop. -- ;;;;joseph. 'Array(16).join("wat" - 1) + " Batman!"' - G. Bernhardt - _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
