As per Alastair's suggestion I've removed the exceptions and as per Rachel's suggestion I've removed the financial/legal scoping. https://docs.google.com/document/d/1WhZAbswvPHs7A3stfqM_ATsaBHPeGbHtARcmaKMck1U/edit?usp=sharing Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613-806-9005 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, Apr 29, 2020 at 8:25 AM Alastair Campbell <acampbell@nomensa.com> wrote: > > a cold reading of what the SC currently says may make developers > wonder why it's literally just the progress once you're IN a process, but > not the actual control that may INITIATE a process? > > Because of this: > > If squinting hard enough, almost anything you look at on a > website/app can be argued to be a "process"? > > Ideally, yes, we would want to include initiation controls as well, but it > makes the scoping much harder. > > I think we could agree that 'browsing' is not a process, but other than > that it is a bit muddy until you are in a step-by-step process scenario. > Therefore, if we don't include the 'initiate' of a process it is much > clearer what is in scope. > > If you find any tricky examples, please do pop them into the examples doc. > > Cheers, > > -Alastair >
Received on Wednesday, 29 April 2020 12:51:19 UTC