Umbrella Issue to note potential accessibility improvements

[windymilla]

1. "Decorative" <hr> elements, e.g. for chapter break, or surrounding an illo, rather than a true thought break that was probably part of the original text: add aria-hidden="true" to the <hr> element. See Winnie-the-Pooh for example. Addressed by Flag added hr elements as decorative #1844
2. Possibly put <main> (or <main role="main">) at start & </main> at end of book during HTML autogeneration. PG header footer will end up outside that when WWed. PPer can adjust position, e.g. to exclude adverts, for some books. Don't do this one - it's better for ebookmaker to handle it. Addressed by Add <main> tags around whole book #1859
3. Consider putting <nav> tags around autogenerated ToC. Addressed by Add <nav> around HTML autogen-ed ToC #1846
4. Possible report on use of plain <i> or <b>: "Fix" button could convert to <em> or <strong> - would need to also convert next matching closing tag. Question: does it need to consider nesting, e.g. <i><i>double</i> italics</i>? I think not. [**ETA - after further consideration, I think the Regex Library file italic_semantic.json is OK for this, rather than a new tool. Would need to add a <b>--><strong> entry to it. Addressed by Add <b> semantic markup fix to regex library #1850

[windymilla]

Notes for documentation:

1. section elements should be used for front matter, end/back matter - to be manually added by PPer
2. GG adds nav tags round auto-ToC. If PPer isn't using it, they should add them round their ToC
3. GG adds aria-hidden="true" to hr elements it adds between chapters. If user inserts additional decorative hr elements, they should include the same element. This is not needed for hr which represent a true thought break, e.g. * * * in text to indicate a thought break, that gets converted to hr
4. Accessibility stuff should be consolidated ( HTML Best Practices Document, https://www.pgdp.net/wiki/Accessibility_Recipes/Emphasis, https://www.pgdp.net/wiki/Accessible_HTML_eBooks, etc). Then the PP FAQ should have a link (or links) to it.
5. WAVE report button (or instructions for doing it manually) should be documented.

[windymilla]

Tasks all complete. Documentation added to https://www.pgdp.net/wiki/Accessible_HTML_eBooks