ARIA State Attribute Pair Check
Checks a WAI-ARIA 1.2 state attribute name and a defined value token in recommended lowercase author spelling. This exact-spelling lexical pair check does not evaluate browser error recovery, role applicability or accessibility.
Description
ARIA states expose changing interface conditions through defined attribute/value tokens.
ARIA states expose changing interface conditions through defined attribute/value tokens. Lexical validity is only one part of an accessible interface.1
Checks a WAI-ARIA 1.2 state attribute name and a defined value token in recommended lowercase author spelling. This exact-spelling lexical pair check does not evaluate browser error recovery, role applicability or accessibility.
When to use ARIA State Attribute Pair Check
Use this for the following task: Checks a WAI-ARIA 1.2 state attribute name and a defined value token in recommended lowercase author spelling. This exact-spelling lexical pair check does not evaluate browser error recovery, role applicability or accessibility.
Prepare the parsed attribute values, element states or ordered local lists requested below. Keep attribute presence separate from value.
How to use ARIA State Attribute Pair Check and understand its results
- Prepare the parsed attribute values, element states or ordered local lists requested below. Keep attribute presence separate from value.
- Enter attribute, value using the field table, then run the tool.
- Read knownState, definedValue. Interpret flags, units, ordering and placeholder values using the rules below.
- Review any reported issue or failed check, correct the supplied values when appropriate, and verify the result in its intended context.
| Input field | Meaning | Value type and bounds | Requirement |
|---|---|---|---|
| attribute | Attribute | string; maximum text length 100 | Required |
| value | Value | string; maximum text length 100 | Required |
Enter a single state name and value in exact lowercase spelling. Look up the supported WAI-ARIA 1.2 state table, including deprecated aria-grabbed, and return name and paired-token recognition separately.2
knownState = attribute in supported state table; definedValue = value in its token set This summarizes the declared operation. Units, indexing, inclusivity and exceptional cases are explained in the surrounding text.
| Output field | Meaning | Value type |
|---|---|---|
| knownState | Known State | boolean |
| definedValue | Defined Value | boolean |
{
"input": {
"attribute": "aria-checked",
"value": "mixed"
},
"output": {
"knownState": true,
"definedValue": true
}
}Limitations and assumptions
Unknown strings return false flags rather than input errors. Role applicability, browser recovery and accessibility behavior are not evaluated.
This evaluates supplied local information; it does not fetch a page or run a browser. Malformed requests produce input errors. A successfully evaluated request can still contain false flags, empty result lists or a result outside the supplied threshold; those outcomes have the meanings stated above.
Alternative or Complementary methods
Choose Valid ARIA Role Names Lookup for this operation: Classifies individual WAI-ARIA 1.2 role names in their recommended lowercase author spelling as concrete, abstract or unknown. This exact-spelling vocabulary lookup excludes extensions and browser case-insensitive processing. For a complementary task, use aria-live polite/assertive/off Lookup for this operation: Classifies aria-live priorities: polite waits for an appropriate idle opportunity, assertive may interrupt, and off permits updates associated with focus. Actual assistive-technology announcements are not guaranteed.
Further background: HTML / accessibility reference: ARIA State Attribute Pair Check.
References
Similar or alternative tools
- Valid ARIA Role Names Lookup
Classifies individual WAI-ARIA 1.2 role names in their recommended lowercase author spelling as concrete, abstract or unknown. This exact-spelling vocabulary lookup excludes extensions and browser case-insensitive processing.
- aria-live polite/assertive/off Lookup
Classifies aria-live priorities: polite waits for an appropriate idle opportunity, assertive may interrupt, and off permits updates associated with focus. Actual assistive-technology announcements are not guaranteed.