From 52df79224658a2f5a22dc81f4ab635bf4f937f0a Mon Sep 17 00:00:00 2001 From: laurwill <104158104+laurwill@users.noreply.github.com> Date: Tue, 13 Aug 2024 08:33:13 -0400 Subject: [PATCH 1/3] Clarifying new aria guidance --- src/_includes/content/phone-numbers.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/_includes/content/phone-numbers.md b/src/_includes/content/phone-numbers.md index 6502405bc..9a2b7936d 100644 --- a/src/_includes/content/phone-numbers.md +++ b/src/_includes/content/phone-numbers.md @@ -11,10 +11,11 @@ Using the [Telephone component]({{ site.baseurl }}/components/telephone) will ap * Use a verb ahead of the number. Use "call" or "call us at..." for phone numbers and "text" or "text us at" for text numbers. * When a phone number has (TTY: 711) included, it should be formatted in parenthesis directly following the phone number. Example: 866-440-1238 (TTY: 711) or 866-440-1238, ext. 4 (TTY: 711) -### Links -* Hyperlink all phone numbers, including TTY numbers. It’s not a requirement to link the "call" or "text" verb that precedes the number. We do however include "TTY" in the link and aria label to make it clear that it's specifically for TTY so that users who need the service see it and so those who do not do not unintentionally call a TTY number. +### Links and aria +* Hyperlink all phone numbers, including (TTY: 711). Include "TTY:" in the link. Don't link the "call" or "text" verb that precedes the number. +* **New guidance as of August 2024:** You no longer need to use aria on phone numbers or TTY. This shift came out of evolving accessibility guidance for AT users. Teams should stop adding aria to phone numbers and TTY in new content, but the shift will take time to implement on existing content. If you have questions, contact Sitewide CAIA team. -If for some reason you cannot use the Telephone component, you are responsible for meeting the same formatting and accessibility guidance when creating links to phone numbers. +**Note:** If for some reason you cannot use the Telephone component, you are responsible for meeting the same formatting and accessibility guidance when creating links to phone numbers. ### Don't use vanity phone numbers in body copy We don’t use vanity phone numbers in body copy, as it adds visual noise and is not helpful to screen readers. We use and hyperlink only the numeric phone number in body copy. From f48b8a3c68aadd8507dc172c0343a2a50c114590 Mon Sep 17 00:00:00 2001 From: Megan Zehnder <72934749+megzehn@users.noreply.github.com> Date: Thu, 15 Aug 2024 12:19:13 -0500 Subject: [PATCH 2/3] Update phone-numbers.md spelled out CAIA and AT --- src/_includes/content/phone-numbers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_includes/content/phone-numbers.md b/src/_includes/content/phone-numbers.md index 9a2b7936d..dfda5ef5f 100644 --- a/src/_includes/content/phone-numbers.md +++ b/src/_includes/content/phone-numbers.md @@ -13,7 +13,7 @@ Using the [Telephone component]({{ site.baseurl }}/components/telephone) will ap ### Links and aria * Hyperlink all phone numbers, including (TTY: 711). Include "TTY:" in the link. Don't link the "call" or "text" verb that precedes the number. -* **New guidance as of August 2024:** You no longer need to use aria on phone numbers or TTY. This shift came out of evolving accessibility guidance for AT users. Teams should stop adding aria to phone numbers and TTY in new content, but the shift will take time to implement on existing content. If you have questions, contact Sitewide CAIA team. +* **New guidance as of August 2024:** You no longer need to use aria labels on phone numbers or TTY. This shift came out of evolving accessibility guidance for people who use assistive technology. Teams should stop adding aria labels to phone numbers and TTY in new content, but the shift will take time to implement on existing content. If you have questions, contact the Sitewide Content, Accessibility, and Information Architecture (CAIA) team. **Note:** If for some reason you cannot use the Telephone component, you are responsible for meeting the same formatting and accessibility guidance when creating links to phone numbers. From e912837cd38fc540c2443d558a855a44e7ebcb9a Mon Sep 17 00:00:00 2001 From: Megan Zehnder <72934749+megzehn@users.noreply.github.com> Date: Fri, 30 Aug 2024 11:50:35 -0400 Subject: [PATCH 3/3] Update phone-numbers.md added example to aria label --- src/_includes/content/phone-numbers.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/_includes/content/phone-numbers.md b/src/_includes/content/phone-numbers.md index dfda5ef5f..fc49eb23f 100644 --- a/src/_includes/content/phone-numbers.md +++ b/src/_includes/content/phone-numbers.md @@ -12,7 +12,8 @@ Using the [Telephone component]({{ site.baseurl }}/components/telephone) will ap * When a phone number has (TTY: 711) included, it should be formatted in parenthesis directly following the phone number. Example: 866-440-1238 (TTY: 711) or 866-440-1238, ext. 4 (TTY: 711) ### Links and aria -* Hyperlink all phone numbers, including (TTY: 711). Include "TTY:" in the link. Don't link the "call" or "text" verb that precedes the number. +* Hyperlink all phone numbers, including (TTY: 711). Include "TTY:" in the link. Don't link the "call" or "text" verb that precedes the number. +Example: ` 202-123-1234 (TTY: 711)` * **New guidance as of August 2024:** You no longer need to use aria labels on phone numbers or TTY. This shift came out of evolving accessibility guidance for people who use assistive technology. Teams should stop adding aria labels to phone numbers and TTY in new content, but the shift will take time to implement on existing content. If you have questions, contact the Sitewide Content, Accessibility, and Information Architecture (CAIA) team. **Note:** If for some reason you cannot use the Telephone component, you are responsible for meeting the same formatting and accessibility guidance when creating links to phone numbers.