Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use correct list structure. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-19 | ✗→✓ | ▲ Improved | 23% | 0% |
| case-01 | ✓→✓ | = Same ✓ | -6% | 0% |
| case-02 | ✓→✓ | = Same ✓ | 39% | 0% |
| case-03 | ✓→✓ | = Same ✓ | 27% | 0% |
| case-04 | ✓→✓ | = Same ✓ | -3% | 0% |
Screen readers rely on a specific parent-child relationship for lists to correctly announce the number of items and the user's current position within the list.
<ul>) and ordered (<ol>) lists must only contain <li> elements<div> or <p> directly inside a list<li> elementCheck the structure of all lists to ensure only <li> elements are direct children of <ul> or <ol>.
Remove or move any non-li elements from within <ul> and <ol> tags.
Explain why assistive technology needs a consistent list structure to provide accurate navigation information.
Review the rendered markup and interactive states that affect Use correct list structure. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/list-structure
Other measured skills in the registry, with their headline benchmark lift.