Report if required a11y metadata 'conformsTo' is absent.

[marisademeglio]

See http://www.idpf.org/epub/a11y/accessibility.html#sec-conf-reporting

We don't process <link> elements (as far as I know) so maybe that's why this isn't already included. The other a11y properties are <meta>s.

[laudrain]

We had discussions about that in France in "Normes&Standards" working group.
We are thoughtful about self-certification by the publisher, and considering a 2 steps process:

• publishers (and epub producers) setup a conformance level
• independant organisations can verify the conformance and declare certification
  Then the certifiedBy property would not be setup at production level.
  Are we diverging from this specification?

[rdeltour]

Are we diverging from this specification?

No, the 2-step approach you’re describing sounds OK!

For clarification: the absence of conformsTo would not be reported as a violation, but the (its value or its absence) property should be reported along with other properties in the "Accessibility metadata" section.

[laudrain]

@rdeltour: thanks for the clarification.

[mattgarrish]

should be reported along with other properties in the "Accessibility metadata" section

It's currently only reported in the links section when present.

[marisademeglio]

@rdeltour Is there any other property that would be in links that we want in the metadata table? I'm just running into an issue where this link property gets special treatment, separate from the others. It's fine but ugly.

Also, if we do want to include other link properties, should they just have their own table? Or should we rename our current one "metadata and links" ?

[rdeltour]

@rdeltour Is there any other property that would be in links that we want in the metadata table?

Looking at the link vocabulary, I don’t think so.

Well, we could of course try to fetch and parse external metadata records, but I don’t think we want to go there just yet 🙂

Also, if we do want to include other link properties, should they just have their own table? Or should we rename our current one "metadata and links" ?

The conformsTo info should really be at the same place as the other a11y metadata info, so I wouldn’t put it in its own table. Renaming the table is fine, but then it’s a long name, does it integrate well in the UI?

[marisademeglio]

The conformsTo info should really be at the same place as the other a11y metadata info, so I wouldn’t put it in its own table. Renaming the table is fine, but then it’s a long name, does it integrate well in the UI?

It's not as nice. We will just lump this one link property in with the metadata and call it all "metadata".

[jenstroeger]

Helpful discussion, thank you!

Is it possible to derive the value of conformsTo from the results of an Ace run? Or need I provide that conformance level value myself? And if so, will that value be validated against the state of the document?