RE: Failure technique F109 and password terms

Yes, I believe that consistency in wording to create more understandable guidelines.

Lori
Lori Oakley
CX Service Accessibility Lead
[Oracle_Service_rgb]



From: Niemann, Gundula <gundula.niemann@sap.com>
Sent: Tuesday, May 2, 2023 10:37 AM
To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: [External] : Failure technique F109 and password terms

Hello,

in
New Failure Technique F109 for Issue #1918 Accessible Authentication needs better techniques by dan-hw * Pull Request #2990 * w3c/wcag * GitHub<https://urldefense.com/v3/__https:/github.com/w3c/wcag/pull/2990/files*diff-540118c56fc3e16ad630781640b93b68166e7deed892b0a1b11503d049869aa6R8__;Iw!!ACWV5N9M2RV99hQ!PBuCQVjt1PqQIAyw3pkk1GfbItWxy6acnCIVwqK5ZZy6md3UBDVP16p1wrJECAiQjiS3dV3vURPhA3LzYHR8UD438g$>
I looked up which terms I found Tuesday May 2 towards the end of our meeting.

This is what I found:


  *   Title:  password in "<title>Failure of Success Criterion 3.3.8 and 3.3.9 due to forcing transcription of individual password characters</title>"
  *   line 5: passphrase in "<h1>Failure of Success Criterion 3.3.8 and 3.3.9 due to forcing transcription of individual passphrase characters</h1>"
  *   line 8: password or passcode
  *   later same line: Password
  *   later in same line: password or passcode
  *   line 12: password
  *   line 15: passcode
  *   line 16: password
  *   line 23: password or passcode
  *   line 124: Password in "Failure of Success Criterion 3.3.8 and 3.3.9 due to forcing transcription of individual password characters"

So it does not seem to be fully consistent.
Do you agree to harmonize it?

Best regards,
Gundula
----------
Dr. Gundula Niemann
SAP PE UX Accessibility
SAP SE