dequelabs / dequelabs/axe-core

role=application shouldn't be treated as landmark

Open
#4,663 2 comments 0 reactions 0 assignees View on GitHub
best practice fix rules
Dominant language
JavaScript
Stars
7.5k
Forks
933
Avg merge
2d 23h
Merged PRs (30d)
17

Description

### Product

axe-core

### Product Version

_No response_

### Latest Version

- [x] 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
```html

some aside thing

```
#### Additional context
w3c [spec](https://www.w3.org/TR/wai-aria-1.2/#landmark_roles) doesn't have `application` role among landmarks
but AXE treats it so:
```js
application: {
type: 'landmark',
allowedAttrs: [ 'aria-activedescendant', 'aria-expanded' ],
superclassRole: [ 'structure' ],
accessibleNameRequired: true
},
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.