Skip to content

header choice should be constrained #1136

@Erwan-le-Gall

Description

@Erwan-le-Gall

label: accessibility

When I insert a new header

Then I should be constrained to:

  • immediately preceding higher level
  • same level
  • immediately following loxer level

because headers hierarchy should not have "holes" in it (it must be continuous).

This is a requirement for accessibility compliance.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions