You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@mattgarrish, it seems doc-pagefooter and doc-pageheader never made their way to ARIA in HTML, and consequently to v.Nu. What's that status of these two role?
Shouldn't they be submitted to ARIA in HTML before being added to EPUBCheck?
DPUB-ARIA 1.1 was finally made a REC back in May so they are official roles now.
But, yes, we shouldn't move ahead of ARIA in HTML on where they're allowed. They weren't added by us but for applications like google docs that want to suppress the running headers and footers they put in. I'd likely wait on them to submit as I don't know their intended use cases for the roles.
But if you feel pressed to do something, you could always allow them on elements that accept any role. That would never be an invalid use.
Stumbling upon this, this does not seem to be an ARIA-in-HTML problem as such. Elements that allow all roles also allow the new DPUB-ARIA 1.1 roles (e.g. div). If other elements should support them, then I'd file an issue on the html-aria tracker.
Similarly, there was no nu validator issue filed to add support for these new DPUB 1.1 roles (so even the currently specified usage won't validate). Also, nu validator saw a lot of improvements recently; it'd be nice if epubcheck would update.
Activity
rdeltour commentedon Sep 9, 2025
@mattgarrish, it seems
doc-pagefooteranddoc-pageheadernever made their way to ARIA in HTML, and consequently to v.Nu. What's that status of these two role?Shouldn't they be submitted to ARIA in HTML before being added to EPUBCheck?
mattgarrish commentedon Sep 9, 2025
DPUB-ARIA 1.1 was finally made a REC back in May so they are official roles now.
But, yes, we shouldn't move ahead of ARIA in HTML on where they're allowed. They weren't added by us but for applications like google docs that want to suppress the running headers and footers they put in. I'd likely wait on them to submit as I don't know their intended use cases for the roles.
But if you feel pressed to do something, you could always allow them on elements that accept any role. That would never be an invalid use.
pkra commentedon Jan 13, 2026
Stumbling upon this, this does not seem to be an ARIA-in-HTML problem as such. Elements that allow all roles also allow the new DPUB-ARIA 1.1 roles (e.g.
div). If other elements should support them, then I'd file an issue on the html-aria tracker.Similarly, there was no nu validator issue filed to add support for these new DPUB 1.1 roles (so even the currently specified usage won't validate). Also, nu validator saw a lot of improvements recently; it'd be nice if epubcheck would update.
feat: support 'doc-pageheader' and 'doc-pagefooter' DPUB ARIA roles