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 <[email protected]> To: Alexander Surkov <[email protected]> Cc: IAccessible2 mailing list <[email protected]> Date: 04/27/2015 03:32 PM Subject: Re: [Accessibility-ia2] placeholder mapping Sent by: [email protected] Hey Alex. On 04/27/2015 12:58 PM, Alexander Surkov wrote: [...] > Also it's backward compatible approach. So does the following make sense? > > 1) If placeholder is used to label the control, i.e accessible name is > not provided otherwise then map placeholder (aria-placeholder) into > accessible name > 2) Expose placeholder as object attribute on the accessible object if it > wasn't used as name. What about changing 2) to just "Expose placeholder as object attribute."? In other words, independent of what happens in terms of the name mapping. That's what's happening -- and has been happening for several years -- in Gtk+ and WebKitGtk for native (non-ARIA) placeholder text. --joanie _______________________________________________ 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
