@thedaviddias
Staff Front-End Engineer | Front-End Architecture, Design Systems & Accessibility | Creator of the Front-End Checklist (74K+ ⭐) and serving 100K+ devs
467 skills6 repositories 75.2K
Review the balance and relevance of internal and external links in an article. Suggest links to related site content and authoritative sources, giving readers useful next steps and supporting the article’s facts and claims.
Review ARIA attributes, which describe interface elements to assistive technology, for invalid values and missing ID references. Get specific corrections and guidance for checking that element states and labels are communicated correctly.
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.
Review article bylines to check that author names, roles, and biography links are clearly visible. Inspect rendered pages and related metadata to identify specific pages or templates that need clearer author information.
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.
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.
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.
Audit pages excluded from search results by noindex directives in HTML or response headers. Check whether important products and articles are blocked by mistake, identify affected routes, and explain appropriate corrections.
Review website images and delivery settings to introduce AVIF, an image format with efficient compression. Check image size and loading behavior, and provide WebP or JPEG alternatives for browsers that do not support AVIF.
Audit whether author profiles clearly present relevant experience, qualifications, and professional links. Review rendered pages, metadata, structured data, and HTTP responses to identify specific places where author expertise needs clearer presentation and explain how to verify improvements.
Review tooltips so keyboard and screen reader users can access their explanations. Check the rendered HTML, accessible associations, hover and focus behavior, Escape dismissal, and contrast, then identify the elements and attributes that need fixes.
Review dynamic page updates so screen reader users hear status changes without moving focus. Check ARIA live regions, areas that announce updates, choose suitable announcement urgency, and identify markup or interaction issues to verify with accessibility tools.
Review buttons, links, and menu items to check whether screen readers announce their purpose. Identify missing accessible names, meaning labels available to assistive technology, and suggest fixes using text or ARIA attributes, with guidance for verification.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
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.
Review meter elements for accessible names, the labels screen readers use to explain what a value measures. Identify missing labels, add aria-label or aria-labelledby, and describe checks using browser accessibility tools or assistive technology.
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.
Audit large animated GIFs that may slow a web page, confirm their impact with performance measurements, and guide conversion to MP4 or WebM with video markup suited to looping animations.
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 how pages return from the browser’s back/forward cache, which restores them from memory. Identify event handlers that block restoration, fix lifecycle assumptions, and refresh time-sensitive information when a cached page resumes.
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.
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 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.
Review website link text and replace vague phrases with wording that explains the destination. Check the rendered page to help search engines and people using screen readers understand where each link leads.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)