Re: Placeholder behavior

Use of placeholder without other visual label also raises concerns under SC.  3.3.2 in my opinion.

Jon


On Oct 6, 2014, at 3:30 PM, Steve Faulkner <faulkner.steve@gmail.com<mailto:faulkner.steve@gmail.com>> wrote:

hi sailesh,

although placeholder should not be used as a label it sometimes is. For the purpose of accessible name calculation in browsers placeholder is used as a fallback accessible name in accessibility APIs when other names sources are not provided.

here are some results of browser testing from late last year http://www.html5accessibility.com/tests/placeholder-labelling.html

--

Regards

SteveF
HTML 5.1<http://www.w3.org/html/wg/drafts/html/master/>

On 6 October 2014 20:08, Sailesh Panchang <spanchang02@yahoo.com<mailto:spanchang02@yahoo.com>> wrote:
JAWS 14/15 and NVDA  read the placeholder label even after entering text into the text field  in Firefox32 and IE11. VoiceOver in Ios 7 does not do so.
So for instance in the following code, the placeholder "Account number:"  though not visible, is announced by JAWS and NVDA even when some text is present in the field.
<p><input type="text" placeholder="Account Number:" size="7" /></p>
(Note: There is no text  outside the input element that funtcions  like a label).
NVDA does not read it  when arrowing through the content (i.e. out of forms mode) when there's data in the field.
HTML5 specs clearly states using placeholder as a label poses accessibility problems.
But thought I'll note this interesting behavior with screen readers.
Sailesh