RE: new coga SC #31 ready to be submitted

From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com]
Sent: Tuesday, January 31, 2017 9:39 AM

It’s my guess that it extends SC 3.2.4 to things beyond “components”  to patterns like error messaging, etc.  Having a consistent method of error identification across a set of pages is example of things that isn’t clearly covered under SC 3.2.4 that could be covered here (in my opinion).
[Jason] I think that’s a well informed guess as to the intent and a good example, but we need a proposal that clearly states what it’s asking for, and which is clearly distinguished from 3.2.4.


________________________________

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.

________________________________