On Fri, May 1, 2015 at 11:41 AM, Joseph Scheuhammer <[email protected]>
wrote:
> On 2015-05-01 10:52 AM, Alexander Surkov wrote:
>
>> But I'm not sure I see reasoning of *not* mapping it into accessible
>> name/description the way what HTML5 spec suggests.
>>
>
> If the placeholder text is put in both the name and placeholder
> properties, then the same text might be presented twice, once as the name,
> and then echoed as the placeholder.
>
> To combat that, the AT could compare the two, and if identical, just
> present one of them.
>
true, not sure if there are better options.
>
> Or, the placeholder text could be only in the placeholder property, in
> which case, the AT immediately knows there is only placeholder text
> available. The AT could present it as the name, description, or
> placeholder; whatever is the best user experience.
I really concerned about backward compatibility, all users on Windows will
suffer from this approach. On the other hand I think of placeholder as
secondary concept that is not so important as accessible name. I assume
that some AT might not care to support placeholder at all, if it's exposed
as accessible name. At least this worked more or less well.
>
>
> --
> ;;;;joseph.
>
> 'Array(16).join("wat" - 1) + " Batman!"'
> - G. Bernhardt -
>
>
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
