W3C home > Mailing lists > Public > site-comments@w3.org > March 2021

Re: Link purpose examples

From: Shawn Henry <shawn@w3.org>
Date: Thu, 25 Mar 2021 12:31:10 -0500
To: john.cavano@deltacollege.edu
Cc: "site-comments@w3.org" <site-comments@w3.org>, "'wai@w3.org'" <wai@w3.org>
Message-ID: <c8ff725d-844d-6f3a-c867-a8d82662d5ed@w3.org>
Hello John,

Thank you for taking the time to write, and for your thoughtful input.

It would be most helpful if you would submit your comment directly to the Accessibility Guidelines Working Group (AG WG), the group that maintains that page. Options for submitting comments, in preferred order:
* Open a new GitHub issue via https://github.com/w3c/wcag/issues/new
* Submit the online form https://www.w3.org/WAI/WCAG20/comments/understanding.php
* Send in e-mail to public-comments-wcag20@w3.org

Note that AG WG is processing many comments, and it might be a while before they get to your comment.

If you would like to get more perspectives (before or after you submit your comment to AG WG), you are welcome to send your questions to the public WAI Interest Group discussion list. You can search the mailing list archives, to get a feel for the list, through: http://lists.w3.org/Archives/Public/w3c-wai-ig/

You can join the mailing list and post questions by following the instructions about the Discussion List under:
     https://www.w3.org/WAI/about/groups/waiig/#mailinglist

Best regards,
~ Shawn
<http://www.w3.org/People/Shawn/>


> Begin forwarded message:
>
> *From: *John Cavano <john.cavano@deltacollege.edu <mailto:john.cavano@deltacollege.edu>>
> *Subject: **Link purpose examples*
> *Date: *20 March 2021 at 01:03:16 CET
> *To: *"site-comments@w3.org <mailto:site-comments@w3.org>" <site-comments@w3.org <mailto:site-comments@w3.org>>
> *Resent-From: *site-comments@w3.org <mailto:site-comments@w3.org>
> *Archived-At: *<https://www.w3.org/mid/BYAPR03MB39602CEACA32A89461BFCB838A6A9@BYAPR03MB3960.namprd03.prod.outlook.com <https://www.w3.org/mid/BYAPR03MB39602CEACA32A89461BFCB838A6A9@BYAPR03MB3960.namprd03.prod.outlook.com>>
> *Message-Id: *<BYAPR03MB39602CEACA32A89461BFCB838A6A9@BYAPR03MB3960.namprd03.prod.outlook.com <mailto:BYAPR03MB39602CEACA32A89461BFCB838A6A9@BYAPR03MB3960.namprd03.prod.outlook.com>>
>
> Hello,
>
> Would you please edit or clarify two of the examples for stating link purpose? I'm referring to this page: https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html <https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html>. I found this page while assisting a college faculty member who was editing their Canvas course, so thank you for creating it!
>
> There are two examples that I have questions about:
>
>  *
>     *A list of book titles*
>     A list of books is available in three formats: HTML, PDF, and mp3 (a recording of a person reading the book). To avoid hearing the title of each book three times (once for each format), the first link for each book is the title of the book, the second link says "PDF" and the third says, "mp3."
>  *
>     *News article summaries*
>     A Web page contains a collection of news articles. The main page lists the first few sentences of each article, followed by a "Read more" link. A screen reader command to read the current paragraph provides the context to interpret the purpose of the link.
>
> For the list of books, I think the title should still be in the link name, such as after the format type. Otherwise, a screen reader user using a links list might get confused about which format is referring to which book. Placing the format type first would allow the user to quickly hear the type and then move to the next link without having to listen to the whole title, but they could still confirm they were on the correct title if they listened to it.
>
> For the news articles, I think it would be confusing to hear in the links list, "read more", "read more" without hearing which article the "read more" related to. As a sighted user, I might be biased about what a blind user might need, and maybe not everyone uses a links list in this manner, but I'm basing my understanding on working with a blind college student.
>
> Could I suggest editing the following examples?
>
>  *
>     *A list of book titles*
>     A list of books available in three formats: HTML, PDF, and mp3 (a recording of a person reading the book). Help differentiate between the formats by naming each link with the format before the title of the book, such as "(HTML) [Book Title]", "(PDF) [Book Title]" and "(mp3) [Book Title]".
>  *
>     *News article summaries*
>     A Web page contains a collection of news articles. The main page lists the first few sentences of each article, followed by a "Read more" link.. Include the article title after "read more" in the link name to help differentiate links in a screen reader links list, such as "Read more about [Title of Article]". 
>
> My suggestions will probably require discussion and user testing to determine if they are actually useful for most people. I really appreciate your work on this topic and on accessibility overall. Thank you!
>
> *John Cavano, OTR/L, ATP *
> *Associate Professor / Assistive Technology *
> San Joaquin Delta College
> john.cavano@deltacollege.edu <mailto:john.cavano@deltacollege.edu>
> Google Voice: (209) 213-2936
> Desktop Phone: (209) 954-5151 ext 6106 

--
Coralie Mercier  -  W3C Marketing & Communications - https://www.w3.org <https://www.w3.org>
mailto:coralie@w3.org <mailto:coralie@w3.org> +337 810 795 22 https://www.w3.org/People/Coralie/ <https://www.w3.org/People/Coralie/>
Received on Thursday, 25 March 2021 17:31:18 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 25 March 2021 17:31:19 UTC