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

I think this is the correct way to go, because the language will probably change with WPG specs, but the concepts do not change.
 
Best
George
 
 
From: Avneesh Singh [mailto:avneesh.sg@gmail.com] 
Sent: Monday, September 4, 2017 8:58 AM
To: Matt Garrish <matt.garrish@gmail.com>; 'Romain' <rdeltour@gmail.com>
Cc: public-publ-wg@w3.org
Subject: Re: [a11y] Minutes for Accessibility TF call, held on Aug 23, 2017
 
I do not think that terminology of primary VS secondary is yet resolved on Github issues, and terms perfection can take even months.
 
The objective of the navigation wiki page is to clarify the concepts. So, for this wiki, should we just use “content resource” for the resources in publication that readers will read.
 
With regards
Avneesh
From: Matt Garrish 
Sent: Thursday, August 31, 2017 22:56
To: 'Romain' ; 'Avneesh Singh' 
Cc: public-publ-wg@w3.org <mailto:public-publ-wg@w3.org>  
Subject: RE: [a11y] Minutes for Accessibility TF call, held on Aug 23, 2017
 
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 <mailto:avneesh.sg@gmail.com> >
Cc: public-publ-wg@w3.org <mailto: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-Requirements-for-WP
 
3.
https://github.com/w3c/publ-wg/wiki/Requirements-and-design-options-for-synchronized-multimedia
 
With regards
Avneesh Singh
COO, DAISY Consortium