@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 interface copy for assumptions about disability, gender, or culture. Suggest neutral wording, clearer instructions, and constructive error messages that guide people through problems without blaming them or relying on culturally specific expressions.
Review web page headings for skipped levels, unclear labels, and incorrect structure. Organize HTML headings around the content so people using screen readers can understand page sections and navigate between them.
Audit links between pages on a website to find important pages with few incoming links. Suggest relevant connections from related content and clearer link text that describes the destination page.
Review Front-End Checklist rule files and improve their instructions, explanations, and code examples. Use the project's quality scorer and structure validator to identify gaps, replace vague prompts, and organize each rule into a usable reference for developers and agents.
Review pop-ups, modals, and banners that obscure page content. Identify mobile usability and search visibility concerns, then improve dismissal controls and keyboard focus, the element currently receiving keyboard input.
Review HSTS, a browser policy that keeps site connections on HTTPS. Check response headers, policy duration, and subdomain coverage, guide server or CDN configuration, and explain the precautions needed before enabling browser preloading.
Audit a page’s HTTP requests to find unnecessary network activity behind slow loading. Confirm bottlenecks with performance measurements, then suggest changes such as combining files, grouping icons, or embedding resources needed for the initial display.
Review JavaScript written directly in HTML and move suitable code into external files. Replace inline event handlers with addEventListener, clarify browser verification steps, and explain how separating code supports maintenance, caching, and security.
Find optional features that slow the first page load and defer their code until a user interacts. Use dynamic imports, which load code on demand, and add immediate loading feedback while preserving the initial page experience.
Review HTML forms and JavaScript requests to find data sent over unencrypted HTTP. Check submission URLs, pages with implicit form destinations, and server redirects, then update endpoints to use HTTPS.
Review website images for file format, size, dimensions, and loading behavior. Produce improved HTML with image variants for different screen sizes, suitable compression, and deferred loading where appropriate, while addressing loading speed and layout shifts.
Audit HTML page size and identify oversized embedded JSON, SVGs, images, or scripts. Use the findings to plan lighter pages and investigate whether document size could explain content missing from Google's search index.
Audit important pages for settings that interfere with search indexing, including noindex directives, HTTP headers, and robots.txt rules. Identify accidental restrictions, suggest configuration fixes, and guide follow-up checks in Google Search Console.
Review public forms for automated abuse protection. Check CAPTCHA, a mechanism for detecting bots, along with hidden trap fields and request limits, then help integrate a CAPTCHA service and validate its tokens on the server.
Audit article update dates across the visible page, HTTP response headers, and structured data that describes the article to search engines. Align these signals with substantive content changes and review how the CMS or build process updates them.
Audit page links to find missing, empty, or unusable href values and navigation handled only by JavaScript. Guide fixes using real URLs and appropriate HTML elements so search engines can discover linked pages.
Review image input buttons for missing or empty alternative text. Suggest alt attributes that describe actions such as searching or submitting, and explain how to verify that screen readers communicate each button’s purpose.
Review website images and reduce file sizes while limiting visible quality changes. Check compression, formats, display dimensions, loading behavior, and delivery settings, then recommend suitable tools or build automation and verification in browser DevTools.
Review form validation so users, including people using screen readers, can understand and correct errors. Check field descriptions, required states, and grouped choices in rendered HTML, while accounting for React forms that handle submission in the browser.
Review page language attributes so HTML and XML readers receive consistent language information. Check matching lang and xml:lang values, validate language codes, and recommend keeping both attributes for XHTML or removing the unnecessary XML attribute from standard HTML5.
Audit website image file sizes against guidelines for photos, graphics, hero images, and thumbnails. Report oversized assets with target sizes, distinguish compression issues from dimension mismatches, and guide format conversion and delivery of smaller variants to mobile devices.
Measure how Google Tag Manager affects page loading and rendering. Identify costly tags, triggers, and requests, then guide cleanup, asynchronous loading, or a move to server-side processing based on observed performance problems.
Audit whether a website serves all pages over HTTPS with valid TLS certificates, which secure connections. Check certificate coverage and expiration, permanent redirects from HTTP, and HTTPS URLs for internal links and resources, then review the necessary configuration changes.
Find JavaScript code that changes existing objects or arrays, then replace those updates with modified copies. Review shared state and browser behavior to make data changes easier to trace and check fixes in context.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)