thedaviddias/Front-End-Checklist

Front-End Checklist

Front-End Checklist is the open-source front-end quality system for humans and AI agents. It turns front-end best practices into a practical review workflow you can browse on the web, run through with MCP-compatible tools, or work through directly in this README.

• Website: frontendchecklist.io
• Rules: frontendchecklist.io/rules
• MCP server: mcp.frontendchecklist.io

Companion project: UX Patterns for Devs helps developers choose the right UI pattern before using Front-End Checklist to verify implementation quality.

[!IMPORTANT] Use the website for browsing and filtering, the MCP server for agent workflows, and this README when you want the checklist in one place.

What you get

• 385 English rules across 11 active categories
• 11 MCP tools exposed by the hosted server
• Rule pages with explanations, remediation guidance, and verification steps

How to use this checklist

1. Start with the category navigator below and jump straight to the part of the checklist you need.
2. Work through the checkbox items that apply to your project, audit, or pull request.
3. Open the linked rule pages when you need the full guidance, examples, verification steps, and AI prompts.
4. Use frontendchecklist.io for interactive browsing, and mcp.frontendchecklist.io when you want agents to use the same rule corpus directly.

Priority legend

• means site-breaking, compliance-sensitive, or security-sensitive issues that should be fixed first.
• means issues with major impact on user experience, accessibility, performance, or discoverability.
• means strong best practices that should be part of normal frontend quality review.
• means useful improvements that are situational or lower urgency.

Choose your workflow

Browse online

• Explore all rules at frontendchecklist.io/rules
• Use curated checklists at frontendchecklist.io/checklists
• Open a category page for focused audits and implementation guidance

Choose the right pattern first

Front-End Checklist helps you review implementation quality. If you are still deciding what interface to build, use UX Patterns for Devs to compare common UI patterns, understand tradeoffs, and find practical guidance for forms, navigation, data display, feedback states, authentication, and AI interfaces.

Contribute to the checklist

• Install dependencies: pnpm install
• Run local development: pnpm dev
• Validate structure: pnpm validate:rule-structure
• Score the corpus: pnpm score:rules
• Regenerate derived artifacts: pnpm generate:skills and pnpm generate:readme

Use with MCP

Connect an MCP-capable agent to Front-End Checklist for frontend code review, structured rule lookup, audits, and remediation workflows across React, Next.js, HTML, CSS, JavaScript, accessibility, performance, SEO, security, images, privacy, i18n, and testing.

[!TIP] Best first use: point an MCP-capable agent at a real component, page, or public URL and explicitly ask it to use the Front-End Checklist MCP for the highest-confidence frontend findings first. Some clients discover installed MCP tools lazily, so naming the server in the prompt helps.

• Public endpoint: mcp.frontendchecklist.io
• Public docs: frontendchecklist.io/mcp
• Local/editor integration: stdio server at packages/mcp/src/cli.ts

What you can do:

• Review pasted code or file contents against the checklist
• Audit a live public URL
• Fetch a specific rule with remediation guidance
• Search rules by keyword, category, or priority
• Get a workflow or quick reference for a focused audit

Agent usage guidance:

• Use review_code first for pasted HTML, CSS, JavaScript, React, or Next.js code
• Use search_rules before making frontend accessibility, performance, SEO, security, or image recommendations
• Use get_workflow or get_checklist_rules for launch, accessibility, SEO, security, and performance audits
• Use audit_url for public https:// pages

Example prompts:

• Use the Front-End Checklist MCP to review this React component and report the highest-confidence findings first.
• Use the Front-End Checklist MCP to audit https://example.com for accessibility, performance, and SEO issues.
• Use the Front-End Checklist MCP to explain the canonical URL rule and suggest a fix with code examples.

Use with skills

Install Front-End Checklist skills when you want reusable audit workflows or focused rule-specific guidance in tools that support them.

Install:

npx skills add frontendchecklist/skills
npx skills add frontendchecklist/skills --skill https

Useful entry points:

• Global audit entry point: skills/frontend-checklist-global/SKILL.md
• Focused rule skill example: skills/https/SKILL.md

Example uses:

• Run a broad frontend audit against the full Front-End Checklist corpus
• Use a focused skill like https for security review on one concern
• Use rule-specific skills to explain why a rule matters and how to fix it

Checklist

Jump to a category

• HTML (25) · Open on the site
• CSS (32) · Open on the site
• JavaScript (26) · Open on the site
• Performance (43) · Open on the site
• Accessibility (95) · Open on the site
• SEO (94) · Open on the site
• Security (22) · Open on the site
• Images (25) · Open on the site
• Testing (13) · Open on the site
• Privacy (5) · Open on the site
• Internationalization (5) · Open on the site

Categories

HTML

25 rules. Semantic markup, metadata, forms, and document structure rules.

Browse HTML on frontendchecklist.io

• Add Subresource Integrity to external scripts : Use Subresource Integrity (SRI) hash attributes on external scripts and stylesheets loaded from CDNs to ensure the content hasn't been tampered with.
• Add thumbnail images to videos : HTML5 video elements should have a poster attribute providing a thumbnail image displayed before the video loads or is played.
• Create a custom 404 error page : A custom 404 error page is designed with helpful navigation options for lost users.
• Declare UTF-8 character encoding : The charset (UTF-8) is declared correctly as the first element in the head.
• Ensure all IDs are unique : All ID attributes are unique within the document. No duplicate IDs exist on the page.
• Implement accessible breadcrumb navigation : Breadcrumb navigation is implemented with proper semantic markup and ARIA attributes for accessibility.
• Implement favicons for all devices : All necessary favicon formats are implemented for browsers, devices, and PWA support.
• Link a Web App Manifest for installability : Include a Web App Manifest (manifest.json) linked from the HTML head to enable Progressive Web App features like home screen installation, standalone display, and splash screens.
• Load scripts with defer, async, or type=module : Prevent JavaScript from blocking HTML parsing by using defer, async, or type=module attributes on script tags so the browser can continue building the DOM while scripts download.
• Make custom elements and Web Components accessible : Custom elements must implement ARIA reflection via ElementInternals, keyboard interaction, and form association so that screen readers and assistive technologies can interpret them correctly.
• Make file uploads accessible : File upload components are accessible with proper labels, file type restrictions, and progress feedback.
• Make pagination accessible : Pagination controls are accessible with proper ARIA labels, keyboard navigation, and current page indication.
• Make search inputs accessible : Search functionality is accessible with proper input type, label, role, and autocomplete suggestions.
• Make videos accessible with captions : Videos have captions, audio descriptions, transcripts, pause controls, and avoid autoplay for users with hearing, vision, or cognitive impairments.
• Meet PWA installability criteria : The web app satisfies the browser's minimum PWA installability requirements: a valid web app manifest, a registered service worker, HTTPS, and maskable icons.
• Provide noscript fallback content : A noscript tag provides fallback content for users with JavaScript disabled.
• Remove comments and debug code in production : Unnecessary code, comments, and debug elements are removed before deploying to production.
• Set text direction for RTL languages : The dir attribute is used for languages that read right-to-left (RTL) or mixed content.
• Set the page lang attribute : The element must have a lang attribute with a valid BCP 47 language code so screen readers, translation tools, and search engines know the primary language of the page.
• Set the responsive viewport meta tag : The viewport meta tag is declared correctly for responsive design.
• Use semantic HTML elements : HTML5 Semantic Elements are used appropriately (header, section, footer, main, article, aside...).
• Use semantic input type attributes : Set the correct type attribute on input elements to trigger the right mobile keyboard, enable browser validation, and improve autofill accuracy.
• Use the HTML5 doctype : The HTML5 doctype declaration must appear as the first line of every HTML document to trigger standards mode rendering in all browsers.
• Validate forms accessibly : Forms provide clear validation feedback with accessible error messages and proper ARIA attributes.
• Validate HTML against W3C standards : HTML markup is validated against W3C standards for cross-browser compatibility.

Back to top

CSS

32 rules. Layout, typography, responsive design, and styling rules.

Browse CSS on frontendchecklist.io

• Apply Flexbox best practices : Use Flexbox for one-dimensional layouts with the right properties, avoiding common mistakes like overusing flex:1, ignoring min-width:0, and misunderstanding flex-basis.
• Avoid embedded and inline CSS : Embedded and inline CSS are avoided except for critical CSS and performance optimization.
• Avoid intrusive interstitials : Full-screen interstitials (pop-ups, overlays, cookie banners) that block the main content on mobile are a ranking penalty signal and accessibility barrier. Use non-intrusive alternatives.
• Do not disable pinch zoom : The viewport meta tag must not set user-scalable=no or maximum-scale=1 as these prevent users from zooming in to read content, violating WCAG 2.1 SC 1.4.4 (Resize Text).
• Include a print stylesheet : A print stylesheet is provided and correctly optimized for printed pages.
• Inline critical CSS for faster rendering : Critical CSS (above-the-fold content) is inlined in the head for faster initial render.
• Keep CSS specificity low and flat : Write selectors at the lowest specificity that works, avoiding ID selectors and deep nesting, so styles can be overridden cleanly without resorting to !important.
• Lint CSS and SCSS files : All CSS/SCSS files are linted with Stylelint to detect errors and enforce standards.
• Load CSS without blocking render : Non-critical CSS is loaded asynchronously to avoid blocking DOM rendering.
• Minify all CSS files : All CSS files are minified to reduce file size and improve page load performance.
• Optimize web font formats : Web fonts use modern formats (WOFF2, WOFF) with proper fallbacks and loading strategies.
• Order CSS files correctly : All CSS files are loaded before JavaScript files to prevent render blocking.
• Prevent horizontal scrolling : Web pages must not require horizontal scrolling at standard viewport widths. Horizontal overflow breaks responsive layouts and makes content inaccessible to low-vision users who zoom in.
• Provide visible custom focus indicators : Ensure all interactive elements have a clearly visible focus indicator for keyboard navigation — never just remove the default outline without providing a better alternative.
• Register CSS custom properties with @property for animation and type safety : Use @property to register CSS custom properties with a type, initial value, and inheritance control — enabling animation of custom properties and providing compile-time validation for design tokens.
• Remove unused CSS rules : Unused CSS is removed to reduce bundle size and improve performance.
• Support dark mode with prefers-color-scheme : Implement dark mode using the prefers-color-scheme media query and CSS custom properties so the site automatically adapts to the user's system preference.
• Use :has() to style parent elements based on their descendants : Use the CSS :has() relational pseudo-class to select and style an element based on what it contains, replacing JavaScript DOM manipulation for many common styling scenarios.
• Use @layer to manage CSS cascade order explicitly : CSS Cascade Layers (@layer) are used to give the codebase explicit, predictable control over specificity and cascade order, eliminating the need to fight specificity with !important.
• Use a CSS reset or normalize stylesheet : A CSS reset or normalize is used to ensure consistent styling across browsers.
• Use consistent CSS naming conventions : Adopt a consistent class naming methodology (BEM, CUBE CSS, or a team-agreed pattern) to make class names self-documenting and prevent style conflicts.
• Use container queries for component-level responsiveness : Use CSS container queries to make components respond to their own container's size rather than the viewport, enabling truly reusable responsive components.
• Use CSS containment to limit repaint scope : Apply the contain property to components to tell the browser they are independent from the rest of the page, enabling rendering optimizations that reduce repaint and reflow scope.
• Use CSS custom properties for design tokens : Define design system values (colors, spacing, typography) as CSS custom properties on :root to enable consistent theming, dynamic updates, and dark mode support.
• Use CSS Grid for two-dimensional layouts : Use CSS Grid when you need to control both rows and columns simultaneously, such as page layouts, card grids, and complex component arrangements.
• Use CSS logical properties for i18n and RTL support : Use CSS logical properties (margin-inline, padding-block, border-inline-start) instead of physical properties (margin-left, padding-top) to support right-to-left languages automatically.
• Use CSS subgrid to align nested grid items to parent tracks : Use grid-template-columns: subgrid (or subgrid for rows) to make nested grid items participate in the parent grid's tracks, solving the card-content alignment problem without JavaScript height matching.
• Use oklch() and oklab() for perceptually uniform colour palettes : Colour values in the design system use oklch() or oklab() colour functions to produce perceptually uniform palettes where equal numeric steps produce equal perceived lightness changes.
• Use readable font sizes on mobile : Text must be large enough to read without zooming on mobile devices. Using relative units (rem/em) allows browser font size preferences to be respected.
• Use relative units for responsive layouts : Use rem, em, %, vw, vh, and clamp() instead of fixed px values to build layouts that scale with user font size preferences and viewport dimensions.
• Use the View Transitions API for smooth page and component transitions : The View Transitions API is used to animate between page states or navigations with cross-fade or custom animations, providing a native-app quality transition without JavaScript animation libraries.
• Use transform and opacity for animations : Animate with CSS transform and opacity properties to keep animations running on the GPU compositor thread at 60fps, avoiding layout-triggering properties like top, left, width, and height.

Back to top

JavaScript

26 rules. Client-side behavior, async patterns, and runtime quality rules.

Browse JavaScript on frontendchecklist.io

• Avoid implicit type coercion : Use strict equality (===), explicit type conversion, and Number/String/Boolean constructors to avoid JavaScript's implicit type coercion producing unexpected results.
• Avoid inline JavaScript : Inline JavaScript is avoided. JavaScript is kept in external files for caching and maintainability.
• Avoid the any type — use unknown, generics, or type guards instead : Replace TypeScript's any type with unknown, proper generics, or narrowed type assertions to preserve type safety without sacrificing expressiveness.
• Debounce and throttle event handlers : Use debounce or throttle for high-frequency events like scroll, resize, and input to improve performance.
• Enable noUncheckedIndexedAccess to catch out-of-bounds array bugs : Enable noUncheckedIndexedAccess in tsconfig.json to make array and object index access return T | undefined, forcing explicit null checks that prevent out-of-bounds runtime errors.
• Enable TypeScript strict mode in tsconfig.json : Enable "strict": true in tsconfig.json to activate the full suite of TypeScript type-checking flags and catch the most common runtime bugs at compile time.
• Handle cross-origin requests securely : Use CORS correctly, validate message origins with postMessage, and understand the Same-Origin Policy to prevent cross-origin attacks.
• Implement proper error handling : Use try-catch blocks and error boundaries to gracefully handle errors in async operations and UI components.
• Lint JavaScript code : JavaScript code is linted with ESLint to detect errors and enforce coding standards.
• Minify all JavaScript files : All JavaScript files are minified to reduce file size and improve loading performance.
• Minimize costly DOM read/write operations : Batch DOM reads and writes separately to avoid layout thrashing — the performance problem caused by alternating between reading and writing layout properties.
• Never use eval() or unsafe dynamic code execution : Avoid eval(), new Function(), setTimeout/setInterval with string arguments, and innerHTML with untrusted content — they execute arbitrary code and create critical XSS vulnerabilities.
• Parse JSON safely with error handling : Always wrap JSON.parse() in try/catch and validate the parsed structure before use, as invalid JSON or unexpected data shapes cause runtime errors.
• Prefer const and let over var : Use block-scoped const and let declarations instead of function-scoped var to avoid hoisting bugs and unintended variable mutations.
• Prefer immutable data patterns : Use spread operators, Object.assign, and array methods that return new values instead of mutating objects and arrays in place, to make data flow predictable and debugging easier.
• Prevent common memory leak patterns : Identify and avoid the most common JavaScript memory leak sources: forgotten event listeners, retained DOM references, closures holding large objects, and uncleared timers.
• Remove console statements in production : Remove or disable console.log, console.debug, and other console statements before deploying to production.
• Split large JavaScript bundles : Use dynamic imports and route-based code splitting to break large bundles into smaller chunks that load on demand, reducing initial page load time.
• Use ES modules (import/export) : Use native ES module syntax for imports and exports instead of CommonJS require() to enable static analysis, tree-shaking, and better tooling support.
• Use event delegation for dynamic content : Attach event listeners to stable parent elements rather than individual dynamic children to reduce memory usage and handle elements added to the DOM after page load.
• Use import type for type-only imports : Use the import type syntax for imports that are only needed as TypeScript types, ensuring they are fully erased at compile time with zero runtime cost.
• Use modern array and object methods : Use ES2015+ array methods (map, filter, reduce, find, flatMap) and object methods (Object.entries, Object.fromEntries, structuredClone) for cleaner, more expressive code.
• Use scheduler.yield() to keep the main thread responsive during long tasks : Break up tasks longer than 50 ms by yielding to the browser with scheduler.yield() or a MessageChannel fallback so that user input is never blocked.
• Use Web Storage API safely : Use localStorage and sessionStorage with proper serialization, error handling, and security awareness to avoid data corruption and storage quota errors.
• Validate external data at runtime with a schema library : Use Zod or Valibot to validate data from API responses, form inputs, localStorage, and environment variables — TypeScript types are erased at runtime and cannot protect against unexpected shapes.
• Write internationalisation-friendly translation strings : Translation strings use message format patterns (ICU or similar) rather than string concatenation, and correctly handle pluralisation, gender, and variable interpolation.

Back to top

Performance

43 rules. Loading speed, rendering, optimization, and Core Web Vitals rules.

Browse Performance on frontendchecklist.io

• Analyze performance with WebPageTest : Page performance is analyzed with WebPageTest to identify loading bottlenecks and optimization opportunities.
• Avoid JavaScript-based redirects : Detects JavaScript resources that return 3XX redirects to reduce latency
• Avoid serving legacy JavaScript to modern browsers : Detects ES5 polyfills and legacy JavaScript code to reduce bundle size and improve execution
• Convert animated GIFs to video : Large animated GIFs are replaced with more efficient video formats like MP4 or WebM to reduce page weight.
• Disable lazy loading for above-the-fold content : Detects lazy loading on likely above-fold images to improve Largest Contentful Paint (LCP)
• Eliminate render-blocking resources : Checks for render-blocking CSS and JavaScript that prevent the initial page render
• Enable browser caching : Cache-Control and ETag headers are properly configured for static resources.
• Enable HTTP/2 or HTTP/3 : Use modern HTTP protocols to enable request multiplexing and reduce network latency.
• Enable text-based compression : Compress text resources (HTML, CSS, JS) using Gzip or Brotli to reduce data transfer size.
• Implement Google Consent Mode v2 : Adjust Google Tag behavior based on user consent to comply with privacy regulations and maintain data insights.
• Implement lazy loading for offscreen content : Images and heavy resources below the fold are lazy loaded to improve initial performance.
• Keep page load time under 3 seconds : Page fully loads in under 3 seconds on a standard connection.
• Keep page weight under 1500KB : Total page weight including all resources is under 1500KB (ideally under 500KB).
• Load non-critical code on user interaction : Defer JavaScript modules, widgets, and third-party code until the user signals intent through a click, focus, hover, or similar interaction.
• Load non-critical code when content approaches the viewport : Use viewport-aware loading to fetch components, embeds, and feature code shortly before they become visible instead of shipping them on first load.
• Minimize critical request chains : Reduce the number and depth of dependent resource requests that block the initial rendering of the page.
• Minimize cumulative layout shift : Page maintains visual stability with a CLS score below 0.1, preventing unexpected content shifts during load.
• Minimize HTTP requests : HTTP requests are minimized by combining files, using sprites, and HTTP/2.
• Optimize CSS file size : Keep individual CSS files small and remove unused styles to accelerate the critical rendering path.
• Optimize first contentful paint : First content renders within 1.8 seconds, providing quick visual feedback that the page is loading.
• Optimize Google Tag Manager implementation : Configure Google Tag Manager efficiently to minimize its impact on page load speed and main-thread blocking.
• Optimize interaction to next paint : Page responds to user interactions within 200ms, ensuring good responsiveness.
• Optimize JavaScript bundle size : Checks for JavaScript files that exceed recommended size limits to ensure fast interaction
• Optimize largest contentful paint : The largest content element loads within 2.5 seconds for a good user experience.
• Optimize pages for back/forward cache : Pages avoid back/forward cache blockers such as unload listeners and restore state correctly when a browser resumes them from memory.
• Optimize third-party script loading : Load third-party scripts asynchronously to prevent blocking the main thread and improve page performance.
• Optimize web font loading : Use efficient font formats and loading strategies to prevent layout shifts and invisible text.
• Perform browser-based performance audits : Conduct performance audits in a full browser environment to capture accurate runtime metrics and layout shifts.
• Provide an offline fallback page : When the network is unavailable, users are shown a custom offline fallback page rather than the browser's generic error screen.
• Provide source maps for production debugging : Checks for source map availability and configuration to ensure easier debugging
• Reduce DOM size and complexity : Keep the DOM tree small and shallow to improve memory usage and rendering performance.
• Reduce Time to First Byte (TTFB) : Measures and optimizes server response time (TTFB) to ensure a fast initial response
• Register a service worker for caching and offline support : A service worker is registered to intercept network requests, cache critical assets, and enable offline functionality for your web application.
• Remove duplicate JavaScript libraries : Detect and consolidate duplicate JavaScript libraries to reduce bundle size and prevent version conflicts.
• Show loading indicators : Loading indicators provide feedback during asynchronous operations to keep users informed of progress.
• Stream HTML to the browser before the full response is ready : Use HTTP chunked transfer encoding and React renderToPipeableStream (or ReadableStream) to begin delivering HTML to the browser as soon as the first bytes are available, reducing Time to First Byte and First Contentful Paint.
• Use a content delivery network : Static assets are served from a CDN for reduced latency and faster delivery.
• Use fetchpriority to hint resource loading priority : The fetchpriority attribute is applied to critical images, scripts, and preload links to help the browser prioritise the most important resources and defer lower-priority ones.
• Use preconnect for critical third-party origins : Checks for preconnect hints to critical third-party origins to reduce connection latency
• Use resource hints for faster loading : Implement preload, prefetch, and preconnect hints to optimize resource loading priority.
• Use secure and up-to-date JS libraries : Detects JavaScript libraries and checks for known vulnerabilities
• Use the Speculation Rules API to prefetch and prerender navigations : The Speculation Rules API is used to declaratively prefetch or prerender likely next pages, making navigation feel near-instant without the overhead of a full client-side router.
• Virtualize long lists and tables : Render only the visible subset of rows or cards in large collections to reduce DOM size, memory usage, and scroll-time rendering work.

Back to top

Accessibility

95 rules. Keyboard, screen reader, ARIA, and inclusive UX rules.

Browse Accessibility on frontendchecklist.io

• Align visible labels with accessible names : The accessible name of a control should contain its visible label text.
• Allow pasting into form inputs : Users should be able to paste content into form fields to improve usability and reduce errors.
• Announce dynamic content with ARIA live regions : Dynamic content updates are announced to screen readers using appropriate ARIA live regions.
• Associate labels with form controls : Form inputs must have programmatically associated labels.
• Avoid autofocus on form fields : Form fields do not use the autofocus attribute which can disorient screen reader users and cause unexpected page behavior.
• Avoid autoplaying media : Audio and video content does not autoplay, or provides immediate controls to pause or stop playback.
• Avoid focusable descendants in role="text" elements : Checks that elements with role='text' have no focusable descendants
• Avoid images of text : Real text is used instead of images containing text, except for logos or when specific visual presentation is essential.
• Avoid meta refresh redirects : Meta refresh redirects can disorient users and cause accessibility issues by refreshing the page unexpectedly.
• Avoid redundant entry in the same process : Information already provided earlier in a multi-step flow is auto-populated or available for selection instead of being typed again.
• Avoid redundant image alternative text : Alternative text should not contain redundant words like 'image' or 'photo'.
• Avoid scrolljacking and custom scroll behavior : Natural scroll behavior is preserved without custom scroll speeds, directions, or hijacked scroll events.
• Avoid sensory-only instructions : Instructions do not rely solely on sensory characteristics like color, shape, size, location, or sound.
• Avoid using deprecated ARIA roles : Checks for deprecated or abstract ARIA roles to ensure long-term compatibility.
• Create accessible tooltips : Tooltips are accessible to keyboard users and screen readers with proper ARIA attributes and focus handling.
• Define proper table headers : Checks that data tables have proper headers
• Do not use aria-hidden on the document body : Ensures the document body is not set to aria-hidden, which would hide the entire page from screen readers.
• Enable keyboard navigation for all elements : All interactive elements are accessible via keyboard with logical focus order and hidden elements excluded from tab sequence.
• Ensure accesskey values are unique : Checks that accesskey values are unique to avoid shortcut conflicts.
• Ensure all input fields have accessible names : Checks that input fields have accessible names so screen reader users know what data each field expects.
• Ensure ARIA attributes are valid : All ARIA attributes must be valid and exist in the WAI-ARIA specification.
• Ensure ARIA roles are contained by required parent roles : Checks that elements with certain roles have required parent roles
• Ensure ARIA roles contain required child roles : Elements with certain ARIA roles must contain the required child roles or the widget structure will be broken for assistive technologies.
• Ensure content remains usable without CSS : Content structure, instructions, and primary tasks remain understandable and operable when author CSS is disabled or replaced by user styles.
• Ensure dialogs have an accessible name : Checks that dialog elements have accessible names to orient screen reader users.
• Ensure headings contain text : All heading elements (h1-h6) must have visible, descriptive content.
• Ensure identical links have consistent destinations : Links with the same text must point to the same destination or be distinguishable.
• Ensure logical focus order : Tab focus order follows the visual layout and logical reading sequence of the page.
• Ensure table headers associate with data cells : Checks that table headers have associated data cells
• Ensure tables have unique accessible names : Checks that data tables have unique accessible names
• Fix empty and broken links : All links contain accessible text content and do not lead to broken destinations.
• Hide decorative elements from assistive technology : Decorative images and visual elements are hidden from screen readers using aria-hidden or empty alt attributes.
• Implement "Skip to Content" links : Checks for bypass mechanisms for keyboard navigation
• Include a skip navigation link : A skip navigation link is provided to allow keyboard users to bypass repetitive content and navigate directly to main content.
• Include required ARIA attributes for roles : Checks that elements have required ARIA attributes for their roles
• Keep focused elements unobscured : Sticky headers, footers, banners, and overlays must not fully hide the element that currently has keyboard focus.
• Keep repeated help mechanisms in a consistent location : When help or support mechanisms appear on multiple pages in the same flow, they stay in the same relative order so users can find them predictably.
• Link table cells to headers using IDs : Checks that td headers attribute references valid th ids
• Maintain logical heading order : Heading levels should follow a sequential, hierarchical order.
• Make accordions keyboard navigable : Accordion components use proper ARIA attributes and keyboard interactions for screen reader accessibility.
• Make carousels accessible : Carousels and sliders are accessible with pause controls, keyboard navigation, and proper ARIA attributes.
• Make drag and drop accessible : Drag and drop interfaces provide keyboard alternatives and proper ARIA attributes for accessibility.
• Make links in text blocks visually distinguishable : Links within blocks of text must be distinguishable from surrounding non-link text by more than color alone.
• Make modal dialogs keyboard accessible : Modal dialogs are accessible with proper focus trapping, ARIA attributes, and keyboard dismissal.
• Make notifications accessible : Toast notifications and alerts are announced to screen readers using ARIA live regions and appropriate roles.
• Make tabs keyboard navigable : Tab components implement the ARIA tabs pattern with proper roles, states, and keyboard navigation.
• Manage focus during dynamic interactions : Focus is programmatically managed during dynamic interactions like modals, page transitions, and content updates.
• Match lang and xml:lang attributes : The lang and xml:lang attributes on the html element must have identical values to avoid conflicting language signals across HTML and XML parsers.
• Meet minimum color contrast ratios : Text and background colors must have sufficient contrast to be readable by users with low vision or color blindness.
• Place list items within list containers : List item elements (li) must always be direct children of a list container (ul, ol, or menu) to maintain valid HTML structure and correct screen reader announcements.
• Prevent data loss from session timeouts : Users are warned before session expiry, can extend time when appropriate, and can re-authenticate or resume work without losing entered data.
• Prevent seizure-triggering flashing content : Content does not flash more than three times per second to prevent seizures in users with photosensitive epilepsy.
• Provide accessible authentication methods : Authentication flows avoid unnecessary cognitive tests and support assistive mechanisms such as password managers, paste, OTP autofill, and passkeys.
• Provide accessible names for all interactive elements : Checks that interactive elements have accessible names for clear navigation.
• Provide accessible names for ARIA command elements : Checks that command elements like buttons and links have accessible names for screen reader support.
• Provide accessible names for buttons : All buttons must have a discernible, descriptive accessible name for screen readers.
• Provide accessible names for meter elements : Checks that meter elements have accessible names to provide context for measurements.
• Provide accessible names for progress bars : Checks that progressbar elements have accessible names
• Provide accessible names for select elements : All <select> elements must have an associated label or an accessible name to be correctly identified by screen readers.
• Provide accessible names for toggle fields : Checks that toggle fields (checkbox, radio, switch) have accessible names
• Provide accessible names for tooltips : Checks that tooltip elements have accessible names
• Provide accessible names for tree items : All elements with role="treeitem" must have a descriptive accessible name so screen reader users can navigate hierarchical tree widgets.
• Provide alt text for image buttons : Input elements of type='image' must have a descriptive alt attribute.
• Provide alternative text for objects : The <object> element must contain alternative content to ensure accessibility for users who cannot view the primary content.
• Provide alternatives to parallax effects : Parallax scrolling effects have reduced-motion alternatives or can be disabled by users.
• Provide audio descriptions for video : Videos with important visual content include audio descriptions that narrate visual information for blind users.
• Provide captions for video content : Prerecorded video with audio must have synchronized captions. Live video must have real-time captions. This is required by WCAG 2.1 SC 1.2.2 and SC 1.2.4.
• Provide instant anchor scroll option : Smooth scroll animations to anchor links respect motion preferences or provide an instant alternative.
• Provide sufficient touch target size : Interactive elements must have large enough touch targets so users with motor impairments can activate them accurately on touchscreen devices.
• Provide titles for iframes and frames : iframes and frames must have a title attribute to describe their content.
• Remove focusable elements from aria-hidden containers : Ensures aria-hidden elements do not contain focusable content to avoid "ghost" focus.
• Respect reduced motion preferences : Animations respect user motion preferences, avoid seizure-triggering flashing, and include warnings for excessive motion.
• Support both portrait and landscape orientation : Content and functionality work in both portrait and landscape unless a specific orientation is essential to the activity.
• Support content reflow at 400% zoom : Content reflows when zoomed to 400% without requiring horizontal scrolling or loss of functionality.
• Support text resizing to 200% : Text can be resized up to 200% without loss of content or functionality using browser settings.
• Test with screen readers : Pages must be tested with actual screen reader software (NVDA, JAWS, VoiceOver, TalkBack) to verify announcements, focus order, and widget behavior beyond what automated tools can detect.
• Use a single label for each form field : Form fields should have exactly one associated element for maximum clarity.
• Use appropriate tabindex values : Checks for appropriate tabindex values
• Use correct definition list structure : Definition lists (<dl>) must only contain valid <dt> and <dd> elements.
• Use correct list structure : Lists (ul, ol) should only contain list item elements (li) to ensure they are correctly interpreted by assistive technology.
• Use descriptive link text : Link text clearly describes the destination or purpose without relying on surrounding context.
• Use exactly one main landmark : Each page must have one and only one main landmark.
• Use inclusive language : Content uses inclusive, non-discriminatory language that welcomes all users regardless of ability, gender, race, or background.
• Use landmark regions correctly : Proper landmark regions (main, nav, footer) help users navigate the page more efficiently.
• Use logical heading hierarchy : Headings follow a sequential structure (h1 to h6) that reflects the content hierarchy without skipping levels.
• Use navigation landmark regions : Page navigation uses nav elements with proper ARIA labels to distinguish multiple navigation regions.
• Use only allowed ARIA attributes for each role : Checks that ARIA attributes are allowed on their elements to ensure valid accessibility trees.
• Use semantic list elements : Groups of related items use ul, ol, or dl elements so screen readers announce list context and item count.
• Use semantic table markup for screen readers : Data tables use proper semantic markup with headers, captions, and scope attributes for screen reader accessibility.
• Use unique IDs for active elements : All focusable or active elements must have a unique ID attribute.
• Use unique IDs for ARIA references : IDs referenced by ARIA attributes must be unique to ensure correct accessibility relationships.
• Use valid ARIA role values : Checks for valid ARIA role values
• Use valid values for ARIA attributes : Checks for valid values in ARIA attributes
• Wrap definition items in a definition list : Description terms (<dt>) and details (<dd>) must be contained within a <dl> element.
• Write in plain language : Content uses clear, simple language that is easy to understand for users with cognitive disabilities and non-native speakers.

Back to top

SEO

94 rules. Crawlability, metadata, structured data, and search visibility rules.

Browse SEO on frontendchecklist.io

• 4XX Pages in Sitemap : Checks for sitemap URLs that return 4XX HTTP status codes, indicating broken or removed pages.
• Add a favicon to every page : Checks for favicon presence and correct link element configuration
• Add disclaimers to sensitive content : Checks for appropriate disclaimers on sensitive content types such as medical, legal, financial, and affiliate pages
• Add FAQPage schema markup : Validates FAQPage JSON-LD structured data for question-and-answer content
• Add internal links to key pages : Validates that key pages receive adequate internal links from other site pages
• Add internal links to orphan pages : Detects pages with no internal links pointing to them
• Add LocalBusiness schema markup : Validates LocalBusiness schema for local SEO
• Add Organization schema markup : Validates Organization schema for brand presence
• Add outgoing links to dead-end pages : Pages with no outgoing internal links, potentially trapping users and crawlers
• Add Product schema markup : Validates Product schema for e-commerce
• Add relevant external links : Validates that pages include outgoing links to authoritative external sources where appropriate
• Add Review schema markup : Validates Review and AggregateRating schema on product, service, and business pages to enable star-rating rich results.
• Add share buttons to content pages : Checks for social sharing buttons on articles, blog posts, and other shareable content pages.
• Add structured data markup : Schema.org structured data (JSON-LD) is implemented for rich search results.
• Add Twitter Card meta tags : Validates Twitter (X) Card meta tags for correct card type, image dimensions, and required fields.
• Add VideoObject schema to video pages : Checks for VideoObject structured data on pages containing video content to enable video rich results in Google Search.
• Audit all noindex pages : Lists and reviews all pages blocked from indexing to ensure critical content is accessible.
• Audit and refine AI-generated content : Detects and reviews content that appears to be primarily AI-generated to ensure quality.
• Avoid conflicting indexability signals : Detects conflicting signals between robots.txt, meta robots, X-Robots-Tag headers, and canonical tags
• Avoid duplicate meta descriptions : Checks for duplicate meta descriptions across the site
• Avoid keyword stuffing : Detects excessive keyword repetition in content, titles, or meta tags that signals manipulative SEO
• Avoid multi-hop redirect chains : Detects multi-hop redirect chains that waste crawl budget
• Avoid nofollow on internal links : Flags internal links with rel=nofollow
• Avoid nosnippet on important pages : Detects pages preventing search engine snippets
• Avoid redirect chains on canonical URLs : Ensures that canonical tags point directly to the final destination URL without intermediate redirects.
• Avoid thin content on key pages : Checks content length on key pages to identify thin content that may underperform in search results.
• Check for broken links : All links are tested and none are broken. Links redirect to intended destinations.
• Cite authoritative external sources : Checks for citations to reputable external websites to back up factual claims and build trust.
• Create a comprehensive Contact page : Checks for a dedicated contact page with multiple methods for users to reach out.
• Create a dedicated About page : Checks for a dedicated about or company page with meaningful content.
• Create and submit an XML sitemap : An XML sitemap is available at /sitemap.xml and includes all important pages.
• Display a physical business address : Checks for visible physical address information
• Display clear author bylines : Checks for visible author names on content pages to establish transparency and trust.
• Do not link from HTTPS to HTTP : Detects links from HTTPS pages to HTTP destinations, which trigger mixed content warnings and lose ranking signals
• Fix invalid links : Detects malformed, empty, or syntactically invalid link formats on the page
• Fix malformed HTML structure : Ensures that the HTML document is well-formed with correctly nested and closed tags.
• Fix or remove broken external links : Detects and resolves external links that return error codes or have timed out.
• Geo Meta Tags : Checks for geographic meta tags for local or regional targeting
• Highlight author credentials and expertise : Checks for author bios and credentials to establish expertise and trust.
• Identify YMYL content on your site : Detects Your Money or Your Life (YMYL) content that is subject to Google's elevated E-E-A-T quality standards.
• Implement comprehensive author markup : Uses structured data to provide machine-readable metadata about content authors.
• Implement valid Article structured data : Validates that articles use the correct Schema.org properties for improved search visibility.
• Implement valid BreadcrumbList schema : Adds structured data to breadcrumb navigation for better site hierarchy and search appearance.
• Include indexable pages in your sitemap : Checks for canonical-url, indexable pages that are missing from the XML sitemap.
• Include keywords in URL slugs : Checks if URL slugs contain descriptive, keyword-relevant words instead of IDs, random strings, or vague terms.
• Keep HTML documents under crawl limits : Checks HTML document size against Googlebot crawl limits
• Keep linked PDFs under 60 MB : Checks linked PDF sizes against Googlebot 60MB truncation limit
• Keep NAP details consistent : Checks for consistent Name, Address, Phone across site
• Keep page titles unique : Checks that the tag is unique across all pages of the site to avoid duplicate title SEO issues.
• Keep sitemap URLs on the correct domain : Checks that all URLs in the sitemap belong to the same domain and protocol as the sitemap itself.
• Keep URLs concise : Checks URL length for optimal crawlability and usability
• Keep XML sitemaps valid : Validates sitemap XML structure against the sitemaps.org protocol, URL limits, and encoding requirements.
• Limit unnecessary URL parameters : Checks for excessive URL parameters
• Link directly to final destination URLs : Detects URLs that redirect and links pointing to redirects
• Link to active social profiles : Checks for links to the organization's social media profiles to help search engines connect the site to its social entity and build E-E-A-T signals.
• Make content easy for LLMs to parse : Analyzes how well LLMs can parse and understand the content
• Make important pages indexable : Identifies important pages blocked from search engine indexing by noindex, robots.txt, or other directives
• Meta Tags in Body : Detects meta tags incorrectly placed in document body
• MIME Type Validation : Detects Content-Type header mismatches with file extensions
• Noindex in Sitemap : Checks for noindexed pages listed in sitemap
• OG Image Size : Checks og:image meets recommended size (1200x630)
• OG URL Match : Checks that og:url matches canonical URL
• Open Graph Tags : Validates Open Graph meta tags for social sharing
• Optimize article link density : Ensures articles have a healthy balance of internal and external links relative to their length.
• Provide clear affiliate disclosures : Checks for affiliate and sponsored content disclosures to maintain transparency.
• Publish a robots.txt file : Checks if robots.txt exists at the root, is accessible, and contains valid directives.
• Publish an editorial policy page : Checks for editorial and content policy pages that demonstrate site-wide trustworthiness
• Publish high-quality content : LLM-based content quality analysis for SEO
• Publish llms.txt for documentation-heavy sites : Offer an optional llms.txt index that points AI tools to high-value documentation pages and, when useful, a fuller llms-full.txt companion.
• Resolve internal broken links : Detects and fixes internal links that return 404 or 5xx errors to improve user experience.
• Robots Meta Conflict : Detects pages blocked by robots.txt that also carry noindex meta tags, creating a paradox where the directive is never read.
• Schema + Noindex Conflict : Detects pages that carry rich result schema markup but are blocked from indexing via noindex or robots.txt.
• Service Area Pages : Checks for properly structured service-area or location pages for businesses serving multiple geographic regions.
• Set canonical URLs for all pages : A canonical URL tag is present to prevent duplicate content issues.
• Set robots meta directives correctly : Checks robots meta tag for valid indexing directives in the page head.
• Show content freshness signals : Checks for last-modified and published date signals that help Google assess content currency
• Show published and updated dates : Checks for published and modified dates on content pages
• Show trust signals on key pages : Checks for trust badges, certifications, client logos, testimonials, and social proof on high-conversion pages.
• Sync HTML canonical tags and Link headers : Ensures consistency between HTML rel="canonical" tags and HTTP Link canonical-url headers.
• Tel & Mailto Links : Validates that phone numbers use the tel: scheme and email addresses use the mailto: scheme for one-click contact on mobile devices.
• URL Special Characters : Checks for problematic special characters in URL paths that can cause crawling, parsing, or canonicalization issues.
• URL Stop Words : Flags common stop words in URL slugs that add length without improving keyword relevance.
• Use a single descriptive H1 : Validates that each page has exactly one H1 tag containing a descriptive, keyword-relevant heading
• Use canonicals on paginated pages : Checks that paginated pages have proper canonicals
• Use descriptive anchor text : Checks for descriptive, keyword-rich anchor text that provides context for users and search engines.
• Use hyphens in URLs : Checks that URL slugs use hyphens as word separators, not underscores or spaces
• Use lowercase URLs : Checks that URLs are lowercase
• Use trailing slashes consistently : Checks for consistent trailing slash usage across all URLs to avoid duplicate content and canonicalization issues.
• Use valid JSON-LD structured data : Validates JSON-LD structured data for syntax correctness, required properties, and schema.org compliance
• Weak Internal Links : Detects pages with very few dofollow internal links pointing to them, indicating poor link equity distribution and crawl discoverability.
• WebSite Search Schema : Checks for WebSite schema with SearchAction to enable the Sitelinks Searchbox in Google Search results.
• Write a descriptive page title : Validates page title presence and length
• Write a meta description for each page : Validates meta description presence and length
• Write at a clear reading level : Analyzes content readability using Flesch-Kincaid

Back to top

Security

22 rules. Headers, transport, safe linking, and frontend security rules.

Browse Security on frontendchecklist.io

• Adblock Element Hiding : Checks for HTML elements and CSS classes that would be hidden by common adblockers, causing layout breaks or missing functionality for users with ad blocking enabled.
• Audit dependencies for known vulnerabilities : Dependencies are regularly scanned for known security vulnerabilities using automated tooling, and critical findings are remediated before deployment.
• Avoid mixed content on HTTPS pages : An HTTPS page that loads resources over HTTP has mixed content — browsers block or warn about these requests, breaking functionality and undermining transport security.
• Blocked Tracking Links : Links and resources pointing to known tracking or advertising domains may be blocked by adblockers, breaking navigation and functionality for a significant portion of users.
• External Link Security : Links that open in a new tab using target='_blank' must include rel='noopener noreferrer' to prevent the opened page from accessing the opener's window context.
• Implement a content security policy : A Content Security Policy is implemented to prevent XSS attacks and control resource loading.
• Leaked Environment Variables : Checks for exposed API keys, tokens, passwords, and other secrets embedded in HTML source, JavaScript bundles, or client-accessible files.
• Link to your terms of service in the footer : Websites offering services to users should publish Terms of Service and link to them from every page — this establishes the legal agreement governing use of the service.
• Prevent stack trace exposure in production error responses : Production error responses never include stack traces, internal file paths, framework internals, or other debugging detail that could aid an attacker (OWASP A09).
• Protect public forms with CAPTCHA : Public forms that accept user input without authentication must include bot protection to prevent spam, credential stuffing, and automated abuse.
• Redirect HTTP to HTTPS : All HTTP requests must be permanently redirected (301) to HTTPS to prevent users from accessing your site over an insecure connection.
• Secure password input fields : Password fields implement security best practices including proper autocomplete, show/hide toggle, and strength indicators.
• Serve all pages over HTTPS : Every page and resource on your site must be delivered over HTTPS to protect user data in transit and enable modern browser features.
• Set a Permissions-Policy header : The Permissions-Policy header lets servers restrict which browser features (camera, microphone, geolocation, etc.) can be used in a page or its embedded iframes.
• Set a Referrer-Policy header : The Referrer-Policy header controls how much referrer information is sent when navigating from your site to another, protecting user privacy and preventing leaking sensitive URL parameters.
• Set an HSTS header : The Strict-Transport-Security response header tells browsers to always use HTTPS for your domain, preventing protocol downgrade attacks and cookie hijacking.
• Set an X-Frame-Options header : The X-Frame-Options header controls whether your page can be embedded in an iframe, frame, or object — preventing clickjacking attacks.
• Set Secure, HttpOnly, and SameSite flags on session cookies : All session and authentication cookies are issued with the Secure, HttpOnly, and an appropriate SameSite flag to prevent interception, JavaScript exfiltration, and cross-site request forgery.
• Set X-Content-Type-Options: nosniff : The X-Content-Type-Options: nosniff header prevents browsers from MIME-sniffing a response away from the declared Content-Type, blocking a class of drive-by download and XSS attacks.
• Store authentication tokens securely : Sensitive authentication tokens are stored in httpOnly cookies rather than localStorage or sessionStorage to prevent theft via cross-site scripting attacks (OWASP A07).
• Submit forms over HTTPS : All HTML form actions must point to HTTPS URLs to ensure form data is encrypted in transit and cannot be intercepted by network attackers.
• Use COOP, COEP, and CORP for cross-origin isolation when needed : Sensitive or high-capability applications use COOP, COEP, and CORP deliberately, audit third-party embeds, and verify cross-origin isolation in the browser before relying on it.

Back to top

Images

25 rules. Formats, responsive delivery, optimization, and media quality rules.

Browse Images on frontendchecklist.io

• Compress images without quality loss : All images are compressed without significant quality loss to reduce file sizes.
• Fix broken images : No images return 404 errors or display broken-image icons to users.
• Handle image loading errors gracefully : Broken images are handled gracefully with fallback images or placeholder content.
• Implement responsive images with srcset : Images use srcset and sizes attributes for responsive delivery across devices.
• Keep image file sizes within recommended limits : Individual image files are compressed to reasonable sizes to avoid wasted bandwidth and slow load times, especially on mobile networks.
• Lazy load offscreen images : Images below the visible viewport use loading="lazy" to defer download until the user scrolls near them, reducing initial page load time.
• Manage inline SVG size and complexity : Large or complex SVGs inlined in HTML are extracted to external files or components, preventing them from bloating the HTML document and blocking parsing.
• Optimise images for faster loading : All images are compressed and metadata-stripped before deployment, removing unnecessary bytes without visible quality loss.
• Optimize all images for web : Images are optimized with appropriate formats, compression, and modern techniques.
• Optimize SVG files : SVG files are optimized with SVGO to remove unnecessary metadata and reduce size.
• Prioritize loading critical images : Hero and above-the-fold images are preloaded with high fetch priority for LCP.
• Provide meaningful alt text for images : Every informative image has a descriptive alt attribute; decorative images use alt="" to be ignored by screen readers.
• Serve images at the correct display size : Images are not significantly larger than their display dimensions—serving a 2000px image for a 400px container wastes bandwidth and hurts LCP.
• Serve images from a CDN : Images are served from a CDN with automatic optimization, resizing, and format conversion.
• Set explicit width and height on images : All elements have explicit width and height attributes so browsers can reserve space before the image loads, preventing layout shift.
• Support high-DPI retina displays : High-resolution images (2x, 3x) are provided for retina and high-DPI displays.
• Use and for image captions : Images with visible captions are wrapped in with a child, creating a semantic association between image and caption.
• Use with an fallback : Every element contains a required fallback as its last child, ensuring images display in all browsers including those that don't support .
• Use AVIF format for modern browsers : Images support AVIF format for superior compression with proper browser fallbacks.
• Use descriptive image filenames : Image filenames are descriptive and human-readable, using lowercase letters, hyphens as separators, and meaningful words that reflect the image content.
• Use image sprites where appropriate : Small images and icons use sprites or SVG to reduce HTTP requests.
• Use modern image formats (WebP, AVIF) : Images are served in modern formats (WebP or AVIF) instead of legacy JPEG/PNG where browser support allows, reducing file size without visible quality loss.
• Use progressive JPEG encoding : JPEG images use progressive format for better perceived loading performance.
• Use srcset for responsive images : Images wider than 100px use the srcset attribute to offer multiple resolution variants, letting the browser download the optimal size for the user's viewport and device pixel ratio.
• Use WebP format with fallbacks : Images are served in WebP format with fallbacks for older browsers.

Back to top

Testing

13 rules. Unit, integration, E2E, monitoring, and quality assurance rules.

Browse Testing on frontendchecklist.io

• Enforce performance budgets in CI : Define measurable performance thresholds (bundle size, Lighthouse scores, Core Web Vitals) and fail CI builds automatically when they're exceeded.
• Follow mocking best practices : Use mocks strategically to isolate units under test without over-mocking.
• Implement consumer-driven contract testing for API boundaries : Consumer-driven contract tests (Pact) define and verify the API contracts between the frontend consumer and backend provider, catching integration mismatches before they reach production.
• Implement end-to-end testing : Use E2E testing frameworks like Playwright or Cypress to test critical user journeys.
• Include accessibility testing : Automate accessibility testing with tools like axe-core, jest-axe, or Playwright's accessibility testing.
• Integrate real-time error monitoring in production : A real-time error monitoring service captures, groups, and alerts on unhandled exceptions and promise rejections in production so issues are discovered before users report them.
• Maintain test coverage thresholds : Set and enforce minimum code coverage thresholds to ensure adequate test coverage.
• Test across all major browsers : Website works correctly across major browsers (Chrome, Firefox, Safari, Edge).
• Test on real mobile devices and viewports : Verify your application on real mobile devices and browser DevTools device emulation to catch touch interaction issues, viewport bugs, and mobile-specific rendering problems.
• Use mutation testing to measure how well tests detect bugs : Run Stryker mutation testing on critical business logic to verify that your test suite will actually catch real bugs, not just achieve line coverage.
• Use visual regression testing : Capture screenshots of components and pages, then automatically compare them against approved baselines to detect unintended visual changes before they reach production.
• Write integration tests for key workflows : Test how multiple units of code work together — API routes with their database queries, form submissions with validation, and component trees with their state management.
• Write unit tests : Critical functionality has unit tests with good coverage for reliability.

Back to top

Privacy

5 rules. Consent, tracking, retention, and user data rights rules.

Browse Privacy on frontendchecklist.io

• Avoid third-party cookies : Third-party cookies set by external domains track users across sites without their knowledge. Modern browsers are phasing them out, and regulations like GDPR and CCPA require consent before setting them.
• Collect only the minimum personal data necessary : Limit data collection to only what is strictly required for the stated purpose, in line with GDPR Article 5(1)(c) data minimisation principles.
• Implement a user-facing data deletion mechanism : Provide users with a clear way to request deletion of their personal data, fulfilling GDPR Article 17 (right to erasure / right to be forgotten).
• Link to your privacy policy in the footer : Websites that collect any personal data must publish a privacy policy and link to it prominently — this is a legal requirement under GDPR, CCPA, and most other privacy regulations.
• Show a cookie consent notice : Websites that set non-essential cookies must obtain prior, informed user consent under GDPR, CCPA, and similar privacy regulations before cookies are placed.

Back to top

Internationalization

5 rules. Localization, RTL, language handling, and translation workflow rules.

Browse Internationalization on frontendchecklist.io

• Add hreflang tags for multilingual sites : Hreflang tags indicate language and regional variations for multilingual sites.
• Design UI components to accommodate text expansion from translation : Ensure that layouts use flexible sizing so that translated text — which can be 30–50% longer than English — does not overflow, clip, or break the UI.
• Handle plural forms with Intl.PluralRules or ICU MessageFormat : Select the correct grammatical plural category for every language using Intl.PluralRules or an ICU-aware i18n library instead of simple singular/plural branching.
• Use Intl APIs for currency, number, and date formatting : Format monetary values, numbers, and dates using the browser's built-in Intl.NumberFormat and Intl.DateTimeFormat APIs instead of manual string manipulation.
• Use locale-neutral images and provide cultural overrides when needed : Default to abstract, culture-neutral icons and illustrations, and supply locale-specific image variants only when visual content carries meaning that differs across regions.

Back to top

Monorepo overview

Common commands

• pnpm dev - Run local development tasks
• pnpm build - Build all apps and packages with Turborepo
• pnpm lint - Run Biome linting
• pnpm typecheck - Run TypeScript checks across the repo
• pnpm test - Run the test suite
• pnpm validate:rule-structure - Validate rule heading structure
• pnpm score:rules - Score the rule corpus against the quality gate
• pnpm generate:skills - Regenerate installable skills from the rules
• pnpm generate:readme - Regenerate the root README checklist and the generated catalog copy

Contributing

Most content work happens in packages/content/rules/en. A typical rule-editing flow is:

1. Edit or add the relevant rule MDX files.
2. Run pnpm score:rules.
3. Run pnpm validate:rule-structure.
4. Run pnpm validate:sources when source metadata changes.
5. Run pnpm generate:skills.
6. Run pnpm generate:readme if rule titles or descriptions changed.

See AGENTS.md, scripts/README.md, and docs/generated/rules-catalog.md for repo conventions, script docs, and the generated standalone catalog copy.

Contributors

Thanks goes to these wonderful people (emoji key):

Support

• GitHub repo: thedaviddias/Front-End-Checklist
• Issues: open an issue
• License: MIT