You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to do an audit of phone numbers in rich text editors to see which are not following the VA content guidelines.
Update
As of 12/1 it's been decided that the aria-label attribute is not going to be required in phone numbers going forward. The reasoning for this:
Pronunciation should not be forced. By using the aria-label attribute, we are forcing screen readers to pronounce the phone numbers how we think users want them to be read.
There are multiple articles and research supporting the idea that aria-label is not needed in this instance
Adding an aria-label to phone numbers is not convention, meaning that this behavior is not expected for all phone numbers across all sites throughout the web, but rather the opposite. Screen reader users expected to NOT have the attribute and expect the default behavior.
Next steps
Confirm the assumption/change with BVA at the next monthly meeting on 12/13
Figure out change management since editors (Especially the VAMC editors) have consistently been told that this is how they need to add phone numbers
Description
We want to do an audit of phone numbers in rich text editors to see which are not following the VA content guidelines.
Update
As of 12/1 it's been decided that the
aria-labelattribute is not going to be required in phone numbers going forward. The reasoning for this:aria-labelattribute, we are forcing screen readers to pronounce the phone numbers how we think users want them to be read.aria-labelis not needed in this instancearia-labelto phone numbers is not convention, meaning that this behavior is not expected for all phone numbers across all sites throughout the web, but rather the opposite. Screen reader users expected to NOT have the attribute and expect the default behavior.Next steps
<va-telephone>DS componentAcceptance Criteria
Team
Please check the team(s) that will do this work.
CMS TeamPublic WebsitesFacilitiesUser supportThe text was updated successfully, but these errors were encountered: