Fix SharePoint Accessibility Assistant Missing Incorrect Heading Levels
Question details
The user needs to know how to resolve an issue where the SharePoint Accessibility Assistant does not flag skipped heading levels as an error.

- Product
- SharePoint
- Device & OS
- not provided
- Scenario
- Checking a SharePoint page for accessibility compliance using the built-in Accessibility Assistant.
- Observed behavior
- The Accessibility Assistant incorrectly reports valid headings even when the page structure skips a level, such as using an H1 directly followed by an H3.
Verify that your page actually contains the skipped heading levels and identify your organization's Microsoft 365 administrator, as resolving this bug requires administrative support access.
Submit a Service Request via Microsoft 365 Admin Center
Since the Accessibility Assistant lacks user settings to modify its checks, this bug must be reported directly to the Microsoft development team for investigation.
The reported behavior is not expected, as skipping from H1 to H3 creates an inaccessible heading hierarchy. Because the Accessibility Assistant is an independent feature with no customizable user controls, it requires a developer-side fix.
If you are not an administrator, contact your organization's IT department or Microsoft 365 administrator to report the issue to them.
Have the administrator navigate to the Microsoft 365 admin center and log in with their admin credentials.
Open a new support ticket detailing that the SharePoint Accessibility Assistant fails to flag H1 to H3 heading skips. Be sure to attach any relevant diagnostic logs or page screenshots to help the development team investigate.
Create Perfectly Structured Documents with WPS Office
While managing web accessibility in SharePoint might require Microsoft support, creating well-structured, highly accessible documents is seamless in WPS Office. Switch to a lightweight, free alternative that makes managing heading hierarchies effortless.

Frequently Asked Questions
Why is an H1 followed by an H3 considered an accessibility error?
Assistive technologies, such as screen readers, rely on a logical, sequential heading structure (H1, H2, H3) to help users navigate content. Skipping a heading level confuses these tools and makes it difficult for visually impaired users to understand the page hierarchy.
Can I manually adjust the checking rules in the SharePoint Accessibility Assistant?
No, the SharePoint Accessibility Assistant is currently a standalone feature that does not provide user-facing settings or controls to adjust, add, or bypass specific accessibility checks.
How do I collect diagnostic logs for a SharePoint issue?
Diagnostic logs are typically gathered by your Microsoft 365 administrator using network tracing tools or the Microsoft Support and Recovery Assistant (SaRA). Your admin will handle attaching these logs when they submit the service request.




