fix(field-input-purpose): replace email address with proper placeholder #5880
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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