Re: Identify Common Purpose - resolving issues

I'm OK with removing all non-html 5 autofill purposes and marking the SC at
risk awaiting implementation of AT that can make use of this during CR.
But I kind of feel like the engineers who hold their breath as the Space
Shuttle takes off, knowing that there are things to worry about.

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, Jan 10, 2018 at 9:59 AM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> Jason wrote:
>
> > if implementations are expected to emerge during the CR period, mark it
> as “at risk”.
>
>
>
> I believe they are, so that is what I suggested.
>
>
>
> -Alastair
>