Aria Native First
Use a native HTML element before applying ARIA roles, states, or properties — native semantics are more robust, require less maintenance, and have broader assistive technology support than ARIA overrides (ARIA in HTML sp…
$ aoe install @community/rule-aria-native-firstProjection
Always in _index.xml · the agent never has to ask for this.
AriaNativeFirst [rule] v1.0.0
Use a native HTML element before applying ARIA roles, states, or properties — native semantics are more robust, require less maintenance, and have broader assistive technology support than ARIA overrides (ARIA in HTML spec §2.1 'First Rule of ARIA Use').
Loaded when retrieval picks the atom as adjacent / supporting.
AriaNativeFirst [rule] v1.0.0
Use a native HTML element before applying ARIA roles, states, or properties — native semantics are more robust, require less maintenance, and have broader assistive technology support than ARIA overrides (ARIA in HTML spec §2.1 'First Rule of ARIA Use').
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Rule
Decision order:
1. Does a native HTML element express this semantics? → Use it. Done.
2. Is the native element stylistically impossible to theme? → Use it + CSS (e.g. <button>/<select> with appearance: none).
3. No native element exists for this pattern (combobox, listbox, tree, grid)? → Build with ARIA roles + full keyboard pattern.
Counter Examples
- @community/counter-example-aria-bandaid
- @community/counter-example-div-button-no-tabindex
- @community/counter-example-div-onclick-dropdown
Severity
warning
Verification
Search codebase for role='button' | role='link' | role='checkbox' | role='radio' | role='tab' on non-semantic elements; verify each has no native equivalent.
Loaded when retrieval picks the atom as a focal / direct hit.
AriaNativeFirst [rule] v1.0.0
Use a native HTML element before applying ARIA roles, states, or properties — native semantics are more robust, require less maintenance, and have broader assistive technology support than ARIA overrides (ARIA in HTML spec §2.1 'First Rule of ARIA Use').
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Rule
Decision order:
1. Does a native HTML element express this semantics? → Use it. Done.
2. Is the native element stylistically impossible to theme? → Use it + CSS (e.g. <button>/<select> with appearance: none).
3. No native element exists for this pattern (combobox, listbox, tree, grid)? → Build with ARIA roles + full keyboard pattern.
Counter Examples
- @community/counter-example-aria-bandaid
- @community/counter-example-div-button-no-tabindex
- @community/counter-example-div-onclick-dropdown
Severity
warning
Verification
Search codebase for role='button' | role='link' | role='checkbox' | role='radio' | role='tab' on non-semantic elements; verify each has no native equivalent.
Relations
related: [@community/counter-example-aria-bandaid, @community/counter-example-div-button-no-tabindex, @community/rule-keyboard-accessible, @community/counter-example-div-onclick-dropdown, @community/anti-pattern-breaking-keyboard-flow, @community/example-radix-dropdown]
Rationale
ARIA is a patch for gaps in HTML semantics, not a replacement. Native elements (
Source
aoe-engine/examples/frontend-design/primes/compiled/@community/rule-aria-native-first/atom.yaml