Update G195 - removal of last line of test (low contrast OK if focus ring > 2px thick)

[detlevhfischer]

Deletion of last line of test procedure that indicated that contrast below 3:1 is OK if the focus ring is more than 2px thick

Closes #3682

[bruce-usab]

Discussed on TF call 11/8 and moved to Ready for approval after Patrick offered to double check.

[netlify]

✅ Deploy Preview for wcag2 ready!

Name	Link
🔨 Latest commit	48f360f
🔍 Latest deploy log	https://app.netlify.com/sites/wcag2/deploys/6749f500aa8823000878956f
😎 Deploy Preview	https://deploy-preview-3686--wcag2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[mbgower]

@patrickhlauke and @detlevhfischer please see my comments #3682 . I believe we need to decide whether we are to maintain two versions of G195. Either way, we need more changes in the Test (unless we are intentionally exceeding the Non-text Contrast requirements). Also, if we decide not to apply this technique to 2.4.13 in 2.2, we need to make adjustments to the Understanding document to remove the mapping.

[mbgower]

@kfranqueiro I'm just bringing this one to your attention, as it may be relevant to your 2.1 update

[mbgower]

Discussed on the TF admin call.
I will do the following:

• rewrite the G195 test to be specific to meet Non-text Contrast (and focus visible)
• remove the reference to G195 in the Focus Apperance Understanding document
• investigate other techniques that attempt to meet both AA and AAA (e.g., G17 and G18)
• open a new issue to draft a new technique to meet Focus Appearance
• Consider the title and guidance in G195 and the new technique to ensure they are complementary but also distinctive

[alastc]

I agree with having two separate techniques:

• G195 is for WCAG 2.1, and we remove the focus-appearance aspects.
• G2xx for WCAG 2.2, which meets the focus-appearance one. Include a note at the top saying something like "This builds on G195 to cover Focus-Appearance".

This PR could be just for the first part, and separate the second one.

[mbgower]

@alastc as per the comments in the issue, I found that if we can do it, it actually makes more sense to extend the test to meet Focus Appearance. If necessary, we can sever the connections from 2.1, but I have now made the test include a check that it meets 1.4.11 requirements, so even though the technique exceeds 1.4.11, it could still stay as being sufficient.

[mbgower]

Suggested change

	<li>If Check #1 is true, all other checks are also true.</li>
	<li>If Check #1 is true, all other checks must also be true.</li>

[mbgower]

@mbgower to check history of G195 and merge the first to test steps into the preamble
For each user interface component on the page that should receive keyboard focus:

1. Check that the focus indicator or its background color has been modifed by the author

[bruce-usab]

Discussed on TF call 12-6, facilitators to discuss on a coordination call.