Amend process definition to remove registration example - #3538

I agree it would have been better to have authentication as an example of a process (as compared to account registration). That said, I am not enthusiastic about including this as an erratum (since it is normative). It is not wrong that account registration is an example of a process.

it causes real confusion for the already confusing "accessible authentication" concepts. and while yes, it's a change to a normative part, it only changes the non-exhaustive examples within the definition

✅ Deploy Preview for wcag2 ready!

Name	Link
🔨 Latest commit	37e7479
🔍 Latest deploy log	https://app.netlify.com/projects/wcag2/deploys/6a8369f750f22b0008a459e6
😎 Deploy Preview	https://deploy-preview-3538--wcag2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Agree with Bruce from Nov 2023 - this is a normative change that doesn't feel like it is necessary. As an example, it isn't a problem to refer to one type of situation and doesn't limit applicability to other situations.

it isn't a problem

it does cause an apparent non-sequitur - see #3264 (comment)

it does cause an apparent non-sequitur - see #3264 (comment)

It is still a process, and it could be fully in-line with 3.3.8/9 - we have no idea what the Turing test is in the example.

It is still a process, and it could be fully in-line with 3.3.8/9 - we have no idea what the Turing test is in the example.

sure, it's a process, but 3.3.8/3.3.9 apply to authentication processes, which creation of a new account is not (which is the whole point of that discussion, which gets then muddied by account creation being listed as an example of a process)

so making a tiny tweak to the example provided (while not trying to imply that account creation isn't a process) removes a small stumbling block in understanding 3.3.8/3.3.9

sure, it's a process, but 3.3.8/3.3.9 apply to authentication processes, which creation of a new account is not (which is the whole point of that discussion, which gets then muddied by account creation being listed as an example of a process)

The process definition is to define "process" not "authentication process". the process definition is linked from ~4 SC and the 5.2.3 Complete processes.

It's worth noting that the text says "authentication process" but only the second (generic) term is linked, so I would not expect the process definition to be tailored to authentification or even necessarily include authentification.

to me the utility of this comes down to avoiding lengthy explanations for people who haven't grappled with the distinction between "authentication" and other uses of cognitive function tests elsewhere.

it avoid the run-around having to explain to people:

"these two SCs only apply to authentication. that's basically logging into an existing account."
"i looked at the definition of process, and it gives an example of creating a new account."
"ah, but that is only a general example of a process. see, for these SCs, it's only scoped to authentication processes, which that one example in the definition of process is not."

and yes, "process" is referenced by other SCs, but changing the non-exhaustive. informative example in the definition does not impact these other SCs in the slightest.

or, you know, we keep it all as is, and just always have to rerun through the conversation above with folks...because why should WCAG be easy :)

Discussed in last TF meeting. Agreed to move to the potential errata column for the next CfC

I think a registration or account creation process is still a valid example to include although I agree the word "registration" is likely to narrow. I'm not clear why both that and authentication cannot be listed.

Merging as per CFC resolution