Word styles + semantics for accessibility

Word is the most widely used authoring tool, which makes it the best place to build accessibility in from the start. Three requests, in priority order:

1. Show the Navigation Pane (Headings view) by default.
   Displaying the document's heading structure while users write makes hierarchy visible and errors easy to spot. At minimum, show Headings.
2. Match default visual styles to semantic hierarchy.
   Make H1 the most prominent style, with H2, H3, and H4 each visibly a step lower. Today, Styles read as purely visual choices, so users often skip levels or fake headings for looks, producing inaccessible documents. Aligning appearance with structure would make accessible output the default.
3. Add heading-hierarchy checks to Check Accessibility (or as a proofing-style alert).
   Flag more than one H1 or skipped levels (e.g., H3 not under H2), and let users fix them in one step using the styles in request #2. Also flag any fonts less than 12 points for possibly being inaccessible. Make this optional, with an IT policy toggle for organizations.

Why it matters: Our organization must meet U.S. Federal Title II accessibility requirements for all web PDFs by April 26, 2027. Without an easy path, our simplest option is to remove them. If users could create properly structured Word documents and export accessible PDFs, we'd have a practical solution to share with staff and the public we serve.