Need an "AND" rather than "OR" in Purpose of controls

[DavidMacDonald]

In content implemented using markup languages, the conventional name of conventional form fields, conventional buttons or controls, or conventional links can be programmatically determined.

The "or conventional links" grammatically turns the lis into an OR list, in which ANY of the the requirements can be met rather than all of them.

I suggest we turn this into a list of AND"s

In content implemented using markup languages, the conventional name of:

• conventional form fields,
• conventional buttons or controls, and
• conventional links
  can be programmatically determined.

Otherwise, it could be like this:

In content implemented using markup languages, the conventional name of conventional form fields, conventional buttons or controls, and conventional links can be programmatically determined.

[joshueoconnor]

Relates to Purpose of Controls https://www.w3.org/TR/WCAG21/#purpose-of-controls

[johnfoliot]

+1 to the change.

[michael-n-cooper]

The wording of bullets above does not work grammatically. I could live with the bullets as follows:

In content implemented using markup languages, the conventional name of the following are programmatically determined:

• conventional form fields;
• conventional buttons or controls; and
• conventional links.

[jake-abma]

Shouldn’t it be “determinable” (instead of "determined"), as in:

In content implemented using markup languages, the conventional name of the following are programmatically determinable:

conventional form fields;
conventional buttons or controls; and
conventional links.

[jake-abma]

(or: can be programmatically determined)

[DavidMacDonald]

+1 To @michael-n-cooper friendly amendment.

with Jake's edit "can be programmatically determined" as per existing WCAG 2 SCs

I've amended the branch
346d372

[joshueoconnor]

Survey https://www.w3.org/2002/09/wbs/35422/Oct_17th_agwg/results

[mraccess77]

+1

[awkawk]

Merged change in pull #406 October 24