W3C home > Mailing lists > Public > public-publ-wg@w3.org > August 2017

RE: [a11y] Minutes for Accessibility TF call, held on Aug 23, 2017

From: Matt Garrish <matt.garrish@gmail.com>
Date: Thu, 31 Aug 2017 13:26:48 -0400
To: "'Romain'" <rdeltour@gmail.com>, "'Avneesh Singh'" <avneesh.sg@gmail.com>
Cc: <public-publ-wg@w3.org>
Message-ID: <014801d3227e$543a7fe0$fcaf7fa0$@gmail.com>
The issue deals with this already, but for anyone who doesn't want to read
it through: primary and secondary made sense when we defined them - with
secondary being supporting resources for primary.

 

Now that that is not true, primary resources are also, by definition,
secondary resources, since they are essential to the publication. Secondary
don't carry any supplementary distinction, either, since secondary resources
may contain the primary narrative (e.g., any publication with only the
starting point listed in the default reading order).

 

I think we're leading to a situation where "primary resource" might begin to
overlap in people's minds with "primary narrative".

 

If it's too early to name the structure that defines the reading order, or
if we don't intend to give it a unique name, can we revert to "resources"
and "resources in the default reading order" for now? We don't have that
many instances of primary/secondary as it is.

 

Matt

 

From: Romain [mailto:rdeltour@gmail.com] 
Sent: August 31, 2017 11:51 AM
To: Avneesh Singh <avneesh.sg@gmail.com>
Cc: public-publ-wg@w3.org
Subject: Re: [a11y] Minutes for Accessibility TF call, held on Aug 23, 2017

 

Hi Avneesh and all,

 

I just read the "accessibility requirements for navigation" [2]  on the
wiki, and these are a bit ambiguous in the use of "primary resource",
"secondary resource". The meaning of these terms are still debated in issue
#55, and the current thinking is that (copying Hadrien's comment):

 

- primary = default reading order

- secondary = part of the publication, not in the default reading order, may
be packaged or cached for offline viewing (can be anything: HTML, CSS,
images, etc).

- external = anything else referenced in the publication, not in any list in
the manifest, won't be packaged or cached for offline viewing

 

I believe the accessibility wiki should be clarified before being share to
the larger group.

 

Best,

Romain.

 

#55: https://github.com/w3c/wpub/issues/55

 

 

On 24 Aug 2017, at 07:07, Avneesh Singh <avneesh.sg@gmail.com
<mailto:avneesh.sg@gmail.com> > wrote:

 

Dear Accessibility Task Force.

 

The cleaned minutes of the conference call held on August 23, 2017, at 14
UTC are available at 1.

The next conference call is scheduled on September 6, at 14:00 UTC (4 PM
Paris / 10 AM Boston).

 

We discussed the following documents in the con call, and further feedback
from the task force is welcome.

Accessibility requirements for navigation in WP. (link 2.)

Accessibility requirements for synchronized multimedia (link 3.)

1.

https://github.com/w3c/publ-wg/wiki/Accessibility-Task-Force

 

2.

https://github.com/w3c/publ-a11y/wiki/Description-of-Accessibility-Requireme
nts-for-WP

 

3.

https://github.com/w3c/publ-wg/wiki/Requirements-and-design-options-for-sync
hronized-multimedia

 

With regards

Avneesh Singh

COO, DAISY Consortium

 
Received on Thursday, 31 August 2017 17:27:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:49:06 UTC