To help author more accessible content (according to ATAG 2.0) adding specific documentation on D8's accessibility will help people learn what is. In ATAG A.4.2 they outline in more detail best practices in "document the user interface, including all accessibility features."

So on the help pages here /admin/help/telephone we could add a section at the bottom, something like:

<h3>Accessibility</h3>

<p>Drupal 8 comes with the HTML5 telephone field which provides a semantic means to convey phone numbers to mobile devices and assistive technology devices.</p>

I expect that there are more elements that can be included.

CommentFileSizeAuthor
#8 document-atag-telephone-2308581-8.patch1.44 KBmgifford
#3 document-atag-telephone-2308581-3.patch1.47 KBmgifford
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

Hmmm... Take a look at the existing function telephone_help(), and consider the "About" / "Uses" structure of help. I do not think this section makes sense to add as suggested...

It sounds like the right thing to do would be to change the "Displaying telephone numbers as links" section in Uses, which currently says:

Telephone numbers can be displayed as links with the scheme name tel: by choosing the Telephone display format on the Manage display page. Any spaces will be stripped out of the link text.

Maybe adding this at the end:

This display format provides a semantic means to convey phone numbers to mobile devices and assistive technology devices.

Thoughts?

mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford commented

That would be fine as a mechanism to convey the accessibility improvements. It's pretty brief so having a whole section on this module would probably be overkill.

mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford commented
Status: Active » Needs review
FileSize
document-atag-telephone-2308581-3.patch1.47 KB

I think that much of it can be done simply by extending the existing description a bit.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented
Status: Needs review » Reviewed & tested by the community
Related issues: +#2202925: Move simple field types into Core/Field

This looks fine to me.

However, see #2202925: Move simple field types into Core/Field, which is most likely getting rid of this module entirely...

mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford commented

Should we postpone this for now?

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

Possibly... not sure if that other patch is going to go in or not. Let's leave that for another core maintainer to decide.

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
CreditAttribution: alexpott commented
Status: Reviewed & tested by the community » Needs work

This semantic markup to convey phone numbers will provide more convenient access to mobile devices and assistive technology devices seems a mouthful. Why not just This semantic markup improves the user experience on mobile and assistive technology devices?

mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford commented
Status: Needs work » Needs review
FileSize
document-atag-telephone-2308581-8.patch1.44 KB

Nice suggestion. I rerolled the patch.

yannickoo’s picture

yannickoo
Location Berlin
CreditAttribution: yannickoo commented
Status: Needs review » Reviewed & tested by the community

Looks good to me :)

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
CreditAttribution: alexpott commented
Status: Reviewed & tested by the community » Fixed

Committed d63702c and pushed to 8.0.x. Thanks!

  • alexpott committed d63702c on 8.0.x 
    Issue #2308581 by mgifford: Added Document accessibility features in...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.