Re: Failure technique F109 and password terms

Hi everyone,

I’ve created an updated version of the proposed F109:
https://github.com/w3c/wcag/pull/3174/files

I had to re-create the PR as it was from an external repo, so that is a branch in the W3C’s repo.

I also tackled the password/passcode/pass phrase wording, and Andrew’s comments from the previous PR.

Preview here: https://raw.githack.com/w3c/wcag/F109-accessible-auth/techniques/failures/F109.html

And special thanks to Dan Harper-Wain for putting forward this technique.

Kind regards,

-Alastair

--

@alastc / www.nomensa.com<http://www.nomensa.com/>




From: Lori Oakley

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

Lori


From: Niemann, Gundula

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

Received on Thursday, 4 May 2023 11:11:12 UTC