313 skills · sorted by relevance
Review keyboard focus, the element currently selected for interaction, to check that Tab navigation follows the page’s visual order. Identify HTML ordering issues and verify focus stays within dialogs and returns to their triggers.
Find empty links, unlabeled icon links, and broken destinations. Add descriptive text or labels that screen readers can announce, and fix or remove broken links so users can understand where each link leads.
Review decorative images and icons to prevent unnecessary screen reader announcements. Check empty alt text, aria-hidden, and relevant keyboard behavior, then suggest fixes for concrete accessibility issues without flagging decorative assets solely because they exist.
Review HTML lists of terms and descriptions, finding dt and dd elements used without a containing dl. Help correct the structure so assistive technologies can associate each term with its description, and explain how to verify the fix.
Review links, buttons, and form fields for duplicate HTML IDs. Identify affected controls, suggest unique IDs, and explain how to verify keyboard navigation, focus movement, and screen reader behavior after the fix.
Review rendered HTML for duplicate IDs used by ARIA attributes, which connect elements to labels and descriptions for assistive technology. Identify ambiguous references, correct IDs and their links, and explain how to verify the changes.
Find empty headings or headings containing only whitespace in rendered web pages. Guide fixes by adding descriptive text or removing unnecessary heading tags, helping screen reader users navigate a meaningful document structure.
Check HTML definition lists, which pair terms with descriptions, for structural problems. Identify invalid child elements and unclear relationships, suggest markup fixes, and explain how to verify that screen readers group the information correctly.
Review whether pages remain understandable and usable without CSS. Check reading order, headings, form labels, instructions, and errors, then suggest HTML changes that preserve meaning when styles fail or users apply their own.
Review buttons for missing or unclear names, including controls that contain only icons. Add text or labels that explain each action to screen reader users, and replace buttons used for page navigation with links.
Review HTML for deprecated ARIA roles, which describe elements to assistive technology, and abstract roles that should not appear in markup. Suggest recommended replacements or native HTML elements and explain potential browser and screen reader compatibility issues.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.
Review forms for autofocus that moves users past introductory content when a page loads. Suggest removing it or moving focus after user interaction, while considering exceptions for login pages and pages dedicated to search.
Check whether ARIA attributes, which describe interface elements to assistive technology, are supported by each element’s role. Review rendered HTML and interactive states, identify invalid combinations, and suggest removals or corrections to support accurate screen reader interpretation.
Check whether aria-hidden on the document body hides an entire page from screen readers, tools that read content aloud. Identify problematic states and suggest limiting hiding to specific background containers.
Review videos for information conveyed only through images, such as actions, expressions, and on-screen text. Identify missing audio descriptions and outline options for a separate description track, an extended version, or descriptions within the main narration.
Check buttons, links, and other controls for clear accessible names, the labels used by assistive technology. Identify missing or vague names and suggest descriptive text or aria-label attributes that explain each action or destination.
Review same-page links for accessible scrolling. Check that reduced-motion preferences disable animated scrolling, provide guidance for instant navigation, and verify that keyboard focus moves to the destination so users can continue navigating there.
Review rendered HTML for links, buttons, or inputs inside role="text" containers. Identify controls hidden from screen readers, suggest markup changes, and explain how to check keyboard access and screen reader output after fixing them.
Inspect hidden page regions for links, buttons, or inputs that still receive keyboard focus. Identify elements that screen readers cannot announce, suggest focus handling changes, and explain how to verify the resulting keyboard behavior.
Check that ARIA roles, which describe interface elements to assistive technology, include their required attributes. Identify missing state or value information in rendered HTML and get guidance on fixes and accessibility verification.
Inspect web pages for automatically playing audio and video, then remove autoplay or adjust required playback with muted defaults and accessible pause controls. Review keyboard access so users can stop media promptly.
Check HTML for misspelled or nonexistent ARIA attributes, which convey interface information to assistive technology. Replace invalid names with standard attributes and explain how to verify that screen readers can interpret element roles and states.
Check checkboxes, radio buttons, and switches for descriptive names that screen readers can announce. Identify missing or unclear labels, suggest appropriate HTML or ARIA labeling, and explain how to verify the changes with accessibility tools.