Meeting minutes
Issue #280: Do we want to display Reason why the publication does not claim to meet the standards
<Simon_Mellins> Testing
test
test
<Simon_Mellins> Should it be showing 'chan-2' in the URL string like this?
(gautier resumed the issue https://
CharlesL: I understand the point of not exposing exemptions. I agree to keep things straight forward with conformity yes or no.
gpellegrino: The EAA aims to inform the end user of the accessibility of the product / service. Transparency is important to be sure we are informing the user.
gpellegrino: I agree to not say why it is not accessible but I see a use case related to the end user raising requests to the authority in charge of survey. So may be we can find a friendly way to inform.
gpellegrino: there is a difference between a book checked and one not checked.
MiiaK: discussing with finnish publishers, they seem to expect this exemption to be displayed to avoid complains or unncessary complains. Especially disproportionate burden.
<rickj> apologies for the late join
gpellegrino: this are guidelines, implementers can decide to twist around our recomandations. Also publishers have hands on theyre metadata.
gautierchomel: 2 use cases. country says no I don't have means to control your metadata I don't want people reaching out, want it to be preinformed. so they can make legislation regarding that.
… the a11y addendum what they want to tell the end users.
… recommending to display these will affect what the publishers put into their books/feeds.
Simon_Mellins: I don't see a reason to not display it, I think it's usefull for the user and the publisher.
AvneeshSingh: we could find a middle part, soften the recomandation and provide a note that the decision may depend on the market you are serving.
GeorgeK: is there a way to diferenciate conformance of thise particular items? Can we determine a publisher choice?
gpellegrino: on ONIX, there is no way to saying if the metadata is for BtoB or to be displayed.
<rickj> we have 32,190 titles that make a WCAG conformance claim
gautierchomel:
… there is a confusion between conformity and accessibility.
… wcag-aa compliant but does not have DisplayTransformability. even if it is AA compliant it doesn't work for me.
… EPUB made of text except for a cover / logo. but I am a micro enterprise I don't want to check things because I have 1000 books, I want to say I don't know i haven't checked
… but it doesn't mean its not accessible just that I haven't made the accessibility conformance testing needed.
… you may have a file that may not conform to the a11y standard but include a11y features.
AvneeshSingh: YOu may not put in the conformance statement but do put in other a11y features.
gpellegrino: in schema unknown a11y features you don't know what features are present in the book. you don't know it is conforms or not.
wendyreid: is this information useful is what it comes down to. Retailers need to know this information but maybe not for the user will find useful or valuable.
wendyreid: there is a way in schema and ONIX to inform about the exemption. As a retailer I can see it and i'll trust it. For the user, is it of use? Few users understand conformity. As a reader, do I really care that the publisher is a micro enterprise? D I even understand what this means? I don't think it is of interest for the end user.
GeorgeK: in the principles, we can put a note in the details area that says when the publisher claims exemption, you may choose to display it or not. And we should change the wording unknown accessibility into unknown conformance.
rickj: I get unconfortable to saying something is or is not accessible. I don't want to make a judgement, I prefer to stick with what the publishers claims or not.
gautierchomel: is it the publisher is claiming is not meeting conformance, but still have some accessibility. There might be chances to be accessible.
… 09 code is not about conformity but is more about that the book may have some a11y issues.
Review of further progress in techniques documents.
AvneeshSingh: we'll make a proposal for the next editor call.
https://
gpellegrino: we are working on conformance, in a wait state since we have to fix the principles (see previous discussion)
gpellegrino: one other point is additional accessibility information. Chris opened numerous github issues to check which are already uqed, and for each not used, he created an issue with proposal to ignore it or to add it to one or another technic or to put it in the Additioonal accessibility information section.
https://
CharlesL: we are ready to merge EPUB techniques related to accessibility summary. Like for ONIX, we are waiting this discussion about conformity to be fixed so we can follow up.
Further updates to the principles document.
https://
GeorgeK: I created an intriduction and made the abstarct more aligned with the specifications. Abstract is smaller now, like an abstract has to be.