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.
55
62%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/list-structure/SKILL.mdScreen 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
48405aa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.