Meeting minutes
Revision of Accessibility summary guide.
<AvneeshSingh> https://
AvneeshSingh: do we need to update this guide?
George: and does it need to exist?
gautierchomel: I would like to rediscuss the sentence related to multiple accessibility summary in different languages. It's a practice we should recognise.
mgarrish: I agree we need to do something, but not sure what.
CharlesL: in GCA we've discussed with publishers and we think it would be great to have examples. Like "pages have been removed from the print original, because blank or legal mentions to print". That could be examples about what not to do.
George: now we have a much better machine readable information and a strong display guide. Maybe we miss a best practices for publishers to write those informations. This guidance could be extended to more topics.
gpellegrino: there are still use cases for using the summary. Today most publisher fill it because it's a reported error by ACE, and zero ACE issues is requested by distributors. ACE should change this. I'll reopen the issue and send an information to the CG.
mgarrish: we have too much information in too many places. too many different documents to map. Maybe that should stand in the techniques.
Madeleine: another place is the vocabulary documents.
CharlesL: most common usecase i see is files missing few things to get wcag aa, they explain that in the summary.
AvneeshSingh: to sumarise, we cannot keept this document as it is. It's a bigger project to move to a new document. For now we can copy what's in the technqiues here and see in the futur how to reorganise.
JonasLillqvist: ACE behavior seems to be based on EPUB accessibility recomandation. It says Should, so as a publisher i interpret is as it is better to include it. We may want to clarify at this level.
JonasLillqvist: Can we change from Should to May?
AvneeshSingh: we can discuss that next week, it will be the Maintenance working group accessibility task force.
George: maybe we can start a CG note knowing it gonna take a long time to complete. This accessibility summary document is linked in many persons bookmarks. It's difficult to make it just disapear.
mgarrish: it will be easier to change ACE behavior than chaging the EPUB Accessibility document.
AvneeshSingh: so we'll add a paragraphe stating that this document is obsolete and start a new one with content copy pasted from the technics and updating it. I wonder if this should not better be in the WG, as rec track document.
AvneeshSingh: advantage of CG is flexibility.
Next steps for localized placeholders.
<AvneeshSingh> w3c/
CharlesL: when putting a date in a sentence, depending on the language you need to move the place of the word.
gpellegrino: instead of concatenating, itr's better to have a placeholder in the string, usually between brackets so it can be freely moved by the person localising.
Hadrien: this came out when implementing in the readium mobile toolkits. It's possible to have more than one variable (day, month, year per exemple). Interpolating strings necesitate to have each piece in brackets.
AvneeshSingh: that mean a change in the json file and a warning for implementers.
Hadrien: we should recomand using interpolated strings and localised dates. As a user I can set up a language and a date format, that's may be different. Implementers should not show raw data for dates, but format them to the user preference.
CharlesL: that also affects WCAG versions and levels.
mgarrish: for WCAG we can rely on official translations as they exist.
AvneeshSingh: editors will figure out how to make that change.
EPUB audio books:
<AvneeshSingh> w3c/
mgarrish: ONIX is more accurate than schema here. We might end up calling an EPUB "audiobook", introducing confusion.
AvneeshSingh: seems for now we can rework the text. For later, see if it can be fixed in schema.
AvneeshSingh: next call may be cancelled as there is a Daisy board meeting.