Right, a good definition will plug that hole. Distinguishing between Accessible Name (which is defined elsewhere in our new SCs) verses Conventional Name ... Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd GitHub <https://github.com/DavidMacDonald> www.Can-Adapt.com <http://www.can-adapt.com/> * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html> On Mon, Jul 24, 2017 at 9:55 AM, White, Jason J <jjwhite@ets.org> wrote: > > > > > *From:* David MacDonald [mailto:david100@sympatico.ca] > *Sent:* Monday, July 24, 2017 8:57 AM > > >In content implemented using markup languages, the conventional name of > conventional user interface components can be programmatically determined. > (AA) > > > > The other thing to iron out with this is ensure that there is not a mixup > between "conventional name" as this intends it, and "ACCNAME" which is one > way to achieve it. > > *[Jason] The definition will, I think, take care of this point. We’re not > responsible for people who don’t read definitions and who then proceed to > misinterpret success criteria.* > > ------------------------------ > > 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 Monday, 24 July 2017 15:49:04 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:15 UTC