E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 3 (In chronological order)

From: Mark Magennis
Date: Fri, Jan 19 2018 3:42AM
Subject: Is same table row sufficient context for a link to meet SC 2.4.4?
No previous message | Next message →

Dear all,

This is probably a very common situation. We have pages containing lists of multimedia assets - videos, audiobooks, e-books and online courses. Each asset has a title, type, and status (started, finished, etc.), followed by a link which is either Watch, Read, Listen, or Explore, depending on the asset type.

The lists are presented in tables with a row for each asset and columns for the title, type, and status and link.

The question is, must the link text include the asset type and title, for example "Watch video Oracle Certified Associate, Java SE8 Programmer"? Or is it okay to just leave the link as "Watch", given that the type and title are in the same row and are very likely to be read just before the link (the title is itself a link)? Is this sufficient context?

WCAG 2.4.4 lists some examples of sufficient context:
same paragraph
same list item
same table cell
table cell header
This doesn't include same table row, however. Failure F63 includes Example 2: A Link in an Adjacent Cell Within a Layout Table. But this example has the link in a different row from the contextual information, so it doesn't definitively answer the question. I note that JAWS has a keyboard shortcut to read the current table row (so the context is not only programmatically available, but also practically available to JAWS users). This may not be true of other ATs though. For example, I can't see a similar command in NVDA.

I feel this is nitpicking to some extent, but WCAG conformance is important in this case and I want to be true to both the spirit and the letter of SC 2.4.4.

Thanks,
Mark

Mark Magennis | Accessibility Support Manager
InterAccess.ie - Accessible UX

From: Birkir R. Gunnarsson
Date: Fri, Jan 19 2018 5:02AM
Subject: Re: Is same table row sufficient context for a link to meet SC 2.4.4?
← Previous message | Next message →

Mark
If you make the title a header cell, you satisfy WCAG 2.4.4
<tr>
<tr>
<td>Adventures of a Frat boy</td>
<td>video</td>
<td><a href="#">Watch</a></td>
</tr>
does not pass, but
<hd>Adventures of a Frat boy</th>
<td>video</td>
<td><a href="#">Watch</a></td>

or

<td role="rowheader">Adventures of a Frat boy</td>
<td>video</td>
<td><a href="#">Watch</a></td>

do.

If we are getting nitpickty, if clicking "Wwatch" loads the video
player it should be a button, not a link (if it navigates to the video
page it should be a link). ;)




On 1/19/18, Mark Magennis < = EMAIL ADDRESS REMOVED = > wrote:
> Dear all,
>
> This is probably a very common situation. We have pages containing lists of
> multimedia assets - videos, audiobooks, e-books and online courses. Each
> asset has a title, type, and status (started, finished, etc.), followed by a
> link which is either Watch, Read, Listen, or Explore, depending on the asset
> type.
>
> The lists are presented in tables with a row for each asset and columns for
> the title, type, and status and link.
>
> The question is, must the link text include the asset type and title, for
> example "Watch video Oracle Certified Associate, Java SE8 Programmer"? Or is
> it okay to just leave the link as "Watch", given that the type and title are
> in the same row and are very likely to be read just before the link (the
> title is itself a link)? Is this sufficient context?
>
> WCAG 2.4.4 lists some examples of sufficient context:
> same paragraph
> same list item
> same table cell
> table cell header
> This doesn't include same table row, however. Failure F63 includes Example
> 2: A Link in an Adjacent Cell Within a Layout Table. But this example has
> the link in a different row from the contextual information, so it doesn't
> definitively answer the question. I note that JAWS has a keyboard shortcut
> to read the current table row (so the context is not only programmatically
> available, but also practically available to JAWS users). This may not be
> true of other ATs though. For example, I can't see a similar command in
> NVDA.
>
> I feel this is nitpicking to some extent, but WCAG conformance is important
> in this case and I want to be true to both the spirit and the letter of SC
> 2.4.4.
>
> Thanks,
> Mark
>
> Mark Magennis | Accessibility Support Manager
> InterAccess.ie - Accessible UX
>
>
>
>
> > > > >


--
Work hard. Have fun. Make history.

From: Bim Egan
Date: Fri, Jan 19 2018 6:56AM
Subject: Re: Is same table row sufficient context for a link to meet SC 2.4.4?
← Previous message | No next message

Hi Mark,

Just to add to Birkir's solid advice: You already use a different text
value for each type of media link, which is great, so if there's been a
previous explanation of what media types are available, the relationship
will be obvious to a great many users. To help anyone who may not
understand, a key to the relationships could appear in text above the table,
or be visually-hidden .

<div id="key" class="visually-hidden">
<H2>Key to link types: </h2>
<ul>
<li>Watch = video; </li>
<li>Read = eBook; </li>
<li>Listen = AudioBook; </li>
<li>Explore = online-learning. </li>
</ul>
</div>

Followed by the table, where the first row and first column cells are all
<th>. In both NVDA and JAWS, if the user tabs into the first interaction
type link, the screenreader announces the media title and whatever you've
used as the <th> cell content above the links.

Note: I've given the <div> an id of "key" because something else you might
consider is using it to associate the contents of the div with the first
cell in the table.
<th aria-describedby="key" scope="col">Title </th>

When a screenreader reaches the first cell, JAWS (but not NVDA) will let the
user know that there's associated text and announce the shortcut to access
the information in the div.

HTH,

Bim