Re: should we have a 2 year refresh cycle or a 4-5 year refresh cycle

That would work for me.

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 Wed, Oct 5, 2016 at 10:58 AM, White, Jason J <jjwhite@ets.org> wrote:

>
>
>
>
> *From:* Katie Haritos-Shea GMAIL [mailto:ryladog@gmail.com]
> *Sent:* Wednesday, October 5, 2016 10:00 AM
>
> There are options between 10 years and 2 years. I believe we need to take
> a well thought-out, more conservative stance, than two year view.
>
>
>
> Somewhere in between for new SC and a new standard – let’s say – 3
> (extremely optimistic), 4 (optimistic), or 5 years (but no more than 5).
>
> *[Jason] Hi Katie,*
>
> Would you be comfortable with the following, which I put forward in order
> to understand your position rather than as a proposal at this stage?
>
> ·        Commit to completing WCAG 2.1 within the next Charter period, in
> parallel with work on Silver.
>
> ·        Allow the Working Group to refine requirements (e.g., draft
> success criteria) that are unable to be included in WCAG 2.1. It would be
> decided near the end of the Charter period whether to seek approval to
> develop a subsequent WCAG 2.x release or whether to incorporate these
> requirements into Silver, depending on the state of progress in development
> of the latter.
>
> ·        Make no commitment now to developing any WCAG 2.x releases other
> than 2.1, and remove any and all reference in the Charter to biennial
> releases.
>
>
>
> ------------------------------
>
> 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 Wednesday, 5 October 2016 15:55:05 UTC