Skip to content

Invalid Heading Orders #473

Open
Open
@bbertucc

Description

@bbertucc

Description:

There is an issue with the heading order on several web pages. Correct heading order is crucial for accessibility as it helps users with screen readers to understand the structure and content hierarchy of the webpage. This issue needs to be resolved to enhance accessibility.

Current Code:

A detailed report of the affected nodes can be found in the CSV file: invalid_heading_orders.csv

Example Fix

One of the nodes with invalid heading order is on https://wordpress.org/about/privacy/data-erasure-request/

<h5>Important!</h5> appears beneath <h1>Data Erasure Request</h1>.

A possible fix would be to change it to: <h2>Important!</h2> or <strong>Important!</strong>.

This fix aligns the heading with the correct hierarchy and improves accessibility.

Steps to Reproduce:

  1. Visit the URLs in the CSV
  2. Open the browser's web inspector (right-click on the page and select "Inspect").
  3. Navigate to the "Lighthouse" tab within the inspector.
  4. Run an accessibility audit.
  5. Check the audit report for heading order issues.

Acceptance Criteria:

  • All heading elements should follow a logical order (e.g., h1, h2, h3, etc.).
  • No skipped heading levels.
  • The changes should be tested using the Lighthouse tool to ensure compliance.
  • The solution should be applied to all instances listed in the CSV.

How critical is this fix?

Fixing this issue is critical as it affects the accessibility and usability of the web pages for users relying on assistive technologies. Fixing all headings will solve 9 issues on WordPress Dotorg.

Reviewed by

This ticket was automatically generated by Equalify and reviewed by the human, @bbertucc. ​​

Metadata

Metadata

Assignees

No one assigned

    Labels

    AccessibilityIssues related to keyboard navigation, screen readers, etc

    Type

    No type

    Projects

    Status

    🛑 Pending discussion

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions