Change for case where all fields are mandatory

[goetsu]

• add information to clarfy that when all fields mandatory this technique is just a best pratice not a requirement
• making test procedure applicable only when form contain both required and optional controls

Closes #1698
Closes #2357

[bruce-usab]

If merged, closes #1698

[patrickhlauke]

@bruce-usab if you add that to the PR's description/first comment, github will do this automagically (I just edited it to that effect)

[bruce-usab]

if you add that to the PR's description/first comment, github will do this automagically

Thanks! That was indeed the effect I was trying to invoke.

[bruce-usab]

Looks good to me, thanks!

[bruce-usab]

Closes #2357

[netlify]

❌ Deploy Preview for wcag2 failed.

Name	Link
🔨 Latest commit	a02e8a5
🔍 Latest deploy log	https://app.netlify.com/sites/wcag2/deploys/679cf2109b5aca0008f79ff2

[bruce-usab]

Added the closing </p> Ken spotted

[mbgower]

I'm a little leery of this change on its own. We've already spent quite a bit of time clarifying that the word "required" as used in Labels or Instructions means "needed".
So I'd like to pay a bit more attention to this technique and bring it in line with that, rather than this very simple change.

I'm also not sure I agree it is only a best practice.

[bruce-usab]

Discussed on backlog call 2/7 and @mbgower offered to make another pass. On call, had several examples where the context means there is no needed to mark fields as being required. Common example is login fields.