Meeting minutes
Next steps for Issue #280: Do we want to display Reason why the publication does not claim to meet the standards
<AvneeshSingh> w3c/
Do we want to display Reason why the publication does not claim to meet the standards]
Avneesh: some publishers may not want this type of information displayed.
… Editors call, Gautier suggested separate Conformance Section and Legal Discloser section which could be optional.
… Gregorio suggested FAP which is meeting on July 5 to ask them about this topic.
George: this exemption information is not a conformance claim, we put it there inadvertently. Current draft 3 examples of conformance and removed the example of company claiming a hardship claim.
gpellegrino: I agree, and lets way for legal, and when we get input we can improve it.
… , statement ONIX 09 = inaccessible or known accessibility issues.
… , where do we place this information?
George: if 09 is present is there the possibility the publisher could have put in other a11y features?
… or a valid onix means those other features would not be present.
Hadrien: exemptions - I should have access to this information. if a publication is not accessible I may want to file a report to the regulator. having this information could influence my decision. I agree it doesn't need to be next to other metadata
George, is 09 same as accessibilityFeatures = none.
… , is accessmodesufficient textual is a property not a feature.
<Zakim> Hadrien, you wanted to discuss code 09 and none in schema.org
Hadrien: I haven't see that type of information. Publisher felt confident enough to add to summary but not in conformance or not accessible. Could change, and this was a large set of data I reviewed.
… distributors / aggregators for small publishers.
rickj: I agree we don't see any publishers not saying they are inaccessible. but do see some information in the Summary.
gpellegrino: digital comic books of images, accessibility is challenging, Have seem some PDFs with that code for inaccessible.
AvneeshSingh: do we need to worry about it? not interpret 09 at this time for the first draft. if publishers want it we could include it.
gpellegrino: we can skip code 09 comic book for example 09 with our guidelines we will end up with "Unknown" for all required fields. since 09 can add free text can include in the accessiblitySummary section. from the free text in 09 as well as the accessibilitySummary.
Charles: works for me.
AvneeshSingh: so this is the ONIX techniques : AccessibilitySummary (addendup, summary and free text from 09)
Hadrien: I have never seen anything useful in those text fields.
AvneeshSingh: lets include it in first draft. this is a compromised instead of leaving it out 09 completely. if they start using it a lot we can revise this.
<rickj> +1
All the accessibility metadata displayed are the claims made by the publisher. How should we convey this fact in our guide.
gpellegrino: should we add "claim" to each item, but everything in metadata is a claim, even the title, subtitle and all a11y metadata, they could claim mathML but there is none in the file itself (copy/paste)
… maybe we can add a note that this metadata is from the publisher and in all claims made by them.
gautierchomel: difference with conformance, claiming could be from a 3rd party certifier.
… or from a service provider / aggregator etc.
… we don't need to specify claim.
rickj
rickj: we add a badge "Accessibility claims" for each title with a11y metadata.
gpellegrino: I like Rick's approach that they whole section is claims made by the publisher. this book claims to be accepted conformance etc.
rickj: we like the short wording is made localization much easier in 37 languages they support. we are using compact statement but if you hover over it shows the full statement.
AvneeshSingh: what about screen readers?
rickj: this is just internal currently but yet we will do that testing.
AvneeshSingh: Accessibility Claims then simplify.
gautierchomel: Claim translated in french doesn't work but "statement" does work well. "Accessibility Decoration" good for French / Italy
Review of further progress in techniques documents.
AvneeshSingh: Onix / EPUB
<AvneeshSingh> https://
gpellegrino: nothing to update we have a PR on conformance but we wanted to wait for the decision about conformance / legal.
… Waiting for Chris to finalize the draft and then we can finalize the PR for ONIX. most of the work has been done.
<AvneeshSingh> https://
Charles: holding pattern waiting for ONIX to finalize Conformance / Legal sections.
Any other business.
George: guidance from editors for Principals doc.