Re:RE: AAA SC for coga

Jason we addressed all the know internationalization issues. Did you look at the issue in GitHub to see how they have been addressed? Do you have a specific issue that is not addressed?
All the best

Lisa Seeman

LinkedIn, Twitter



---- On Wed, 26 Jul 2017 00:02:47 +0300 jjwhite@ets.org wrote ----

I think WCAG needs to be fully internationalized, and I’m not convinced that the proposal is a significant advance upon 3.1.5, which is already at Level AAA. I agree, however, that the proposal has internationalization problems. My point is that I don’t think it’s acceptable to include a proposal without internationalizing it; the better option would be to wait for the next version of WCAG if the work cannot be undertaken now.

 

From: David MacDonald [mailto:david100@sympatico.ca] 
Sent: Tuesday, July 25, 2017 4:58 PM
To: White, Jason J <jjwhite@ets.org>
Cc: lisa.seeman <lisa.seeman@zoho.com>; W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
Subject: Re: AAA SC for coga

 

For the plain language SC  issues/41

 

We could possibly leverage the language at the front of 4.1.1 Where it says "In content implemented using markup languages, "

Perhaps we could say :"In content implemented using the English language"

Or

"In content implemented using latin based languages"

Or some other finite group of languages to which these "rules" are known to be effective

​.

 

I'm not a linguist and I don't know if these rules are actually always indicated, nor do I know to which languages they could be applied ... but this might be a way to get the SC into the standard at AAA​

 


Cheers,
David MacDonald
 
CanAdapt Solutions Inc.
Tel:  613.235.4902
LinkedIn 
twitter.com/davidmacd
GitHub
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.can-adapt.com%2F&data=02%7C01%7Cjjwhite%40ets.org%7C95e59c0e7f7d41be0a0908d4d39fdb01%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636366130903694242&sdata=9hNd%2FjJ0R5pa%2Bh%2B4SrIxn686nH7%2Bdr%2FF18Um%2FL5C6e8%3D&reserved=0
  
  Adapting the web to all users
            Including those with disabilities

 

If you are not the intended recipient, please review our privacy policy

 

On Tue, Jul 25, 2017 at 4:47 PM, David MacDonald <david100@sympatico.ca> wrote:

I think symbols could be a low hanging fruit for AAA

 

>A mechanism is available such that controls that are used to reach, or are part of, a critical service, and each instruction that contains important information that directly relates to a critical service, is preceded by a symbol or picture, which relates to the topic of the control or instruction.

 

Critical Service:

 

service that is needed to prevent significant harm, risk or loss such as: significant financial loss, illness, injury or deterioration in a patient's condition or effective loss of rights or freedoms

 

Note: I would drop "or effective loss of rights or freedoms".  I think that is an ever evolving term and not stable like the rest of the list. (perhaps it could be revised narrower to "allocation of self determination" or something similar.


Cheers,
David MacDonald
 
CanAdapt Solutions Inc.
Tel:  613.235.4902
LinkedIn 
twitter.com/davidmacd
GitHub
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.can-adapt.com%2F&data=02%7C01%7Cjjwhite%40ets.org%7C95e59c0e7f7d41be0a0908d4d39fdb01%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636366130903694242&sdata=9hNd%2FjJ0R5pa%2Bh%2B4SrIxn686nH7%2Bdr%2FF18Um%2FL5C6e8%3D&reserved=0
  
  Adapting the web to all users
            Including those with disabilities

 

If you are not the intended recipient, please review our privacy policy

 

On Tue, Jul 25, 2017 at 2:32 PM, White, Jason J <jjwhite@ets.org> wrote:

I think all of the proposals cited below, in their current form, have significant issues which are independent of the level assignment. Thus, I wouldn’t recommend any of them for inclusion in a draft as they currently stand, whether at level AAA or at another level.

 

However, it may be possible to turn one or more of them into a clearly written, focused, reliably testable proposal. I won’t try to guess which ones would be easiest to revise adequately;  in general, they have difficulties that lack obvious solutions. The difficulties aren’t related to the kinds of issues that determine whether a proposal belongs at Level AAA or not. Based on a quick reading, Minimize user Errors seems to be more precisely defined than the rest, but even it has issues that we’ve discussed in the past and which remain in what seems to be the latest version in GitHub.

 

It would be worth comparing with David MacDonald’s list of proposals that he thinks are on track to possible inclusion.

 

From: lisa.seeman [mailto:lisa.seeman@zoho.com] 
Sent: Tuesday, July 25, 2017 1:09 PM
To: W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
Cc: White, Jason J <jjwhite@ets.org>
Subject: AAA SC for coga

 

 

Hi Folks

 

 

please could you take a look and see if you think the following success criteria can get though at AAA? It wpould be realy helpful to have your feedback as soon as possible so we can prioritize what to put forward.

 

plain language - enhanced: issues/41

symbols: issues/50

provide support: issues/32

minamize user errors: issue 13

 

We also have support personlization at AAA which is also very important (issue 309)  

 

All the best

Lisa Seeman

LinkedIn, Twitter

 

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.

 

 


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.