From: Alastair Campbell [mailto:acampbell@nomensa.com] The problem is that the HTML5 list are tokens for attributes, not human readable names. That undermines the proposed solution in the SC, where the name can be a method of passing. Unless we have token/name pairs that are equivalent? [Jason] The problem here is that the concept of “conventional name” was never clarified. I’ve heard it argued in meetings that it should be a localized string of some kind that refers to the type of UI component based on the list found in the definition. All the proposal states is that the name can be programmatically determined, so a browser extension or other assistive technology can simply maintain an HTML5 token to localized name hash table for this purpose, and look up the name from the token. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Friday, 28 July 2017 13:04:25 UTC