[KevinH]

Originally Posted by Doitsu

It doesn't violate any rules, but if I understand the specs correctly, they prefer <aside> tags, wrapped in <section> tags.
(The <aside> tags may contain other block level tags such as <p>.

E.g. something like this:

  <section aria-label="Footnotes">
    <aside id="note1" epub:type="footnote" role="doc-footnote">
      First footnote. <a epub:type="backlink" href="#ref1">↩</a>
    </aside>

    <aside id="note2" epub:type="footnote" role="doc-footnote">
      Second footnote. <a epub:type="backlink" href="#ref2">↩</a>
    </aside>
  </section>

or

  <section aria-labelledby="footnotes-heading">
    <h2 id="footnotes-heading">Footnotes</h2>

    <aside id="note1" epub:type="footnote" role="doc-footnote">
      First footnote. <a epub:type="backlink" href="#ref1">↩</a>
    </aside>

    <aside id="note2" epub:type="footnote" role="doc-footnote">
      Second footnote. <a epub:type="backlink" href="#ref2">↩</a>
    </aside>
  </section>

Also see this DAISY page fore more information on aria-label and aria-labelledby.

I am confused. Those already exist. You add a "footnotes section" then fill it with "footnote with aside and backlink".

According to the spec, p is an allowed container for all aria roles, just like div.

So you can technically make a footnote with a p tag.

Also footnotes sections are rarely given a title heading, where as endnotes sections are typically given a title heading.

On Books.app , you would have a title followed by nothing as asides for footnotes are hidden, as you pointed out. That is why a "footnote with div" was added.

I can provide an aria-label though but translating it on the fly not to the ui but to the destination epub language would be a bear.