Re: Accessibility updates

I do not think I agree with the argument.

The EPUB spec says: 

> A default vocabulary is one that EPUB creators do not have to declare a prefix for in order to use its terms and properties where a property value is expected. 

The elements of the default vocabulary are defined in the appendix D of the spec[1].

Following up the references for pageBreakSource, we arrive to [2] (a CG Report) which describes the origin of this property and defines it.  But it does not even refer to the EPUB 3.3 Default Vocabulary, ie, it does not say that this property should be considered as part of the EPUB default vocabulary. Nor should it: as a CG note it cannot normatively "change" the Recommendation. Ie, the "a11y" prefix should be used to refer to it.

I am (of course) not against adding this term to the default vocabulary of the spec under the new charter, thereby indeed making the "a11y" prefix obsolete. (We can do that, under the charter's item referring to the Publishing CG's A11y task force.)

[1] https://www.w3.org/TR/epub/#sec-default-vocab
[2] https://www.w3.org/publishing/a11y/page-source-id/

P.S. I am not sure I understand the "and properties where a property value is expected" remark in the aforementioned definition. Is this the source of our misunderstanding?


> On 2 Dec 2024, at 14:55, matt.garrish@gmail.com wrote:
> 
> No, not in this case. It’s replacing the source-of property in the meta properties vocabulary, so it shouldn’t have a prefix. The references in the techniques document need updating. I’ve filed an issue here: https://github.com/w3c/epub-specs/issues/2667
>  
> Matt
>  
> From: Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>> 
> Sent: December 2, 2024 8:45 AM
> To: Daniel Weck <daniel.weck@gmail.com <mailto:daniel.weck@gmail.com>>
> Cc: Matt Garrish <matt.garrish@gmail.com <mailto:matt.garrish@gmail.com>>; W3C PM Working Group <public-pm-wg@w3.org <mailto:public-pm-wg@w3.org>>; W3C Publishing Community Group <public-publishingcg@w3.org <mailto:public-publishingcg@w3.org>>
> Subject: Re: Accessibility updates
>  
> I would also rely on Matt for an authoritative answer, but I believe that the "a11y:pageBreakSource" is the right one. "a11y" is, by the way, one of the predefined prefixes for the package document, see:
>  
>  https://www.w3.org/TR/epub/#sec-reserved-prefixes
>  
> Cheers
>  
> Ivan
>  
> 
> 
>> On 2 Dec 2024, at 13:40, Daniel Weck <daniel.weck@gmail.com <mailto:daniel.weck@gmail.com>> wrote:
>>  
>> Hello all (especially Matt),
>>  
>> Could you please clarify which syntax is correct?
>> property="pageBreakSource" or property="a11y:pageBreakSource"
>>  
>> See contradicting examples:
>> https://www.w3.org/publishing/a11y/page-source-id/#examples
>> https://www.w3.org/TR/epub-a11y-tech-11/#pageSource
>>  
>> Thank you!
>> Kind regards, Daniel
>>  
>>  
>>  
>> On Fri, 5 Jul 2024 at 14:32, <matt.garrish@gmail.com <mailto:matt.garrish@gmail.com>> wrote:
>>> Hi folks,
>>>  
>>> I just wanted to bring to your attention to some recent updates to the accessibility documents and practices:
>>>  
>>> Now that WCAG 2.2 is the current recommendation, we’ve added the corresponding conformance strings[1] to the list in the accessibility specification. The update is only in the editor’s draft right now, but if you’re producing content that conforms to WCAG 2.2, you don’t need to wait for it to be published.
>>> If you have page breaks or a page list in your publication, the pagination source should now be identified using the a11y:pageBreakSource property.[2] The old method of using dc:source with a source-of property remains valid for backwards compatibility but is no longer recommended.
>>> We also want to make sure that producers are adding the pageNavigation accessibilityFeature value when a page list is included, and that the pageBreakMarkers feature is specified when page breaks are present (do not use printPageMarkers anymore).
>>> It’s also possible to add individual unknown accessibility hazards. As audio hazards still need a clearer definition, the unknownAudioHazard value is the most likely to be used.
>>>  
>>> For a complete list of recent changes to the techniques document, please refer to the change log.[3]
>>>  
>>> On a related note, the accessibility vocabulary will soon be updated to add a new “MathML-chemistry” value for the accessibilityFeature property. This value is to capture chemical equations that are marked up using MathML, a distinction that wasn’t previously possible to make. The change is part of adding a process for defining additional descriptors for values. If you would like more information, or to provide feedback, please refer to the pull request for this change.[4]
>>>  
>>> [1] https://w3c.github.io/epub-specs/epub33/a11y/#sec-conf-reporting-pub
>>> [2] https://www.w3.org/TR/epub-a11y-tech-11/#pageSource
>>> [3] https://www.w3.org/TR/epub-a11y-tech-11/#change-log
>>> [4] https://github.com/w3c/a11y-discov-vocab/pull/107
>>>  
>>> Matt
> 
>  
> 
> ----
> Ivan Herman, W3C 
> Home: http://www.w3.org/People/Ivan/
> mobile: +33 6 52 46 00 43


----
Ivan Herman, W3C 
Home: http://www.w3.org/People/Ivan/
mobile: +33 6 52 46 00 43