fix(field-input-purpose): replace email address with proper placeholder#5880
fix(field-input-purpose): replace email address with proper placeholder#5880
Conversation
|
📚 Branch Preview🔍 Visual Regression Test ResultsWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
Deployed to Azure Blob Storage: If the changes are expected, update the |
de29f3c to
c5a57c1
Compare
📚 Branch Preview Links🔍 First Generation Visual Regression Test ResultsWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
Deployed to Azure Blob Storage: If the changes are expected, update the |
c5a57c1 to
f1abfcd
Compare
Description
Updated the field-label documentation's Anatomy section example to use "Product name" instead of "Email address" to avoid using personal data fields in examples.
Motivation and context
The Email address field example violated WCAG 2.2 criterion 1.3.5 (Identify Input Purpose - Level AA) by using a personal data field without an autocomplete attribute. Rather than adding autocomplete to documentation examples, we changed to a non-personal data field ("Product name") which doesn't require autocomplete attributes.
This improves accessibility compliance in our documentation and provides a more universally applicable example.
Related issue(s)
SWC-1167Author's checklist
Reviewer's checklist
Manual review test cases