Skip to content

role=application shouldn't be treated as landmark #4663

Open
@VitalyM

Description

@VitalyM

Product

axe-core

Product Version

No response

Latest Version

  • I have tested the issue with the latest version of the product

Issue Description

Expectation

Element with role=complementary should be valid inside element with role=application

Actual

AXE treats it as error. RuleId = landmark-complementary-is-top-level

How to Reproduce

<body role="application">
  <div role="complementary">some aside thing</div>
</body>

Additional context

w3c spec doesn't have application role among landmarks
but AXE treats it so:

application: {
        type: 'landmark',
        allowedAttrs: [ 'aria-activedescendant', 'aria-expanded' ],
        superclassRole: [ 'structure' ],
        accessibleNameRequired: true
      },

Metadata

Metadata

Assignees

No one assigned

    Labels

    best practicefixBug fixesrulesIssue or false result from an axe-core rule

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions