Open mkraetke opened 2 months ago
If you put the page number inside the heading tag, then it is part of the heading and is computed in the accessible name (e.g., it would be read out in the landmarks). That's not what end users are going to want to hear.
This should really be raised as a violation of SC 1.3.1 since the page number is not heading text.
The fact is that there should not be pagebreaks within a heading, but should be before or after. It violates WCAG Success Criterion Info and Relationships.
Thank you very much for the quick reply! Then we'll change this on our side. An additional check in ACE would be appreciated as well.
ACE shows the page numbers in the "Headings Outline" and the "HTML Outline" section. This is confusing for users especially if you have numbered headlines. For example, we have tagged the page number but it rather looks like a heading number in the "Headings Outline".
I would like to suggest omitting the page numbers in these views as they do not provide important information. Furthermore, they can be easily identified by their
role
orepub:type
attribute.