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]> 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
