Re: Meaning of phrases: "described to the user " or "provided to the user"

>>for dates I suggest that you do not use numbers — as these are often ambiguous between US and Europe.
>>I would suggest that you use the form     28-May-2016
No doubt about that. Most are aware of the different date formats. But the Web authors want this particular format from the intended audience.
That was not the point of the email. Nor the aria-errormessages attribute.
The issue as noted in the email that started this thread relates to the interpretation  of SC 3.3.1 / 3.3.3   and the usage of the phrases  in the subject line.
Thanks,
Sailesh

--------------------------------------------
On Sat, 5/28/16, Gregg Vanderheiden <gregg@raisingthefloor.org> wrote:

 Subject: Re: Meaning of phrases: "described to the user " or "provided to the  user"
 To: "Jason J White" <jjwhite@ets.org>
 Cc: "Sailesh Panchang" <sailesh.panchang@deque.com>, "GLWAI Guidelines WG org" <w3c-wai-gl@w3.org>
 Date: Saturday, May 28, 2016, 1:17 AM
 
 for dates I
 suggest that you do not use numbers — as these are often
 ambiguous between US and Europe.
 For example os    
 04-06-2016     April 6th or  June 4th ?
    
 I
 would suggest that you use the form    
 28-May-2016
 
 
 
 gregg
 
 
 
 On May 23,
 2016, at 12:45 PM, White, Jason J <jjwhite@ets.org>
 wrote:
 
 
 -----Original
 Message-----
 From: Sailesh Panchang
 [mailto:sailesh.panchang@deque.com]
 
 
 Is there an agreement on
 the statement:
 A text message,
 "Please enter the departure date in the correct
 format: MM-DD-YYYY" placed, say,
 next to the field conveying visual association
 passes
  3.3.1
 and 3.3.3 but fails SC 1.3.1 if it is not programmatically
 associated with
 the field?
 
 
 I don't know what there is
 agreement on, but I can point out that the aria-errormessage
 property was recently introduced into ARIA 1.1 to address
 this and similar scenarios. See the latest working draft for
 details, including an example.
 
 
 ________________________________
 
 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 Sunday, 29 May 2016 02:17:22 UTC