Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Page numbers are displayed in outlines tab #415

Open
mkraetke opened this issue May 22, 2024 · 3 comments
Open

Page numbers are displayed in outlines tab #415

mkraetke opened this issue May 22, 2024 · 3 comments

Comments

@mkraetke
Copy link

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".

  • [h1] Soziologie der Arbeit
    • [h2] 1. Was ist Arbeit?
    • [h2] 122. Perspektiven der Soziologie auf Arbeit im Kapitalismus
    • [h2] 3. Arbeitsmärkte und ihre Regulierung im Kapitalismus
    • [h2] 4. Geschichte der deutschen Arbeits- und Industriesoziologie
<h2 id="d335992e274" class="_notoc U3 notoc" title="2. Perspektiven der Soziologie auf Arbeit im Kapitalismus">
  <span class="pagenum" title="12" id="page_12" epub:type="pagebreak" role="doc-pagebreak">12</span>
  2. Perspektiven der Soziologie auf Arbeit im Kapitalismus
</h2>

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 or epub:type attribute.

@mattgarrish
Copy link

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.

@gregoriopellegrino
Copy link

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.

@mkraetke
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants