Re: RE: What to work on next

 This makes sense to me also.

    On Monday, July 9, 2018, 4:24:35 PM EDT, White, Jason J <jjwhite@ets.org> wrote:  
 
 #yiv2535868485 #yiv2535868485 -- _filtered #yiv2535868485 {font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;} _filtered #yiv2535868485 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv2535868485 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv2535868485 #yiv2535868485 p.yiv2535868485MsoNormal, #yiv2535868485 li.yiv2535868485MsoNormal, #yiv2535868485 div.yiv2535868485MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:sans-serif;}#yiv2535868485 a:link, #yiv2535868485 span.yiv2535868485MsoHyperlink {color:blue;text-decoration:underline;}#yiv2535868485 a:visited, #yiv2535868485 span.yiv2535868485MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv2535868485 p.yiv2535868485msonormal0, #yiv2535868485 li.yiv2535868485msonormal0, #yiv2535868485 div.yiv2535868485msonormal0 {margin-right:0in;margin-left:0in;font-size:11.0pt;font-family:sans-serif;}#yiv2535868485 span.yiv2535868485EmailStyle19 {font-family:sans-serif;color:windowtext;}#yiv2535868485 .yiv2535868485MsoChpDefault {font-family:sans-serif;} _filtered #yiv2535868485 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv2535868485 div.yiv2535868485WordSection1 {}#yiv2535868485 _filtered #yiv2535868485 {} _filtered #yiv2535868485 {font-family:Symbol;} _filtered #yiv2535868485 {} _filtered #yiv2535868485 {font-family:Wingdings;} _filtered #yiv2535868485 {font-family:Wingdings;} _filtered #yiv2535868485 {font-family:Wingdings;} _filtered #yiv2535868485 {font-family:Wingdings;} _filtered #yiv2535868485 {font-family:Wingdings;} _filtered #yiv2535868485 {font-family:Wingdings;} _filtered #yiv2535868485 {font-family:Wingdings;}#yiv2535868485 ol {margin-bottom:0in;}#yiv2535868485 ul {margin-bottom:0in;}#yiv2535868485 
I support David’s analysis here. It seems to me that the difficulties encountered in extending WCAG 2.x are largely attributable to problems with its design and assumptions, which only Silver offers the opportunity to revisit.
 
  
 
I also agree with David that extending WCAG 2.x further would offer diminishing returns relative to the work required to do so, and that focusing on Silver would be a more productive effort. In addition, a possible WCAG 2.2 would have a very limited life-time, as it would probably be superseded by Silver within a few years – assuming that the schedule of the latter remains reasonable. I’m allowing for some slippage in that regard, but even so, I think the point still holds.
 
  
 
From: David MacDonald <david@can-adapt.com> 
Sent: Monday, July 9, 2018 3:00 PM
To: WCAG <w3c-wai-gl@w3.org>
Subject: What to work on next
 
  
 
As I know I don't think we've made a decision about what were working on next. It could be 2.2 or it could be silver. 
 
  
 
My thinking at this point  is that it might be best to go directly to Silver. Here's my reasoning: 
    
   - Currently in the 2.1 and 2.2 series we are basically locked into backwards compatibility constraints. The trouble we had getting new requirements into 2.1 will be repeated in 2.2. There are not a lot of issues that we tabled for 2.2 that we can successfully address any better than we could in 2.1. Perhaps we could do some more work on target size and a couple of things like that but it doesn't sound like we can do much more Until new assistive technologies come out or new specifications for instance for COGA.
   - Currently silver is under development and many of us could contribute to that effort if we weren't working on another interim version of WCAG. I think it would be better if we consolidate our efforts and work on the same next big problem which is fleshing out the plausibility of "measurability"  versus "testability"  and seeing if this is a viable way forward for the standard . 
   - I'd be more comfortable if we were all working together on the problem rather than in tandem where most of us can't give it more than a passing glance to what's going on with silver because we have our heads down on the current version.
 
I'm interested in other people's opinions.
 
  
 
Cheers,
David MacDonald
 
 
 
CanAdaptSolutions Inc.
 
Mobile:  613.806.9005
 
LinkedIn

 
twitter.com/davidmacd
 
GitHub
 
www.Can-Adapt.com
 
  
 
  Adapting the web toall users
 
            Including those with disabilities
 
  
 

If you are not the intended recipient, please review ourprivacy policy 

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.