RE: Best citation format for accessibility

As you noted, the actual citations are all a matter of programming.

I don't really think AT will pick up on ontologies without a lot of mapping work, but I don't think it's really necessary either.

My WCAG concern is http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140916/G53 Identifying the purpose of the link. If I simply append the Name date citation to the end of sentence or paragraph, is the link actually understandable? Further, if the same Name Date (Smith 2015) is used repeatedly in a publication, does that add a layer of confusion?



Tzviya Siegman
Digital Book Standards & Capabilities Lead
Wiley
201-748-6884
tsiegman@wiley.com 


-----Original Message-----
From: Robin Berjon [mailto:robin@berjon.com] 
Sent: Tuesday, September 22, 2015 4:19 PM
To: Siegman, Tzviya - Hoboken; public-digipub-ig@w3.org
Subject: Re: Best citation format for accessibility

Hi Tzviya,

On 22/09/2015 11:33 , Siegman, Tzviya - Hoboken wrote:
> Great to hear from you.

Likewise :)

> There is a great lack of consensus on best practices for citation in 
> general. Harvard vs AMA vs Vancouver, and that does not include the 
> variety of HTML citations. They all include essentially the same 
> information in a different sequence.

Indeed. Your latter sentence there is what interests me: we can reorder (and punctuate, and apply font styling) at the style level. That becomes a matter of writing sufficiently cunning CSS that can match a given style guide, i.e. it's a SMOP (Simple Matter Of Programming).


> I turn the question around to you. What is missing?

I'm not sure — that's why I'm asking :) I mean, I can easily go with the order that I think would make sense as the semantic order but I want to make sure I'm not 927ing the space.

> Should citations be chunked elements that a user can tab through?

On instinct I wouldn't think so. I think it largely boils down to what order to use, along with some additional notions such as whether multiple initials stuck together might somehow trip a screen reader (e.g. Vancouver style would cite this email as from "Berjon RM" which I reckon might read strangely).

I'd be tempted to go with something like (at 30kft): title, author, source, date. Without the ontological markup (and with space for readability), this would look like:

<li>
  <cite>Moby-Dick</cite>
  <span class='punct'>, by </span>
  <span>Herman Melville</span>
  <span class='punct'>(</span>
  <span>Bentley</span>
  <span class='punct'>, </span>
  <time>1851-10</time>
  <span class='punct'>).</span>
</li>

> If
> AT can pick up on existing ontologies we can do this now using 
> resources like BIBO [1], CITO [2], and others. (This might not be 
> easy, but it's better than <span class="surname">)

At this point my understanding is that AT is still catching up to ARIA, I don't think we should be too reliant on it picking up ontologies.

> 
> One pain point I see is the Name Date method of citation, which refers 
> the reader to the citation by use of the authors surname and year of 
> publication. For example, a reference to Moby Dick would be (Melville, 
> 1851). Multiple references to the same work would use the same 
> reference. When digital, these references are usually links.  I think 
> this method of linking violates WCAG unless one is really careful.

I'm curious which part of WCAG this might violate? Sure enough the content text is not very explicit, but that's not what you have in mind?

We could switch references between various styles using data-* attributes and style like the following; but that requires adding data to the links. I'm not sure it's a good idea — at this point I'm focusing on the actual citations.

      .refs.numeric a, .refs.author-year a {
        font-size: 0;
      }
      .refs.numeric a::after {
        font-size: 16px;
        content: " (" attr(data-num) ")";
      }
      .refs.author-year a::after {
        font-size: 16px;
        content: " [" attr(data-authyear) "]";
      }

> Should we loop in WAI?

Yeah, I'll point some WAI folks at this thread.

--
• Robin Berjon - http://berjon.com/ - @robinberjon • http://science.ai/ — intelligent science publishing •

Received on Thursday, 24 September 2015 12:48:48 UTC