View Single Post
Old 10-21-2026, 10:00 AM   #4
Lukusaukko
Connoisseur
Lukusaukko ought to be getting tired of karma fortunes by now.Lukusaukko ought to be getting tired of karma fortunes by now.Lukusaukko ought to be getting tired of karma fortunes by now.Lukusaukko ought to be getting tired of karma fortunes by now.Lukusaukko ought to be getting tired of karma fortunes by now.Lukusaukko ought to be getting tired of karma fortunes by now.Lukusaukko ought to be getting tired of karma fortunes by now.Lukusaukko ought to be getting tired of karma fortunes by now.Lukusaukko ought to be getting tired of karma fortunes by now.Lukusaukko ought to be getting tired of karma fortunes by now.Lukusaukko ought to be getting tired of karma fortunes by now.
 
Posts: 98
Karma: 392326
Join Date: Feb 2023
Device: Kobo Libra 2
Quote:
Originally Posted by DNSB View Post
How does the ouput from your proposed plugin for the calibre ebook-editor compare to the output from the Access-Aide plugin for Sigil?
Are we talking about the semantic code itself? In that case, it shouldn't be all that different - accessible semantics are pretty much set. Otherwise, in it's current proof-of-concept form, it produces a list of accessibility issues it discovers (a subset of ACE checks), and then lets the user click at the issue and jump to the spot; it also has some automatic fixes, such as adding missing language definitions and aria roles corresponding to their epub:types where those are missing. It then lets the user to view the standard Calibre diff to see what has changed.

One of the concepts in CAT is its semantic map editor, which allows the user to define parts of the document in terms of frontmatter, bodymatter, backmatter, and their roles (chapter, preface, etc.) - it can then use that information to create the semantic structure. It's still very basic, but the idea is that ultimately the user creates a semantic map of the document based on its contents, and CAT does the actual semantic tagging where it can automatically do so, and provides an interface to manually edit those parts that need human review (like image alt text or landmarks).

An example of the checker output:
Code:
Warning LANG-DOC-001 chapter01.html:2 The html element declares no language.
Pass HEAD-001 : No problems found by this check.
Pass ID-001 : No problems found by this check.
Pass IMG-001 : No problems found by this check.
Pass LINK-001 : No problems found by this check.
Pass PUB-LANG-001 : No problems found by this check.
Pass PUB-PARSE-001 : No problems found by this check.
Pass PUB-TITLE-001 : No problems found by this check.
Pass SEM-ARIA-001 : No problems found by this check.
Not applicable CONF-001 : No dcterms:conformsTo claim.
Not applicable PAGE-001 : No page-list or page-break markers.
Warning DISC-001-ACCESSIBILITYFEATURE content.opf: schema:accessibilityFeature is not declared.
Warning DISC-001-ACCESSIBILITYHAZARD content.opf: schema:accessibilityHazard is not declared.
Warning DISC-001-ACCESSMODE content.opf: schema:accessMode is not declared.
Warning DISC-001-ACCESSMODESUFFICIENT content.opf: schema:accessModeSufficient is not declared.
Warning NAV-LANDMARKS-001 nav.xhtml: Navigation document has no landmarks nav.
Info DISC-001-ACCESSIBILITYSUMMARY content.opf: schema:accessibilitySummary is not declared.
Pass NAV-002 : No problems found by this check.
Pass NAV-003 : No problems found by this check.
Not applicable DISC-002 : No accessibility metadata declared.
Not applicable DISC-003 : No accessibilityHazard declared.
Not applicable DISC-004 : No accessibility metadata to compare.
Lukusaukko is offline   Reply With Quote