View Single Post
Old 01-21-2025, 09:58 AM   #2
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,870
Karma: 6120478
Join Date: Nov 2009
Device: many
No idea but most of these acts, just rely on native html and website accessibility markup using Aria roles. So as long as you add the proper Aria markup, and semantic markup, and manually follow whatever else is in their guidelines you should be okay.

So this is an epub developer to-do thing and not a Sigil issues as Sigil gives you full access to the markup so you can add what is needed.

That said, if the EAA has a validator app, someone could try to package it up as a plugin much like epubcheck and AccessAide.

Last edited by KevinH; 01-21-2025 at 10:02 AM.
KevinH is offline   Reply With Quote