Accessibility Checker

Karellen · Today, 01:17 AM

Hi @kovidgoyal

Thanks for the latest update.

I noticed the new Accessibility Checker and wanted to give it a try.

The image shows a <h4> heading. This skips a level as there is no <h3> heading above it, only a <h2>.

It shows an epub:type with no matching Aria role.

The checker didn't pick up on either of these. Something I am misunderstanding?

kovidgoyal · Today, 01:53 AM

The heading level checker had a bug, it didnt catch the first heading in a new html file, now fixed.

epub:type without an ARIA role: correct behaviour. epub:type="chapter" matches the role doc-chapter, but ARIA doesn't allow that role on headings, only on things like <section>. Adding it would make the markup invalid, so the checker rightly doesn't suggest it. The real problem is that chapter doesn't belong on an <h4>; it should be on the surrounding <section> or <body>.

Karellen · Today, 02:08 AM

Quote:

Originally Posted by kovidgoyal

The heading level checker had a bug, it didnt catch the first heading in a new html file, now fixed.

Great. Thank you.

Quote:

Originally Posted by kovidgoyal

but ARIA doesn't allow that role on headings, only on things like <section>.

Ok, thanks. I added that epub:type as a test, but also I wasn't aware of that requirement.

I've checked using a <section> tag as suggested, and it captured the missing aria role.

Is it expected that it does not work in reverse - have the aria role, but the epub:type is missing?

kovidgoyal · Today, 02:17 AM

yes, it is, accessibility relies on aria roles not epub:type, so the checker does not care too much about epub:type

Karellen · Today, 03:17 AM

Great. Thanks!!

enuddleyarbl · Today, 07:18 AM

Kovid,

I'd just like to thank you for all the work you're doing. I just looked at the release notes for the latest version and this Accessibility Checker looked really interesting. I'll be testing it out a bit later. Up until now, I've either been ignoring or deleting accessibility stuff in the ebooks I edit because I simply didn't understand how it worked. This will give me an opportunity to figure it out.

Thanks, again.

PS: And, the Content Server updates in this version look really interesting, too. I'm pretty sure I'll be starting to use the Content Server in the next couple of days.

kovidgoyal · Today, 07:49 AM

You're welcome!

Lukusaukko · Today, 10:30 AM

It's a good thing I decided to make the accesibility tool I've been working on into a guided editor rather than just a checker as it was originally - the new functionality would've rendered it obsolete before it was even released

Today, 01:17 AM	#1
Karellen Wizard Posts: 1,921 Karma: 9600930 Join Date: Sep 2021 Location: Australia Device: Kobo Libra 2	Accessibility Checker Hi @kovidgoyal Thanks for the latest update. I noticed the new Accessibility Checker and wanted to give it a try. The image shows a <h4> heading. This skips a level as there is no <h3> heading above it, only a <h2>. It shows an epub:type with no matching Aria role. The checker didn't pick up on either of these. Something I am misunderstanding? Attached Thumbnails

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Plugin] ACE - DAISY EPUB Accessibility Checker wrapper	Doitsu	Plugins	40	12-10-2025 11:53 AM
[Editor Plugin] ACE by Daisy - EPUB Accessibility Checker	thiago.eec	Plugins	26	03-27-2023 09:19 AM
Accessibility	BooksForABuck	News	0	12-30-2004 10:37 PM

Today, 01:53 AM	#2
kovidgoyal creator of calibre Posts: 46,591 Karma: 29634066 Join Date: Oct 2006 Location: Mumbai, India Device: Various	The heading level checker had a bug, it didnt catch the first heading in a new html file, now fixed. epub:type without an ARIA role: correct behaviour. epub:type="chapter" matches the role doc-chapter, but ARIA doesn't allow that role on headings, only on things like <section>. Adding it would make the markup invalid, so the checker rightly doesn't suggest it. The real problem is that chapter doesn't belong on an <h4>; it should be on the surrounding <section> or <body>.

Today, 02:17 AM	#4
kovidgoyal creator of calibre Posts: 46,591 Karma: 29634066 Join Date: Oct 2006 Location: Mumbai, India Device: Various	yes, it is, accessibility relies on aria roles not epub:type, so the checker does not care too much about epub:type

Today, 03:17 AM	#5
Karellen Wizard Posts: 1,921 Karma: 9600930 Join Date: Sep 2021 Location: Australia Device: Kobo Libra 2	Great. Thanks!!

Today, 07:18 AM	#6
enuddleyarbl Guru Posts: 901 Karma: 2111023 Join Date: Sep 2013 Device: Kobo Sage	Kovid, I'd just like to thank you for all the work you're doing. I just looked at the release notes for the latest version and this Accessibility Checker looked really interesting. I'll be testing it out a bit later. Up until now, I've either been ignoring or deleting accessibility stuff in the ebooks I edit because I simply didn't understand how it worked. This will give me an opportunity to figure it out. Thanks, again. PS: And, the Content Server updates in this version look really interesting, too. I'm pretty sure I'll be starting to use the Content Server in the next couple of days.

Today, 07:49 AM	#7
kovidgoyal creator of calibre Posts: 46,591 Karma: 29634066 Join Date: Oct 2006 Location: Mumbai, India Device: Various	You're welcome!

Today, 10:30 AM	#8
Lukusaukko Zealot Posts: 104 Karma: 392326 Join Date: Feb 2023 Device: Kobo Libra 2	It's a good thing I decided to make the accesibility tool I've been working on into a guided editor rather than just a checker as it was originally - the new functionality would've rendered it obsolete before it was even released