CINXE.COM

<!doctype html><html lang="en-US" prefix="og: https://ogp.me/ns#"><head><meta charSet="utf-8"/><meta name="viewport" content="width=device-width,initial-scale=1"/><link rel="icon" href="https://developer.mozilla.org/favicon-48x48.bc390275e955dacb2e65.png"/><link rel="apple-touch-icon" href="https://developer.mozilla.org/apple-touch-icon.528534bba673c38049c2.png"/><meta name="theme-color" content="#ffffff"/><link rel="manifest" href="https://developer.mozilla.org/manifest.f42880861b394dd4dc9b.json"/><link rel="search" type="application/opensearchdescription+xml" href="/opensearch.xml" title="MDN Web Docs"/><title>UI pseudo-classes - Learn web development | MDN</title><link rel="alternate" title="UI-Pseudoklassen" href="https://developer.mozilla.org/de/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" hrefLang="de"/><link rel="alternate" title="Pseudo-classes relatives à l'interface utilisateur" href="https://developer.mozilla.org/fr/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" hrefLang="fr"/><link rel="alternate" title="UI 擬似クラス" href="https://developer.mozilla.org/ja/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" hrefLang="ja"/><link rel="alternate" title="UI 伪类" href="https://developer.mozilla.org/zh-CN/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" hrefLang="zh"/><link rel="alternate" title="UI pseudo-classes" href="https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" hrefLang="en"/><link rel="preload" as="font" type="font/woff2" href="/static/media/Inter.var.c2fe3cb2b7c746f7966a.woff2" crossorigin=""/><link rel="alternate" type="application/rss+xml" title="MDN Blog RSS Feed" href="https://developer.mozilla.org/en-US/blog/rss.xml" hrefLang="en"/><meta name="description" content="In the previous articles, we covered the styling of various form controls in a general manner. This included some usage of pseudo-classes, for example, using :checked to target a checkbox only when it is selected. In this article, we explore the different UI pseudo-classes available for styling forms in different states."/><meta property="og:url" content="https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes"/><meta property="og:title" content="UI pseudo-classes - Learn web development | MDN"/><meta property="og:type" content="website"/><meta property="og:locale" content="en_US"/><meta property="og:description" content="In the previous articles, we covered the styling of various form controls in a general manner. This included some usage of pseudo-classes, for example, using :checked to target a checkbox only when it is selected. In this article, we explore the different UI pseudo-classes available for styling forms in different states."/><meta property="og:image" content="https://developer.mozilla.org/mdn-social-share.d893525a4fb5fb1f67a2.png"/><meta property="og:image:type" content="image/png"/><meta property="og:image:height" content="1080"/><meta property="og:image:width" content="1920"/><meta property="og:image:alt" content="The MDN Web Docs logo, featuring a blue accent color, displayed on a solid black background."/><meta property="og:site_name" content="MDN Web Docs"/><meta name="twitter:card" content="summary_large_image"/><meta name="twitter:creator" content="MozDevNet"/><link rel="canonical" href="https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes"/><style media="print">.article-actions-container,.document-toc-container,.language-menu,.main-menu-toggle,.on-github,.page-footer,.place,.sidebar,.top-banner,.top-navigation-main,ul.prev-next{display:none!important}.main-page-content,.main-page-content pre{padding:2px}.main-page-content pre{border-left-width:2px}</style><script src="/static/js/gtag.js" defer=""></script><script defer="" src="/static/js/main.a44547d8.js"></script><link href="/static/css/main.6ca4d473.css" rel="stylesheet"/></head><body><script>if(document.body.addEventListener("load",(t=>{t.target.classList.contains("interactive")&&t.target.setAttribute("data-readystate","complete")}),{capture:!0}),window&&document.documentElement){const t={light:"#ffffff",dark:"#1b1b1b"};try{const e=window.localStorage.getItem("theme");e&&(document.documentElement.className=e,document.documentElement.style.backgroundColor=t[e]);const o=window.localStorage.getItem("nop");o&&(document.documentElement.dataset.nop=o)}catch(t){console.warn("Unable to read theme from localStorage",t)}}</script><div id="root"><ul id="nav-access" class="a11y-nav"><li><a id="skip-main" href="#content">Skip to main content</a></li><li><a id="skip-search" href="#top-nav-search-input">Skip to search</a></li><li><a id="skip-select-language" href="#languages-switcher-button">Skip to select language</a></li></ul><div class="page-wrapper category-api document-page"><div class="top-banner loading"><section class="place top container"></section></div><div class="sticky-header-container"><header class="top-navigation "><div class="container "><div class="top-navigation-wrap"><a href="/en-US/" class="logo" aria-label="MDN homepage"><svg id="mdn-docs-logo" xmlns="http://www.w3.org/2000/svg" x="0" y="0" viewBox="0 0 694.9 104.4" style="enable-background:new 0 0 694.9 104.4" xml:space="preserve" role="img"><title>MDN Web Docs</title><path d="M40.3 0 11.7 92.1H0L28.5 0h11.8zm10.4 0v92.1H40.3V0h10.4zM91 0 62.5 92.1H50.8L79.3 0H91zm10.4 0v92.1H91V0h10.4z" class="logo-m"></path><path d="M627.9 95.6h67v8.8h-67v-8.8z" class="logo-_"></path><path d="M367 42h-4l-10.7 30.8h-5.5l-10.8-26h-.4l-10.5 26h-5.2L308.7 42h-3.8v-5.6H323V42h-6.5l6.8 20.4h.4l10.3-26h4.7l11.2 26h.5l5.7-20.3h-6.2v-5.6H367V42zm34.9 20c-.4 3.2-2 5.9-4.7 8.2-2.8 2.3-6.5 3.4-11.3 3.4-5.4 0-9.7-1.6-13.1-4.7-3.3-3.2-5-7.7-5-13.7 0-5.7 1.6-10.3 4.7-14s7.4-5.5 12.9-5.5c5.1 0 9.1 1.6 11.9 4.7s4.3 6.9 4.3 11.3c0 1.5-.2 3-.5 4.7h-25.6c.3 7.7 4 11.6 10.9 11.6 2.9 0 5.1-.7 6.5-2 1.5-1.4 2.5-3 3-4.9l6 .9zM394 51.3c.2-2.4-.4-4.7-1.8-6.9s-3.8-3.3-7-3.3c-3.1 0-5.3 1-6.9 3-1.5 2-2.5 4.4-2.8 7.2H394zm51 2.4c0 5-1.3 9.5-4 13.7s-6.9 6.2-12.7 6.2c-6 0-10.3-2.2-12.7-6.7-.1.4-.2 1.4-.4 2.9s-.3 2.5-.4 2.9h-7.3c.3-1.7.6-3.5.8-5.3.3-1.8.4-3.7.4-5.5V22.3h-6v-5.6H416v27c1.1-2.2 2.7-4.1 4.7-5.7 2-1.6 4.8-2.4 8.4-2.4 4.6 0 8.4 1.6 11.4 4.7 3 3.2 4.5 7.6 4.5 13.4zm-7.7.6c0-4.2-1-7.4-3-9.5-2-2.2-4.4-3.3-7.4-3.3-3.4 0-6 1.2-8 3.7-1.9 2.4-2.9 5-3 7.7V57c0 3 1 5.6 3 7.7s4.5 3.1 7.6 3.1c3.6 0 6.3-1.3 8.1-3.9 1.8-2.7 2.7-5.9 2.7-9.6zm69.2 18.5h-13.2v-7.2c-1.2 2.2-2.8 4.1-4.9 5.6-2.1 1.6-4.8 2.4-8.3 2.4-4.8 0-8.7-1.6-11.6-4.9-2.9-3.2-4.3-7.7-4.3-13.3 0-5 1.3-9.6 4-13.7 2.6-4.1 6.9-6.2 12.8-6.2 5.7 0 9.8 2.2 12.3 6.5V22.3h-8.6v-5.6h15.8v50.6h6v5.5zM493.2 56v-4.4c-.1-3-1.2-5.5-3.2-7.3s-4.4-2.8-7.2-2.8c-3.6 0-6.3 1.3-8.2 3.9-1.9 2.6-2.8 5.8-2.8 9.6 0 4.1 1 7.3 3 9.5s4.5 3.3 7.4 3.3c3.2 0 5.8-1.3 7.8-3.8 2.1-2.6 3.1-5.3 3.2-8zm53.1-1.4c0 5.6-1.8 10.2-5.3 13.7s-8.2 5.3-13.9 5.3-10.1-1.7-13.4-5.1c-3.3-3.4-5-7.9-5-13.5 0-5.3 1.6-9.9 4.7-13.7 3.2-3.8 7.9-5.7 14.2-5.7s11 1.9 14.1 5.7c3 3.7 4.6 8.1 4.6 13.3zm-7.7-.2c0-4-1-7.2-3-9.5s-4.8-3.5-8.2-3.5c-3.6 0-6.4 1.2-8.3 3.7s-2.9 5.6-2.9 9.5c0 3.7.9 6.8 2.8 9.4 1.9 2.6 4.6 3.9 8.3 3.9 3.6 0 6.4-1.3 8.4-3.8 1.9-2.6 2.9-5.8 2.9-9.7zm45 5.8c-.4 3.2-1.9 6.3-4.4 9.1-2.5 2.9-6.4 4.3-11.8 4.3-5.2 0-9.4-1.6-12.6-4.8-3.2-3.2-4.8-7.7-4.8-13.7 0-5.5 1.6-10.1 4.7-13.9 3.2-3.8 7.6-5.7 13.2-5.7 2.3 0 4.6.3 6.7.8 2.2.5 4.2 1.5 6.2 2.9l1.5 9.5-5.9.7-1.3-6.1c-2.1-1.2-4.5-1.8-7.2-1.8-3.5 0-6.1 1.2-7.7 3.7-1.7 2.5-2.5 5.7-2.5 9.6 0 4.1.9 7.3 2.7 9.5 1.8 2.3 4.4 3.4 7.8 3.4 5.2 0 8.2-2.9 9.2-8.8l6.2 1.3zm34.7 1.9c0 3.6-1.5 6.5-4.6 8.5s-7 3-11.7 3c-5.7 0-10.6-1.2-14.6-3.6l1.2-8.8 5.7.6-.2 4.7c1.1.5 2.3.9 3.6 1.1s2.6.3 3.9.3c2.4 0 4.5-.4 6.5-1.3 1.9-.9 2.9-2.2 2.9-4.1 0-1.8-.8-3.1-2.3-3.8s-3.5-1.3-5.8-1.7-4.6-.9-6.9-1.4c-2.3-.6-4.2-1.6-5.7-2.9-1.6-1.4-2.3-3.5-2.3-6.3 0-4.1 1.5-6.9 4.6-8.5s6.4-2.4 9.9-2.4c2.6 0 5 .3 7.2.9 2.2.6 4.3 1.4 6.1 2.4l.8 8.8-5.8.7-.8-5.7c-2.3-1-4.7-1.6-7.2-1.6-2.1 0-3.7.4-5.1 1.1-1.3.8-2 2-2 3.8 0 1.7.8 2.9 2.3 3.6 1.5.7 3.4 1.2 5.7 1.6 2.2.4 4.5.8 6.7 1.4 2.2.6 4.1 1.6 5.7 3 1.4 1.6 2.2 3.7 2.2 6.6zM197.6 73.2h-17.1v-5.5h3.8V51.9c0-3.7-.7-6.3-2.1-7.9-1.4-1.6-3.3-2.3-5.7-2.3-3.2 0-5.6 1.1-7.2 3.4s-2.4 4.6-2.5 6.9v15.6h6v5.5h-17.1v-5.5h3.8V51.9c0-3.8-.7-6.4-2.1-7.9-1.4-1.5-3.3-2.3-5.6-2.3-3.2 0-5.5 1.1-7.2 3.3-1.6 2.2-2.4 4.5-2.5 6.9v15.8h6.9v5.5h-20.2v-5.5h6V42.4h-6.1v-5.6h13.4v6.4c1.2-2.1 2.7-3.8 4.7-5.2 2-1.3 4.4-2 7.3-2s5.3.7 7.5 2.1c2.2 1.4 3.7 3.5 4.5 6.4 1.1-2.5 2.7-4.5 4.9-6.1s4.8-2.4 7.9-2.4c3.5 0 6.5 1.1 8.9 3.3s3.7 5.6 3.7 10.2v18.2h6.1v5.5zm42.5 0h-13.2V66c-1.2 2.2-2.8 4.1-4.9 5.6-2.1 1.6-4.8 2.4-8.3 2.4-4.8 0-8.7-1.6-11.6-4.9-2.9-3.2-4.3-7.7-4.3-13.3 0-5 1.3-9.6 4-13.7 2.6-4.1 6.9-6.2 12.8-6.2s9.8 2.2 12.3 6.5V22.7h-8.6v-5.6h15.8v50.6h6v5.5zm-13.3-16.8V52c-.1-3-1.2-5.5-3.2-7.3s-4.4-2.8-7.2-2.8c-3.6 0-6.3 1.3-8.2 3.9-1.9 2.6-2.8 5.8-2.8 9.6 0 4.1 1 7.3 3 9.5s4.5 3.3 7.4 3.3c3.2 0 5.8-1.3 7.8-3.8 2.1-2.6 3.1-5.3 3.2-8zm61.5 16.8H269v-5.5h6V51.9c0-3.7-.7-6.3-2.2-7.9-1.4-1.6-3.4-2.3-5.7-2.3-3.1 0-5.6 1-7.4 3s-2.8 4.4-2.9 7v15.9h6v5.5h-19.3v-5.5h6V42.4h-6.2v-5.6h13.6V43c2.6-4.6 6.8-6.9 12.7-6.9 3.6 0 6.7 1.1 9.2 3.3s3.7 5.6 3.7 10.2v18.2h6v5.4h-.2z" class="logo-text"></path></svg></a><button title="Open main menu" type="button" class="button action has-icon main-menu-toggle" aria-haspopup="menu" aria-label="Open main menu" aria-expanded="false"><span class="button-wrap"><span class="icon icon-menu "></span><span class="visually-hidden">Open main menu</span></span></button></div><div class="top-navigation-main"><nav class="main-nav" aria-label="Main menu"><ul class="main-menu nojs"><li class="top-level-entry-container "><button type="button" id="references-button" class="top-level-entry menu-toggle" aria-controls="references-menu" aria-expanded="false">References</button><a href="/en-US/docs/Web" class="top-level-entry">References</a><ul id="references-menu" class="submenu references hidden inline-submenu-lg" aria-labelledby="references-button"><li class="apis-link-container mobile-only "><a href="/en-US/docs/Web" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Overview / Web Technology</div><p class="submenu-item-description">Web technology reference for developers</p></div></a></li><li class="html-link-container "><a href="/en-US/docs/Web/HTML" class="submenu-item "><div class="submenu-icon html"></div><div class="submenu-content-container"><div class="submenu-item-heading">HTML</div><p class="submenu-item-description">Structure of content on the web</p></div></a></li><li class="css-link-container "><a href="/en-US/docs/Web/CSS" class="submenu-item "><div class="submenu-icon css"></div><div class="submenu-content-container"><div class="submenu-item-heading">CSS</div><p class="submenu-item-description">Code used to describe document style</p></div></a></li><li class="javascript-link-container "><a href="/en-US/docs/Web/JavaScript" class="submenu-item "><div class="submenu-icon javascript"></div><div class="submenu-content-container"><div class="submenu-item-heading">JavaScript</div><p class="submenu-item-description">General-purpose scripting language</p></div></a></li><li class="http-link-container "><a href="/en-US/docs/Web/HTTP" class="submenu-item "><div class="submenu-icon http"></div><div class="submenu-content-container"><div class="submenu-item-heading">HTTP</div><p class="submenu-item-description">Protocol for transmitting web resources</p></div></a></li><li class="apis-link-container "><a href="/en-US/docs/Web/API" class="submenu-item "><div class="submenu-icon apis"></div><div class="submenu-content-container"><div class="submenu-item-heading">Web APIs</div><p class="submenu-item-description">Interfaces for building web applications</p></div></a></li><li class="apis-link-container "><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Web Extensions</div><p class="submenu-item-description">Developing extensions for web browsers</p></div></a></li><li class=" "><a href="/en-US/docs/Web/Accessibility" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Accessibility</div><p class="submenu-item-description">Build web projects usable for all</p></div></a></li><li class="apis-link-container desktop-only "><a href="/en-US/docs/Web" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Web Technology</div><p class="submenu-item-description">Web technology reference for developers</p></div></a></li></ul></li><li class="top-level-entry-container active"><button type="button" id="learn-button" class="top-level-entry menu-toggle" aria-controls="learn-menu" aria-expanded="false">Learn</button><a href="/en-US/docs/Learn_web_development" class="top-level-entry">Learn</a><ul id="learn-menu" class="submenu learn hidden inline-submenu-lg" aria-labelledby="learn-button"><li class="apis-link-container mobile-only "><a href="/en-US/docs/Learn_web_development" class="submenu-item "><div class="submenu-icon learn"></div><div class="submenu-content-container"><div class="submenu-item-heading">Overview / MDN Learning Area</div><p class="submenu-item-description">Learn web development</p></div></a></li><li class="apis-link-container desktop-only "><a href="/en-US/docs/Learn_web_development" class="submenu-item "><div class="submenu-icon learn"></div><div class="submenu-content-container"><div class="submenu-item-heading">MDN Learning Area</div><p class="submenu-item-description">Learn web development</p></div></a></li><li class="html-link-container "><a href="/en-US/docs/Learn_web_development/Core/Structuring_content" class="submenu-item "><div class="submenu-icon html"></div><div class="submenu-content-container"><div class="submenu-item-heading">HTML</div><p class="submenu-item-description">Learn to structure web content with HTML</p></div></a></li><li class="css-link-container "><a href="/en-US/docs/Learn_web_development/Core/Styling_basics" class="submenu-item "><div class="submenu-icon css"></div><div class="submenu-content-container"><div class="submenu-item-heading">CSS</div><p class="submenu-item-description">Learn to style content using CSS</p></div></a></li><li class="javascript-link-container "><a href="/en-US/docs/Learn_web_development/Core/Scripting" class="submenu-item "><div class="submenu-icon javascript"></div><div class="submenu-content-container"><div class="submenu-item-heading">JavaScript</div><p class="submenu-item-description">Learn to run scripts in the browser</p></div></a></li><li class=" "><a href="/en-US/docs/Learn_web_development/Core/Accessibility" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Accessibility</div><p class="submenu-item-description">Learn to make the web accessible to all</p></div></a></li></ul></li><li class="top-level-entry-container "><button type="button" id="mdn-plus-button" class="top-level-entry menu-toggle" aria-controls="mdn-plus-menu" aria-expanded="false">Plus</button><a href="/en-US/plus" class="top-level-entry">Plus</a><ul id="mdn-plus-menu" class="submenu mdn-plus hidden inline-submenu-lg" aria-labelledby="mdn-plus-button"><li class=" "><a href="/en-US/plus" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Overview</div><p class="submenu-item-description">A customized MDN experience</p></div></a></li><li class=" "><a href="/en-US/plus/ai-help" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">AI Help</div><p class="submenu-item-description">Get real-time assistance and support</p></div></a></li><li class=" "><a href="/en-US/plus/updates" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Updates</div><p class="submenu-item-description">All browser compatibility updates at a glance</p></div></a></li><li class=" "><a href="/en-US/plus/docs/features/overview" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Documentation</div><p class="submenu-item-description">Learn how to use MDN Plus</p></div></a></li><li class=" "><a href="/en-US/plus/docs/faq" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">FAQ</div><p class="submenu-item-description">Frequently asked questions about MDN Plus</p></div></a></li></ul></li><li class="top-level-entry-container "><a class="top-level-entry menu-link" href="/en-US/curriculum/">Curriculum <sup class="new">New</sup></a></li><li class="top-level-entry-container "><a class="top-level-entry menu-link" href="/en-US/blog/">Blog</a></li><li class="top-level-entry-container "><button type="button" id="tools-button" class="top-level-entry menu-toggle" aria-controls="tools-menu" aria-expanded="false">Tools</button><ul id="tools-menu" class="submenu tools hidden inline-submenu-lg" aria-labelledby="tools-button"><li class=" "><a href="/en-US/play" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Playground</div><p class="submenu-item-description">Write, test and share your code</p></div></a></li><li class=" "><a href="/en-US/observatory" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">HTTP Observatory</div><p class="submenu-item-description">Scan a website for free</p></div></a></li><li class=" "><a href="/en-US/plus/ai-help" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">AI Help</div><p class="submenu-item-description">Get real-time assistance and support</p></div></a></li></ul></li></ul></nav><div class="header-search"><form action="/en-US/search" class="search-form search-widget" id="top-nav-search-form" role="search"><label id="top-nav-search-label" for="top-nav-search-input" class="visually-hidden">Search MDN</label><input aria-activedescendant="" aria-autocomplete="list" aria-controls="top-nav-search-menu" aria-expanded="false" aria-labelledby="top-nav-search-label" autoComplete="off" id="top-nav-search-input" role="combobox" type="search" class="search-input-field" name="q" placeholder=" " required="" value=""/><button type="button" class="button action has-icon clear-search-button"><span class="button-wrap"><span class="icon icon-cancel "></span><span class="visually-hidden">Clear search input</span></span></button><button type="submit" class="button action has-icon search-button"><span class="button-wrap"><span class="icon icon-search "></span><span class="visually-hidden">Search</span></span></button><div id="top-nav-search-menu" role="listbox" aria-labelledby="top-nav-search-label"></div></form></div><div class="theme-switcher-menu"><button type="button" class="button action has-icon theme-switcher-menu small" aria-haspopup="menu"><span class="button-wrap"><span class="icon icon-theme-os-default "></span>Theme</span></button></div><ul class="auth-container"><li><a href="/users/fxa/login/authenticate/?next=%2Fen-US%2Fdocs%2FLearn_web_development%2FExtensions%2FForms%2FUI_pseudo-classes" class="login-link" rel="nofollow">Log in</a></li><li><a href="/users/fxa/login/authenticate/?next=%2Fen-US%2Fdocs%2FLearn_web_development%2FExtensions%2FForms%2FUI_pseudo-classes" target="_self" rel="nofollow" class="button primary mdn-plus-subscribe-link"><span class="button-wrap">Sign up for free</span></a></li></ul></div></div></header><div class="article-actions-container"><div class="container"><button type="button" class="button action has-icon sidebar-button" aria-label="Expand sidebar" aria-expanded="false" aria-controls="sidebar-quicklinks"><span class="button-wrap"><span class="icon icon-sidebar "></span></span></button><nav class="breadcrumbs-container" aria-label="Breadcrumb"><ol typeof="BreadcrumbList" vocab="https://schema.org/" aria-label="breadcrumbs"><li property="itemListElement" typeof="ListItem"><a href="/en-US/docs/Learn_web_development" class="breadcrumb" property="item" typeof="WebPage"><span property="name">Learn</span></a><meta property="position" content="1"/></li><li property="itemListElement" typeof="ListItem"><a href="/en-US/docs/Learn_web_development/Extensions" class="breadcrumb" property="item" typeof="WebPage"><span property="name">Extension modules</span></a><meta property="position" content="2"/></li><li property="itemListElement" typeof="ListItem"><a href="/en-US/docs/Learn_web_development/Extensions/Forms" class="breadcrumb" property="item" typeof="WebPage"><span property="name">Web forms</span></a><meta property="position" content="3"/></li><li property="itemListElement" typeof="ListItem"><a href="/en-US/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" class="breadcrumb-current-page" property="item" typeof="WebPage"><span property="name">UI pseudo-classes</span></a><meta property="position" content="4"/></li></ol></nav><div class="article-actions"><button type="button" class="button action has-icon article-actions-toggle" aria-label="Article actions"><span class="button-wrap"><span class="icon icon-ellipses "></span><span class="article-actions-dialog-heading">Article Actions</span></span></button><ul class="article-actions-entries"><li class="article-actions-entry"><div class="languages-switcher-menu open-on-focus-within"><button id="languages-switcher-button" type="button" class="button action small has-icon languages-switcher-menu" aria-haspopup="menu"><span class="button-wrap"><span class="icon icon-language "></span>English (US)</span></button><div class="hidden"><ul class="submenu language-menu " aria-labelledby="language-menu-button"><li class=" "><form class="submenu-item locale-redirect-setting"><div class="group"><label class="switch"><input type="checkbox" name="locale-redirect"/><span class="slider"></span><span class="label">Remember language</span></label><a href="https://github.com/orgs/mdn/discussions/739" rel="external noopener noreferrer" target="_blank" title="Enable this setting to automatically switch to this language when it's available. (Click to learn more.)"><span class="icon icon-question-mark "></span></a></div></form></li><li class=" "><a data-locale="de" href="/de/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" class="button submenu-item"><span>Deutsch</span><span title="Diese Übersetzung ist Teil eines Experiments."><span class="icon icon-experimental "></span></span></a></li><li class=" "><a data-locale="fr" href="/fr/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" class="button submenu-item"><span>Français</span></a></li><li class=" "><a data-locale="ja" href="/ja/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" class="button submenu-item"><span>日本語</span></a></li><li class=" "><a data-locale="zh-CN" href="/zh-CN/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" class="button submenu-item"><span>中文 (简体)</span></a></li></ul></div></div></li></ul></div></div></div></div><div class="main-wrapper"><div class="sidebar-container"><aside id="sidebar-quicklinks" class="sidebar"><button type="button" class="button action backdrop" aria-label="Collapse sidebar"><span class="button-wrap"></span></button><nav aria-label="Related Topics" class="sidebar-inner"><header class="sidebar-actions"><section class="sidebar-filter-container"><div class="sidebar-filter "><label id="sidebar-filter-label" class="sidebar-filter-label" for="sidebar-filter-input"><span class="icon icon-filter"></span><span class="visually-hidden">Filter sidebar</span></label><input id="sidebar-filter-input" autoComplete="off" class="sidebar-filter-input-field false" type="text" placeholder="Filter" value=""/><button type="button" class="button action has-icon clear-sidebar-filter-button"><span class="button-wrap"><span class="icon icon-cancel "></span><span class="visually-hidden">Clear filter input</span></span></button></div></section></header><div class="sidebar-inner-nav"><div class="in-nav-toc"><div class="document-toc-container"><section class="document-toc"><header><h2 class="document-toc-heading">In this article</h2></header><ul class="document-toc-list"><li class="document-toc-item "><a class="document-toc-link" href="#what_pseudo-classes_do_we_have_available">What pseudo-classes do we have available?</a></li><li class="document-toc-item "><a class="document-toc-link" href="#styling_inputs_based_on_whether_they_are_required_or_not">Styling inputs based on whether they are required or not</a></li><li class="document-toc-item "><a class="document-toc-link" href="#using_generated_content_with_pseudo-classes">Using generated content with pseudo-classes</a></li><li class="document-toc-item "><a class="document-toc-link" href="#styling_controls_based_on_whether_their_data_is_valid">Styling controls based on whether their data is valid</a></li><li class="document-toc-item "><a class="document-toc-link" href="#styling_enabled_and_disabled_inputs_and_read-only_and_read-write">Styling enabled and disabled inputs, and read-only and read-write</a></li><li class="document-toc-item "><a class="document-toc-link" href="#radio_and_checkbox_states_—_checked_default_indeterminate">Radio and checkbox states — checked, default, indeterminate</a></li><li class="document-toc-item "><a class="document-toc-link" href="#more_pseudo-classes">More pseudo-classes</a></li><li class="document-toc-item "><a class="document-toc-link" href="#test_your_skills!">Test your skills!</a></li><li class="document-toc-item "><a class="document-toc-link" href="#summary">Summary</a></li></ul></section></div></div><div class="sidebar-body"><ol><li class="section"><a href="/en-US/docs/Learn_web_development/Getting_started">Getting started modules</a></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Getting_started/Environment_setup">Environment setup</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Getting_started/Environment_setup/Installing_software">Installing basic software</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Environment_setup/Browsing_the_web">Browsing the web</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Environment_setup/Code_editors">Code editors</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Environment_setup/Dealing_with_files">Dealing with files</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Environment_setup/Command_line">Command line crash course</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Getting_started/Your_first_website">Your first website</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Getting_started/Your_first_website/What_will_your_website_look_like">What will your website look like?</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Your_first_website/Creating_the_content">HTML: Creating the content</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Your_first_website/Styling_the_content">CSS: Styling the content</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Your_first_website/Adding_interactivity">JavaScript: Adding interactivity</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Your_first_website/Publishing_your_website">Publishing your website</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Getting_started/Web_standards">Web standards</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Getting_started/Web_standards/How_the_web_works">How the web works</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Web_standards/The_web_standards_model">The web standards model</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Web_standards/How_browsers_load_websites">How browsers load websites</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Getting_started/Soft_skills">Soft skills</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Getting_started/Soft_skills/Research_and_learning">Research and learning</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Soft_skills/Collaboration_and_teamwork">Collaboration and teamwork</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Soft_skills/Workflows_and_processes">Workflows and processes</a></li><li><a href="/en-US/docs/Learn_web_development/Getting_started/Soft_skills/Job_interviews">Succeeding in job interviews</a></li></ol></details></li><li class="section"><a href="/en-US/docs/Learn_web_development/Core">Core modules</a></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Core/Structuring_content">Structuring content with HTML</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Basic_HTML_syntax">Basic HTML syntax</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Webpage_metadata">What's in the head? Webpage metadata</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Headings_and_paragraphs">Headings and paragraphs in HTML</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Emphasis_and_importance">Emphasis and importance</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Lists">Lists</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Structuring_documents">Structuring documents</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Advanced_text_features">Advanced text features</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Creating_links">Creating links</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Marking_up_a_letter">Challenge: Marking up a letter</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Structuring_a_page_of_content">Challenge: Structuring a page of content</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_images">HTML images</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_video_and_audio">HTML video and audio</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Mozilla_splash_page">Challenge: Mozilla splash page</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_table_basics">HTML table basics</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Table_accessibility">HTML table accessibility</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Planet_data_table">Challenge: Structuring a planet data table</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_forms">Forms and buttons in HTML</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Structuring_content/Debugging_HTML">Debugging HTML</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Core/Styling_basics">CSS styling basics</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/What_is_CSS">What is CSS?</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Getting_started">Getting started with CSS</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Styling_a_bio_page">Challenge: Styling a biography page</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Basic_selectors">Basic CSS selectors</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Attribute_selectors">Attribute selectors</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Pseudo_classes_and_elements">Pseudo-classes and pseudo-elements</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Combinators">Combinators</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Box_model">The box model</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Handling_conflicts">Handling conflicts</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Values_and_units">CSS values and units</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Sizing">Sizing items in CSS</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Backgrounds_and_borders">Backgrounds and borders</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Overflow">Overflowing content</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Images_media_forms">Images, media, and form elements</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Tables">Styling tables</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Debugging_CSS">Debugging CSS</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Fundamental_CSS_comprehension">Challenge: Fundamental CSS comprehension</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Fancy_letterheaded_paper">Challenge: Creating fancy letterheaded paper</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Cool-looking_box">Challenge: A cool-looking box</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Core/Text_styling">CSS text styling</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Core/Text_styling/Fundamentals">Fundamental text and font styling</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Text_styling/Styling_lists">Styling lists</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Text_styling/Styling_links">Styling links</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Text_styling/Web_fonts">Web fonts</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Text_styling/Typesetting_a_homepage">Challenge: Typesetting a community school homepage</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Core/CSS_layout">CSS layout</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Core/CSS_layout/Introduction">Introduction to CSS layout</a></li><li><a href="/en-US/docs/Learn_web_development/Core/CSS_layout/Floats">Floats</a></li><li><a href="/en-US/docs/Learn_web_development/Core/CSS_layout/Positioning">Positioning</a></li><li><a href="/en-US/docs/Learn_web_development/Core/CSS_layout/Flexbox">Flexbox</a></li><li><a href="/en-US/docs/Learn_web_development/Core/CSS_layout/Grids">CSS grid layout</a></li><li><a href="/en-US/docs/Learn_web_development/Core/CSS_layout/Responsive_Design">Responsive design</a></li><li><a href="/en-US/docs/Learn_web_development/Core/CSS_layout/Media_queries">Media query fundamentals</a></li><li><a href="/en-US/docs/Learn_web_development/Core/CSS_layout/Fundamental_Layout_Comprehension">Challenge: Fundamental layout comprehension</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Core/Scripting">Dynamic scripting with JavaScript</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/What_is_JavaScript">What is JavaScript?</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/A_first_splash">A first splash into JavaScript</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/What_went_wrong">What went wrong? Troubleshooting JavaScript</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Variables">Storing the information you need — Variables</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Math">Basic math in JavaScript — numbers and operators</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Strings">Handling text — strings in JavaScript</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Useful_string_methods">Useful string methods</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Arrays">Arrays</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Silly_story_generator">Challenge: Silly story generator</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Conditionals">Making decisions in your code — conditionals</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Loops">Looping code</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Functions">Functions — reusable blocks of code</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Build_your_own_function">Build your own function</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Return_values">Function return values</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Events">Introduction to events</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Event_bubbling">Event bubbling</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Image_gallery">Challenge: Image gallery</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Object_basics">JavaScript object basics</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/DOM_scripting">DOM scripting introduction</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Network_requests">Making network requests with JavaScript</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/JSON">Working with JSON</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Scripting/Debugging_JavaScript">Debugging JavaScript and handling errors</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Core/Frameworks_libraries">JavaScript frameworks and libraries</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Core/Frameworks_libraries/Introduction">Introduction to client-side frameworks</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Frameworks_libraries/Main_features">Framework main features</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_getting_started">Getting started with React</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_todo_list_beginning">Beginning our React todo list</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_components">Componentizing our React app</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_interactivity_events_state">React interactivity: Events and state</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_interactivity_filtering_conditional_rendering">React interactivity: Editing, filtering, conditional rendering</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_accessibility">Accessibility in React</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_resources">React resources</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Core/Accessibility">Accessibility</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Core/Accessibility/What_is_accessibility">What is accessibility?</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Accessibility/Tooling">Accessibility tooling and assistive technology</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Accessibility/HTML">HTML: A good basis for accessibility</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Accessibility/CSS_and_JavaScript">CSS and JavaScript accessibility best practices</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Accessibility/WAI-ARIA_basics">WAI-ARIA basics</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Accessibility/Multimedia">Accessible multimedia</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Accessibility/Mobile">Mobile accessibility</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Accessibility/Accessibility_troubleshooting">Challenge: Accessibility troubleshooting</a></li></ol></details></li><li><a href="/en-US/docs/Learn_web_development/Core/Design_for_developers">Design for developers</a></li><li><a href="/en-US/docs/Learn_web_development/Core/Version_control">Version control</a></li><li class="section"><a href="/en-US/docs/Learn_web_development/Extensions">Extension modules</a></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects">Advanced JavaScript objects</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects/Object_prototypes">Object prototypes</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects/Object-oriented_programming">Object-oriented programming</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects/Classes_in_JavaScript">Classes in JavaScript</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects/Object_building_practice">Object building practice</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects/Adding_bouncing_balls_features">Challenge: Adding features to our bouncing balls demo</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_APIs">Client-side web APIs</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_APIs/Introduction">Introduction to web APIs</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_APIs/Video_and_audio_APIs">Video and Audio APIs</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_APIs/Drawing_graphics">Drawing graphics</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_APIs/Client-side_storage">Client-side storage</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_APIs/Third_party_APIs">Third-party APIs</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Extensions/Async_JS">Asynchronous JavaScript</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Extensions/Async_JS/Introducing">Introducing asynchronous JavaScript</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Async_JS/Promises">How to use promises</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Async_JS/Implementing_a_promise-based_API">How to implement a promise-based API</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Async_JS/Introducing_workers">Introducing workers</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Async_JS/Sequencing_animations">Challenge: Sequencing animations</a></li></ol></details></li><li class="toggle"><details open=""><summary><a href="/en-US/docs/Learn_web_development/Extensions/Forms">Web forms</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/Your_first_form">Your first form</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/How_to_structure_a_web_form">How to structure a web form</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/Basic_native_form_controls">Basic native form controls</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/HTML5_input_types">The HTML5 input types</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/Other_form_controls">Other form controls</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/Styling_web_forms">Styling web forms</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/Advanced_form_styling">Advanced form styling</a></li><li><em><a href="/en-US/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes" aria-current="page">UI pseudo-classes</a></em></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation">Client-side form validation</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/Sending_and_retrieving_form_data">Sending form data</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_tools">Understanding client-side tools</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_tools/Overview">Client-side tooling overview</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_tools/Package_management">Package management basics</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_tools/Introducing_complete_toolchain">Introducing a complete toolchain</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Client-side_tools/Deployment">Deploying our app</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Extensions/Server-side">Server-side websites</a></summary><ol><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/First_steps">Server-side first steps</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/First_steps/Introduction">Introduction to the server side</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/First_steps/Client-Server_overview">Client-Server Overview</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/First_steps/Web_frameworks">Server-side web frameworks</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/First_steps/Website_security">Website security</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django">Django web framework (Python)</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Introduction">Django introduction</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/development_environment">Setting up a Django development environment</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Tutorial_local_library_website">Django Tutorial: The Local Library website</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/skeleton_website">Django Tutorial Part 2: Creating a skeleton website</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Models">Django Tutorial Part 3: Using models</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Admin_site">Django Tutorial Part 4: Django admin site</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Home_page">Django Tutorial Part 5: Creating our home page</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Generic_views">Django Tutorial Part 6: Generic list and detail views</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Sessions">Django Tutorial Part 7: Sessions framework</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Authentication">Django Tutorial Part 8: User authentication and permissions</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Forms">Django Tutorial Part 9: Working with forms</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Testing">Django Tutorial Part 10: Testing a Django web application</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Deployment">Django Tutorial Part 11: Deploying Django to production</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/web_application_security">Django web application security</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Django/django_assessment_blog">Assessment: DIY Django mini blog</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs">Express web framework (Node.js)</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/Introduction">Express/Node introduction</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/development_environment">Setting up a Node development environment</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/Tutorial_local_library_website">Express Tutorial: The Local Library website</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/skeleton_website">Express Tutorial Part 2: Creating a skeleton website</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/mongoose">Express Tutorial Part 3: Using a Database (with Mongoose)</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/routes">Express Tutorial Part 4: Routes and controllers</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/Displaying_data">Express Tutorial Part 5: Displaying library data</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/forms">Express Tutorial Part 6: Working with forms</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/deployment">Express Tutorial Part 7: Deploying to production</a></li></ol></details></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Extensions/Performance">Web performance</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Extensions/Performance/why_web_performance">The "why" of web performance</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Performance/What_is_web_performance">What is web performance?</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Performance/Perceived_performance">Perceived performance</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Performance/Measuring_performance">Measuring performance</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Performance/Multimedia">Multimedia: Images</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Performance/video">Multimedia: video</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Performance/JavaScript">JavaScript performance optimization</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Performance/HTML">HTML performance optimization</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Performance/CSS">CSS performance optimization</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Performance/business_case_for_performance">The business case for web performance</a></li></ol></details></li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Extensions/Testing">Testing</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Extensions/Testing/Introduction">Introduction to cross-browser testing</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Testing/Testing_strategies">Strategies for carrying out testing</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Testing/HTML_and_CSS">Handling common HTML and CSS problems</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Testing/Feature_detection">Implementing feature detection</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Testing/Automated_testing">Introduction to automated testing</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Testing/Your_own_automation_environment">Setting up your own test automation environment</a></li></ol></details></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Transform_animate">Transform and animate CSS</a></li><li><a href="/en-US/docs/Learn_web_development/Extensions/Security_privacy">Security and privacy</a></li><li class="section">Further resources</li><li class="toggle"><details><summary><a href="/en-US/docs/Learn_web_development/Howto">How to solve common problems</a></summary><ol><li><a href="/en-US/docs/Learn_web_development/Howto/Solve_HTML_problems">Solve common HTML problems</a></li><li><a href="/en-US/docs/Learn_web_development/Howto/Solve_CSS_problems">Solve common CSS problems</a></li><li><a href="/en-US/docs/Learn_web_development/Howto/Solve_JavaScript_problems">Solve common JavaScript problems</a></li><li><a href="/en-US/docs/Learn_web_development/Howto/Web_mechanics">Web mechanics</a></li><li><a href="/en-US/docs/Learn_web_development/Howto/Tools_and_setup">Tools and setup</a></li><li><a href="/en-US/docs/Learn_web_development/Howto/Design_and_accessibility">Design and accessibility</a></li></ol></details></li><li><a href="/en-US/docs/Learn_web_development/About">About</a></li><li><a href="/en-US/docs/Learn_web_development/Educators">Resources for educators</a></li><li><a href="/en-US/docs/Learn_web_development/Changelog">Changelog</a></li></ol></div></div><section class="place side"></section></nav></aside><div class="toc-container"><aside class="toc"><nav><div class="document-toc-container"><section class="document-toc"><header><h2 class="document-toc-heading">In this article</h2></header><ul class="document-toc-list"><li class="document-toc-item "><a class="document-toc-link" href="#what_pseudo-classes_do_we_have_available">What pseudo-classes do we have available?</a></li><li class="document-toc-item "><a class="document-toc-link" href="#styling_inputs_based_on_whether_they_are_required_or_not">Styling inputs based on whether they are required or not</a></li><li class="document-toc-item "><a class="document-toc-link" href="#using_generated_content_with_pseudo-classes">Using generated content with pseudo-classes</a></li><li class="document-toc-item "><a class="document-toc-link" href="#styling_controls_based_on_whether_their_data_is_valid">Styling controls based on whether their data is valid</a></li><li class="document-toc-item "><a class="document-toc-link" href="#styling_enabled_and_disabled_inputs_and_read-only_and_read-write">Styling enabled and disabled inputs, and read-only and read-write</a></li><li class="document-toc-item "><a class="document-toc-link" href="#radio_and_checkbox_states_—_checked_default_indeterminate">Radio and checkbox states — checked, default, indeterminate</a></li><li class="document-toc-item "><a class="document-toc-link" href="#more_pseudo-classes">More pseudo-classes</a></li><li class="document-toc-item "><a class="document-toc-link" href="#test_your_skills!">Test your skills!</a></li><li class="document-toc-item "><a class="document-toc-link" href="#summary">Summary</a></li></ul></section></div></nav></aside><section class="place side"></section></div></div><main id="content" class="main-content "><article class="main-page-content" lang="en-US"><header><h1>UI pseudo-classes</h1></header><div class="section-content"><ul class="prev-next"><li><a class="button secondary" href="/en-US/docs/Learn_web_development/Extensions/Forms/Advanced_form_styling"><span class="button-wrap"> Previous </span></a></li><li><a class="button secondary" href="/en-US/docs/Learn_web_development/Extensions/Forms"><span class="button-wrap"> Overview: Web forms</span></a></li><li><a class="button secondary" href="/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation"><span class="button-wrap"> Next </span></a></li></ul> <p>In the previous articles, we covered the styling of various form controls in a general manner. This included some usage of pseudo-classes, for example, using <code>:checked</code> to target a checkbox only when it is selected. In this article, we explore the different UI pseudo-classes available for styling forms in different states.</p> <figure class="table-container"><table> <tbody> <tr> <th scope="row">Prerequisites:</th> <td> A basic understanding of <a href="/en-US/docs/Learn_web_development/Core/Structuring_content">HTML</a> and <a href="/en-US/docs/Learn_web_development/Core/Styling_basics">CSS</a>, including general knowledge of <a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Pseudo_classes_and_elements">pseudo-classes and pseudo-elements</a>. </td> </tr> <tr> <th scope="row">Objective:</th> <td> To understand what parts of forms are hard to style, and why; to learn what can be done to customize them. </td> </tr> </tbody> </table></figure></div><section aria-labelledby="what_pseudo-classes_do_we_have_available"><h2 id="what_pseudo-classes_do_we_have_available"><a href="#what_pseudo-classes_do_we_have_available">What pseudo-classes do we have available?</a></h2><div class="section-content"><p>The original pseudo-classes (from <a href="https://www.w3.org/TR/CSS21/selector.html#dynamic-pseudo-classes" class="external" target="_blank">CSS 2.1</a>) that are relevant to forms are:</p> <ul> <li><a href="/en-US/docs/Web/CSS/:hover"><code>:hover</code></a>: Selects an element only when it is being hovered over by a mouse pointer.</li> <li><a href="/en-US/docs/Web/CSS/:focus"><code>:focus</code></a>: Selects an element only when it is focused (i.e. by being tabbed to via the keyboard).</li> <li><a href="/en-US/docs/Web/CSS/:active"><code>:active</code></a>: selects an element only when it is being activated (i.e. while it is being clicked on, or when the <kbd>Return</kbd> / <kbd>Enter</kbd> key is being pressed down in the case of a keyboard activation).</li> </ul> <p>These basic pseudo-classes should be familiar to you now. <a href="/en-US/docs/Web/CSS/CSS_selectors">CSS selectors</a> provide several other pseudo-classes related to HTML forms. These provide several useful targeting conditions that you can take advantage of. We'll discuss these in more detail in the sections below, but briefly, the main ones we'll be looking at are:</p> <ul> <li><a href="/en-US/docs/Web/CSS/:required"><code>:required</code></a> and <a href="/en-US/docs/Web/CSS/:optional"><code>:optional</code></a>: Target elements that can be required (e.g. elements that support the <a href="/en-US/docs/Web/HTML/Attributes/required"><code>required</code></a> HTML attribute)), based on whether they are required or optional.</li> <li><a href="/en-US/docs/Web/CSS/:valid"><code>:valid</code></a> and <a href="/en-US/docs/Web/CSS/:invalid"><code>:invalid</code></a>, and <a href="/en-US/docs/Web/CSS/:in-range"><code>:in-range</code></a> and <a href="/en-US/docs/Web/CSS/:out-of-range"><code>:out-of-range</code></a>: Target form controls that are valid/invalid according to form validation constraints set on them, or in-range/out-of-range.</li> <li><a href="/en-US/docs/Web/CSS/:enabled"><code>:enabled</code></a> and <a href="/en-US/docs/Web/CSS/:disabled"><code>:disabled</code></a>, and <a href="/en-US/docs/Web/CSS/:read-only"><code>:read-only</code></a> and <a href="/en-US/docs/Web/CSS/:read-write"><code>:read-write</code></a>: Target elements that can be disabled (e.g. elements that support the <a href="/en-US/docs/Web/HTML/Attributes/disabled"><code>disabled</code></a> HTML attribute), based on whether they are currently enabled or disabled, and read-write or read-only form controls (e.g. elements with the <a href="/en-US/docs/Web/HTML/Attributes/readonly"><code>readonly</code></a> HTML attribute set).</li> <li><a href="/en-US/docs/Web/CSS/:checked"><code>:checked</code></a>, <a href="/en-US/docs/Web/CSS/:indeterminate"><code>:indeterminate</code></a>, and <a href="/en-US/docs/Web/CSS/:default"><code>:default</code></a>: Respectively target checkboxes and radio buttons that are checked, in an indeterminate state (neither checked or not checked), and the default selected option when the page loads (e.g. an <a href="/en-US/docs/Web/HTML/Element/input/checkbox"><code><input type="checkbox"></code></a> with the <a href="/en-US/docs/Web/HTML/Element/input#checked"><code>checked</code></a> attribute set, or an <a href="/en-US/docs/Web/HTML/Element/option"><code><option></code></a> element with the <a href="/en-US/docs/Web/HTML/Element/option#selected"><code>selected</code></a> attribute set).</li> </ul> <p>There are many others, but the ones listed above are the most obviously useful. Some of them are aimed at solving very specific niche problems. The UI pseudo-classes listed above have excellent browser support, but of course, you should test your form implementations carefully to ensure they work for your target audience.</p> <div class="notecard note"> <p><strong>Note:</strong> A number of the pseudo-classes discussed here are concerned with styling form controls based on their validation state (is their data valid, or not?) You'll learn much more about setting and controlling validation constraints in our next article — <a href="/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation">Client-side form validation</a> — but for now we'll keep things simple regarding the form validation, so it doesn't confuse things.</p> </div></div></section><section aria-labelledby="styling_inputs_based_on_whether_they_are_required_or_not"><h2 id="styling_inputs_based_on_whether_they_are_required_or_not"><a href="#styling_inputs_based_on_whether_they_are_required_or_not">Styling inputs based on whether they are required or not</a></h2><div class="section-content"><p>One of the most basic concepts regarding client-side form validation is whether a form input is required (it has to be filled in before the form can be submitted) or optional.</p> <p><a href="/en-US/docs/Web/HTML/Element/input"><code><input></code></a>, <a href="/en-US/docs/Web/HTML/Element/select"><code><select></code></a>, and <a href="/en-US/docs/Web/HTML/Element/textarea"><code><textarea></code></a> elements have a <code>required</code> attribute available which, when set, means that you have to fill in that control before the form will successfully submit. For example:</p> <div class="code-example"><div class="example-header"><span class="language-name">html</span></div><pre class="brush: html notranslate"><code><form> <fieldset> <legend>Feedback form</legend> <div> <label for="fname">First name: </label> <input id="fname" name="fname" type="text" required /> </div> <div> <label for="lname">Last name: </label> <input id="lname" name="lname" type="text" required /> </div> <div> <label for="email"> Email address (include if you want a response): </label> <input id="email" name="email" type="email" /> </div> <div><button>Submit</button></div> </fieldset> </form> </code></pre></div> <p>Here, the first name and last name are required, but the email address is optional.</p> <p>You can match these two states using the <a href="/en-US/docs/Web/CSS/:required"><code>:required</code></a> and <a href="/en-US/docs/Web/CSS/:optional"><code>:optional</code></a> pseudo-classes. For example, if we apply the following CSS to the above HTML:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>input:required { border: 1px solid black; } input:optional { border: 1px solid silver; } </code></pre></div> <p>The required controls would have a black border, and the optional control will have a silver border, like so:</p> <iframe width="100%" height="400" src="https://mdn.github.io/learning-area/html/forms/pseudo-classes/basic-required-optional.html" loading="lazy"></iframe> <p>You can also try submitting the form without filling it in, to see the client-side validation error messages browsers give you by default.</p> <p>The above form isn't bad, but it isn't great either. For a start, we are signaling required versus optional status using color alone, which isn't great for colorblind people. Second, the standard convention on the web for required status is an asterisk (<code>*</code>), or the word "required" being associated with the controls in question.</p> <p>In the next section, we'll look at a better example of indicating required fields using <code>:required</code>, which also digs into using generated content.</p> <div class="notecard note"> <p><strong>Note:</strong> You'll probably not find yourself using the <code>:optional</code> pseudo-class very often. Form controls are optional by default, so you could just do your optional styling by default, and add styles on top for required controls.</p> </div> <div class="notecard note"> <p><strong>Note:</strong> If one radio button in a same-named group of radio buttons has the <code>required</code> attribute set, all the radio buttons will be invalid until one is selected, but only the one with the attribute assigned will actually match <a href="/en-US/docs/Web/CSS/:required"><code>:required</code></a>.</p> </div></div></section><section aria-labelledby="using_generated_content_with_pseudo-classes"><h2 id="using_generated_content_with_pseudo-classes"><a href="#using_generated_content_with_pseudo-classes">Using generated content with pseudo-classes</a></h2><div class="section-content"><p>In previous articles, we've seen the usage of <a href="/en-US/docs/Web/CSS/CSS_generated_content">generated content</a>, but we thought now would be a good time to talk about it in a bit more detail.</p> <p>The idea is that we can use the <a href="/en-US/docs/Web/CSS/::before"><code>::before</code></a> and <a href="/en-US/docs/Web/CSS/::after"><code>::after</code></a> pseudo-elements along with the <a href="/en-US/docs/Web/CSS/content"><code>content</code></a> property to make a chunk of content appear before or after the affected element. The chunk of content is not added to the DOM, so it may be invisible to some screen readers. Because it is a pseudo-element, it can be targeted with styles in the same way that any actual DOM node can.</p> <p>This is really useful when you want to add a visual indicator to an element, such as a label or icon, when alternative indicators are also available to ensure accessibility for all users. For example, in our <a href="https://mdn.github.io/learning-area/html/forms/styling-examples/radios-styled.html" class="external" target="_blank">custom radio buttons example</a>, we use generated content to handle the placement and animation of the custom radio button's inner circle when a radio button is selected:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>input[type="radio"]::before { display: block; content: " "; width: 10px; height: 10px; border-radius: 6px; background-color: red; font-size: 1.2em; transform: translate(3px, 3px) scale(0); transform-origin: center; transition: all 0.3s ease-in; } input[type="radio"]:checked::before { transform: translate(3px, 3px) scale(1); transition: all 0.3s cubic-bezier(0.25, 0.25, 0.56, 2); } </code></pre></div> <p>This is really useful — screen readers already let their users know when a radio button or checkbox they encounter is checked/selected, so you don't want them to read out another DOM element that indicates selection — that could be confusing. Having a purely visual indicator solves this problem.</p> <p>Not all <code><input></code> types support having generated content put on them. All input types that show dynamic text in them, such as <code>text</code>, <code>password</code>, or <code>button</code>, don't display generated content. Others, including <code>range</code>, <code>color</code>, <code>checkbox</code>, etc., display generated content.</p> <p>Back to our required/optional example from before, this time we'll not alter the appearance of the input itself — we'll use generated content to add an indicating label (<a href="https://mdn.github.io/learning-area/html/forms/pseudo-classes/required-optional-generated.html" class="external" target="_blank">see it live here</a>, and see the <a href="https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/required-optional-generated.html" class="external" target="_blank">source code here</a>).</p> <p>First of all, we'll add a paragraph to the top of the form to say what you are looking for:</p> <div class="code-example"><div class="example-header"><span class="language-name">html</span></div><pre class="brush: html notranslate"><code><p>Required fields are labeled with "required".</p> </code></pre></div> <p>Screen reader users will get "required" read out as an extra bit of information when they get to each required input, while sighted users will get our label.</p> <p>As previously mentioned, text inputs don't support generated content, so we add an empty <a href="/en-US/docs/Web/HTML/Element/span"><code><span></code></a> to hang the generated content on:</p> <div class="code-example"><div class="example-header"><span class="language-name">html</span></div><pre class="brush: html notranslate"><code><div> <label for="fname">First name: </label> <input id="fname" name="fname" type="text" required /> <span></span> </div> </code></pre></div> <p>The immediate problem with this was that the span was dropping onto a new line below the input because the input and label are both set with <code>width: 100%</code>. To fix this we style the parent <code><div></code> to become a flex container, but also tell it to wrap its contents onto new lines if the content becomes too long:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>fieldset > div { margin-bottom: 20px; display: flex; flex-flow: row wrap; } </code></pre></div> <p>The effect this has is that the label and input sit on separate lines because they are both <code>width: 100%</code>, but the <code><span></code> has a width of <code>0</code> so it can sit on the same line as the input.</p> <p>Now onto the generated content. We create it using this CSS:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>input + span { position: relative; } input:required + span::after { font-size: 0.7rem; position: absolute; content: "required"; color: white; background-color: black; padding: 5px 10px; top: -26px; left: -70px; } </code></pre></div> <p>We set the <code><span></code> to <code>position: relative</code> so that we can set the generated content to <code>position: absolute</code> and position it relative to the <code><span></code> rather than the <code><body></code> (The generated content acts as though it is a child node of the element it is generated on, for the purposes of positioning).</p> <p>Then we give the generated content the content "required", which is what we wanted our label to say, and style and position it as we want. The result is seen below.</p> <iframe width="100%" height="430" src="https://mdn.github.io/learning-area/html/forms/pseudo-classes/required-optional-generated.html" loading="lazy"></iframe></div></section><section aria-labelledby="styling_controls_based_on_whether_their_data_is_valid"><h2 id="styling_controls_based_on_whether_their_data_is_valid"><a href="#styling_controls_based_on_whether_their_data_is_valid">Styling controls based on whether their data is valid</a></h2><div class="section-content"><p>The other really important, fundamental concept in form validation is whether a form control's data is valid or not (in the case of numerical data, we can also talk about in-range and out-of-range data). Form controls with <a href="/en-US/docs/Web/HTML/Constraint_validation">constraint limitations</a> can be targeted based on these states.</p></div></section><section aria-labelledby="valid_and_invalid"><h3 id="valid_and_invalid"><a href="#valid_and_invalid">:valid and :invalid</a></h3><div class="section-content"><p>You can target form controls using the <a href="/en-US/docs/Web/CSS/:valid"><code>:valid</code></a> and <a href="/en-US/docs/Web/CSS/:invalid"><code>:invalid</code></a> pseudo-classes. Some points worth bearing in mind:</p> <ul> <li>Controls with no constraint validation will always be valid, and therefore matched with <code>:valid</code>.</li> <li>Controls with <code>required</code> set on them that have no value are counted as invalid — they will be matched with <code>:invalid</code> and <code>:required</code>.</li> <li>Controls with built-in validation, such as <code><input type="email"></code> or <code><input type="url"></code> are (matched with) <code>:invalid</code> when the data entered into them does not match the pattern they are looking for (but they are valid when empty).</li> <li>Controls whose current value is outside the range limits specified by the <a href="/en-US/docs/Web/HTML/Element/input#min"><code>min</code></a> and <a href="/en-US/docs/Web/HTML/Element/input#max"><code>max</code></a> attributes are (matched with) <code>:invalid</code>, but also matched by <a href="/en-US/docs/Web/CSS/:out-of-range"><code>:out-of-range</code></a>, as you'll see later on.</li> <li>There are some other ways to make an element matched by <code>:valid</code>/<code>:invalid</code>, as you'll see in the <a href="/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation">Client-side form validation</a> article. But we'll keep things simple for now.</li> </ul> <p>Let's go in and look at an example of <code>:valid</code>/<code>:invalid</code> (see <a href="https://mdn.github.io/learning-area/html/forms/pseudo-classes/valid-invalid.html" class="external" target="_blank">valid-invalid.html</a> for the live version, and also check out the <a href="https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/valid-invalid.html" class="external" target="_blank">source code</a>).</p> <p>As in the previous example, we've got extra <code><span></code>s to generate content on, which we'll use to provide indicators of valid/invalid data:</p> <div class="code-example"><div class="example-header"><span class="language-name">html</span></div><pre class="brush: html notranslate"><code><div> <label for="fname">First name: </label> <input id="fname" name="fname" type="text" required /> <span></span> </div> </code></pre></div> <p>To provide these indicators, we use the following CSS:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>input + span { position: relative; } input + span::before { position: absolute; right: -20px; top: 5px; } input:invalid { border: 2px solid red; } input:invalid + span::before { content: "✖"; color: red; } input:valid + span::before { content: "✓"; color: green; } </code></pre></div> <p>As before, we set the <code><span></code>s to <code>position: relative</code> so that we can position the generated content relative to them. We then absolutely position different generated content depending on whether the form's data is valid or invalid — a green check or a red cross, respectively. To add a bit of extra urgency to the invalid data, we've also given the inputs a thick red border when invalid.</p> <div class="notecard note"> <p><strong>Note:</strong> We've used <code>::before</code> to add these labels, as we were already using <code>::after</code> for the "required" labels.</p> </div> <p>You can try it below:</p> <iframe width="100%" height="430" src="https://mdn.github.io/learning-area/html/forms/pseudo-classes/valid-invalid.html" loading="lazy"></iframe> <p>Notice how the required text inputs are invalid when empty, but valid when they have something filled in. The email input on the other hand is valid when empty, as it is not required, but invalid when it contains something that is not a proper email address.</p></div></section><section aria-labelledby="in-range_and_out-of-range_data"><h3 id="in-range_and_out-of-range_data"><a href="#in-range_and_out-of-range_data">In-range and out-of-range data</a></h3><div class="section-content"><p>As we hinted at above, there are two other related pseudo-classes to consider — <a href="/en-US/docs/Web/CSS/:in-range"><code>:in-range</code></a> and <a href="/en-US/docs/Web/CSS/:out-of-range"><code>:out-of-range</code></a>. These match numeric inputs where range limits are specified by the <a href="/en-US/docs/Web/HTML/Element/input#min"><code>min</code></a> and <a href="/en-US/docs/Web/HTML/Element/input#max"><code>max</code></a>, when their data is inside or outside the specified range, respectively.</p> <div class="notecard note"> <p><strong>Note:</strong> Numeric input types are <code>date</code>, <code>month</code>, <code>week</code>, <code>time</code>, <code>datetime-local</code>, <code>number</code>, and <code>range</code>.</p> </div> <p>It is worth noting that inputs whose data is in-range will also be matched by the <code>:valid</code> pseudo-class and inputs whose data is out-of-range will also be matched by the <code>:invalid</code> pseudo-class. So why have both? The issue is really one of semantics — out-of-range is a more specific type of invalid communication, so you might want to provide a different message for out-of-range inputs, which will be more helpful to users than just saying "invalid". You might even want to provide both.</p> <p>Let's look at an example that does exactly this. Our <a href="https://mdn.github.io/learning-area/html/forms/pseudo-classes/out-of-range.html" class="external" target="_blank">out-of-range.html</a> demo (see also the <a href="https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/out-of-range.html" class="external" target="_blank">source code</a>) builds on top of the previous example to provide out-of-range messages for the numeric inputs, as well as saying whether they are required.</p> <p>The numeric input looks like this:</p> <div class="code-example"><div class="example-header"><span class="language-name">html</span></div><pre class="brush: html notranslate"><code><div> <label for="age">Age (must be 12+): </label> <input id="age" name="age" type="number" min="12" max="120" required /> <span></span> </div> </code></pre></div> <p>And the CSS looks like this:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>input + span { position: relative; } input + span::after { font-size: 0.7rem; position: absolute; padding: 5px 10px; top: -26px; } input:required + span::after { color: white; background-color: black; content: "Required"; left: -70px; } input:out-of-range + span::after { color: white; background-color: red; width: 155px; content: "Outside allowable value range"; left: -182px; } </code></pre></div> <p>This is a similar story to what we had before in the <code>:required</code> example, except that here we've split out the declarations that apply to any <code>::after</code> content into a separate rule, and given the separate <code>::after</code> content for <code>:required</code> and <code>:out-of-range</code> states their own content and styling. You can try it here:</p> <iframe width="100%" height="430" src="https://mdn.github.io/learning-area/html/forms/pseudo-classes/out-of-range.html" loading="lazy"></iframe> <p>It is possible for the number input to be both required and out-of-range at the same time, so what happens then? Because the <code>:out-of-range</code> rule appears later in the source code than the <code>:required</code> rule, the <a href="/en-US/docs/Learn_web_development/Core/Styling_basics/Handling_conflicts#understanding_the_cascade">cascade rules</a> come into play, and the out of range message is shown.</p> <p>This works quite nicely — when the page first loads, "Required" is shown, along with a red cross and border. When you've typed in a valid age (i.e. in the range of 12-120), the input turns valid. If however, you then change the age entry to one that is out of range, the "Outside allowable value range" message then pops up in place of "Required".</p> <div class="notecard note"> <p><strong>Note:</strong> To enter an invalid/out-of-range value, you'll have to actually focus the form and type it in using the keyboard. The spinner buttons won't let you increment/decrement the value outside the allowable range.</p> </div></div></section><section aria-labelledby="styling_enabled_and_disabled_inputs_and_read-only_and_read-write"><h2 id="styling_enabled_and_disabled_inputs_and_read-only_and_read-write"><a href="#styling_enabled_and_disabled_inputs_and_read-only_and_read-write">Styling enabled and disabled inputs, and read-only and read-write</a></h2><div class="section-content"><p>An enabled element is an element that can be activated; it can be selected, clicked on, typed into, etc. A disabled element on the other hand cannot be interacted with in any way, and its data isn't even sent to the server.</p> <p>These two states can be targeted using <a href="/en-US/docs/Web/CSS/:enabled"><code>:enabled</code></a> and <a href="/en-US/docs/Web/CSS/:disabled"><code>:disabled</code></a>. Why are disabled inputs useful? Well, sometimes if some data does not apply to a certain user, you might not even want to submit that data when they submit the form. A classic example is a shipping form — commonly you'll get asked if you want to use the same address for billing and shipping; if so, you can just send a single address to the server, and might as well just disable the billing address fields.</p> <p>Let's have a look at an example that does just this. First of all, the HTML is a simple form containing text inputs, plus a checkbox to toggle disabling the billing address on and off. The billing address fields are disabled by default.</p> <div class="code-example"><div class="example-header"><span class="language-name">html</span></div><pre class="brush: html notranslate"><code><form> <fieldset id="shipping"> <legend>Shipping address</legend> <div> <label for="name1">Name: </label> <input id="name1" name="name1" type="text" required /> </div> <div> <label for="address1">Address: </label> <input id="address1" name="address1" type="text" required /> </div> <div> <label for="zip-code1">Zip/postal code: </label> <input id="zip-code1" name="zip-code1" type="text" required /> </div> </fieldset> <fieldset id="billing"> <legend>Billing address</legend> <div> <label for="billing-checkbox">Same as shipping address:</label> <input type="checkbox" id="billing-checkbox" checked /> </div> <div> <label for="name" class="billing-label disabled-label">Name: </label> <input id="name" name="name" type="text" disabled required /> </div> <div> <label for="address2" class="billing-label disabled-label"> Address: </label> <input id="address2" name="address2" type="text" disabled required /> </div> <div> <label for="zip-code2" class="billing-label disabled-label"> Zip/postal code: </label> <input id="zip-code2" name="zip-code2" type="text" disabled required /> </div> </fieldset> <div><button>Submit</button></div> </form> </code></pre></div> <p>Now onto the CSS. The most relevant parts of this example are as follows:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>input[type="text"]:disabled { background: #eee; border: 1px solid #ccc; } label:has(+ :disabled) { color: #aaa; } </code></pre></div> <p>We've directly selected the inputs we want to disable using <code>input[type="text"]:disabled</code>, but we also wanted to gray out the corresponding text labels. As the labels are right before their inputs, we selected those using the pseudo-class <a href="/en-US/docs/Web/CSS/:has"><code>:has</code></a>.</p> <p>Now finally, we've used some JavaScript to toggle the disabling of the billing address fields:</p> <div class="code-example"><div class="example-header"><span class="language-name">js</span></div><pre class="brush: js notranslate"><code>// Wait for the page to finish loading document.addEventListener( "DOMContentLoaded", () => { // Attach `change` event listener to checkbox document .getElementById("billing-checkbox") .addEventListener("change", toggleBilling); }, false, ); function toggleBilling() { // Select the billing text fields const billingItems = document.querySelectorAll('#billing input[type="text"]'); // Toggle the billing text fields for (let i = 0; i < billingItems.length; i++) { billingItems[i].disabled = !billingItems[i].disabled; } } </code></pre></div> <p>It uses the <a href="/en-US/docs/Web/API/HTMLElement/change_event"><code>change</code> event</a> to let the user enable/disable the billing fields, and toggle the styling of the associated labels.</p> <p>You can see the example in action below (also <a href="https://mdn.github.io/learning-area/html/forms/pseudo-classes/enabled-disabled-shipping.html" class="external" target="_blank">see it live here</a>, and see the <a href="https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/enabled-disabled-shipping.html" class="external" target="_blank">source code</a>):</p> <iframe width="100%" height="600" src="https://mdn.github.io/learning-area/html/forms/pseudo-classes/enabled-disabled-shipping.html" loading="lazy"></iframe></div></section><section aria-labelledby="read-only_and_read-write"><h3 id="read-only_and_read-write"><a href="#read-only_and_read-write">Read-only and read-write</a></h3><div class="section-content"><p>In a similar manner to <code>:disabled</code> and <code>:enabled</code>, the <code>:read-only</code> and <code>:read-write</code> pseudo-classes target two states that form inputs toggle between. As with disabled inputs, the user can't edit read-only inputs. However, unlike disabled inputs, read-only input values will be submitted to the server. Read-write means they can be edited — their default state.</p> <p>An input is set to read-only using the <code>readonly</code> attribute. As an example, imagine a confirmation page where the developer has sent the details filled in on previous pages over to this page, with the aim of getting the user to check them all in one place, add any final data that is needed, and then confirm the order by submitting. At this point, all the final form data can be sent to the server in one go.</p> <p>Let's look at what a form might look like (see <a href="https://mdn.github.io/learning-area/html/forms/pseudo-classes/readonly-confirmation.html" class="external" target="_blank">readonly-confirmation.html</a> for the live example; also <a href="https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/readonly-confirmation.html" class="external" target="_blank">see the source code</a>).</p> <p>A fragment of the HTML is as follows — note the readonly attribute:</p> <div class="code-example"><div class="example-header"><span class="language-name">html</span></div><pre class="brush: html notranslate"><code><div> <label for="name">Name: </label> <input id="name" name="name" type="text" value="Mr Soft" readonly /> </div> </code></pre></div> <p>If you try the live example, you'll see that the top set of form elements are not editable, however, the values are submitted when the form is submitted. We've styled the form controls using the <code>:read-only</code> and <code>:read-write</code> pseudo-classes, like so:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>input:read-only, textarea:read-only { border: 0; box-shadow: none; background-color: white; } textarea:read-write { box-shadow: inset 1px 1px 3px #ccc; border-radius: 5px; } </code></pre></div> <p>The full example looks like this:</p> <iframe width="100%" height="660" src="https://mdn.github.io/learning-area/html/forms/pseudo-classes/readonly-confirmation.html" loading="lazy"></iframe> <div class="notecard note"> <p><strong>Note:</strong> <code>:enabled</code> and <code>:read-write</code> are two more pseudo-classes that you'll probably rarely use, given that they describe the default states of input elements.</p> </div></div></section><section aria-labelledby="radio_and_checkbox_states_—_checked_default_indeterminate"><h2 id="radio_and_checkbox_states_—_checked_default_indeterminate"><a href="#radio_and_checkbox_states_—_checked_default_indeterminate">Radio and checkbox states — checked, default, indeterminate</a></h2><div class="section-content"><p>As we've seen in earlier articles in the module, <a href="/en-US/docs/Web/HTML/Element/input/radio">radio buttons</a> and <a href="/en-US/docs/Web/HTML/Element/input/checkbox">checkboxes</a> can be checked or unchecked. But there are a couple of other states to consider too:</p> <ul> <li><a href="/en-US/docs/Web/CSS/:default"><code>:default</code></a>: Matches radios/checkboxes that are checked by default, on page load (i.e. by setting the <code>checked</code> attribute on them). These match the <a href="/en-US/docs/Web/CSS/:default"><code>:default</code></a> pseudo-class, even if the user unchecks them.</li> <li><a href="/en-US/docs/Web/CSS/:indeterminate"><code>:indeterminate</code></a>: When radios/checkboxes are neither checked nor unchecked, they are considered <em>indeterminate</em> and will match the <a href="/en-US/docs/Web/CSS/:indeterminate"><code>:indeterminate</code></a> pseudo-class. More on what this means below.</li> </ul></div></section><section aria-labelledby="checked"><h3 id="checked"><a href="#checked">:checked</a></h3><div class="section-content"><p>When checked, they will be matched by the <a href="/en-US/docs/Web/CSS/:checked"><code>:checked</code></a> pseudo-class.</p> <p>The most common use of this is to add a different style onto the checkbox or radio button when it is checked, in cases where you've removed the system default styling with <a href="/en-US/docs/Web/CSS/appearance"><code>appearance: none;</code></a> and want to build the styles back up yourself. We saw examples of this in the previous article when we talked about <a href="/en-US/docs/Learn_web_development/Extensions/Forms/Advanced_form_styling#using_appearance_none_on_radioscheckboxes">Using <code>appearance: none</code> on radios/checkboxes</a>.</p> <p>As a recap, the <code>:checked</code> code from our <a href="https://mdn.github.io/learning-area/html/forms/styling-examples/radios-styled.html" class="external" target="_blank">Styled radio buttons</a> example looks like so:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>input[type="radio"]::before { display: block; content: " "; width: 10px; height: 10px; border-radius: 6px; background-color: red; font-size: 1.2em; transform: translate(3px, 3px) scale(0); transform-origin: center; transition: all 0.3s ease-in; } input[type="radio"]:checked::before { transform: translate(3px, 3px) scale(1); transition: all 0.3s cubic-bezier(0.25, 0.25, 0.56, 2); } </code></pre></div> <p>You can try it out here:</p> <iframe width="100%" height="200" src="https://mdn.github.io/learning-area/html/forms/styling-examples/radios-styled.html" loading="lazy"></iframe> <p>Basically, we build the styling for a radio button's "inner circle" using the <code>::before</code> pseudo-element, but set a <code>scale(0)</code> <a href="/en-US/docs/Web/CSS/transform"><code>transform</code></a> on it. We then use a <a href="/en-US/docs/Web/CSS/transition"><code>transition</code></a> to make the generated content on the label nicely animate into view when the radio is selected/checked. The advantage of using a transform rather than transitioning <a href="/en-US/docs/Web/CSS/width"><code>width</code></a>/<a href="/en-US/docs/Web/CSS/height"><code>height</code></a> is that you can use <a href="/en-US/docs/Web/CSS/transform-origin"><code>transform-origin</code></a> to make it grow from the center of the circle, rather than having it appear to grow from the circle's corner, and there is no jumping behavior as no box model property values are updated.</p></div></section><section aria-labelledby="default_and_indeterminate"><h3 id="default_and_indeterminate"><a href="#default_and_indeterminate">:default and :indeterminate</a></h3><div class="section-content"><p>As mentioned above, the <a href="/en-US/docs/Web/CSS/:default"><code>:default</code></a> pseudo-class matches radios/checkboxes that are checked by default, on page load, even when unchecked. This could be useful for adding an indicator to a list of options to remind the user what the defaults (or starting options) were, in case they want to reset their choices.</p> <p>Also, the radios/checkboxes mentioned above will be matched by the <a href="/en-US/docs/Web/CSS/:indeterminate"><code>:indeterminate</code></a> pseudo-class when they are in a state where they are neither checked nor unchecked. But what does this mean? Elements that are indeterminate include:</p> <ul> <li><a href="/en-US/docs/Web/HTML/Element/input/radio"><code><input/radio></code></a> inputs, when all radio buttons in a same-named group are unchecked</li> <li><a href="/en-US/docs/Web/HTML/Element/input/checkbox"><code><input/checkbox></code></a> inputs whose <code>indeterminate</code> property is set to <code>true</code> via JavaScript</li> <li><a href="/en-US/docs/Web/HTML/Element/progress"><code><progress></code></a> elements that have no value.</li> </ul> <p>This isn't something you'll likely use very often. One use case could be an indicator to tell users that they really need to select a radio button before they move on.</p> <p>Let's look at a couple of modified versions of the previous example that remind the user what the default option was, and style the labels of radio buttons when indeterminate. Both of these have the following HTML structure for the inputs:</p> <div class="code-example"><div class="example-header"><span class="language-name">html</span></div><pre class="brush: html notranslate"><code><p> <input type="radio" name="fruit" value="cherry" id="cherry" /> <label for="cherry">Cherry</label> <span></span> </p> </code></pre></div> <p>For the <code>:default</code> example, we've added the <code>checked</code> attribute to the middle radio button input, so it will be selected by default when loaded. We then style this with the following CSS:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>input ~ span { position: relative; } input:default ~ span::after { font-size: 0.7rem; position: absolute; content: "Default"; color: white; background-color: black; padding: 5px 10px; right: -65px; top: -3px; } </code></pre></div> <p>This provides a little "Default" label on the item that was originally selected when the page loaded. Note here we are using the subsequent-sibling combinator (<code>~</code>) rather than the Next-sibling combinator (<code>+</code>) — we need to do this because the <code><span></code> does not come right after the <code><input></code> in the source order.</p> <p>See the live result below:</p> <iframe width="100%" height="200" src="https://mdn.github.io/learning-area/html/forms/pseudo-classes/radios-checked-default.html" loading="lazy"></iframe> <div class="notecard note"> <p><strong>Note:</strong> You can also find the example live on GitHub at <a href="https://mdn.github.io/learning-area/html/forms/pseudo-classes/radios-checked-default.html" class="external" target="_blank">radios-checked-default.html</a> (also see the <a href="https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/radios-checked-default.html" class="external" target="_blank">source code</a>.)</p> </div> <p>For the <code>:indeterminate</code> example, we've got no default selected radio button — this is important — if there was, then there would be no indeterminate state to style. We style the indeterminate radio buttons with the following CSS:</p> <div class="code-example"><div class="example-header"><span class="language-name">css</span></div><pre class="brush: css notranslate"><code>input[type="radio"]:indeterminate { outline: 2px solid red; animation: 0.4s linear infinite alternate outline-pulse; } @keyframes outline-pulse { from { outline: 2px solid red; } to { outline: 6px solid red; } } </code></pre></div> <p>This creates a fun little animated outline on the radio buttons, which hopefully indicates that you need to select one of them!</p> <p>See the live result below:</p> <iframe width="100%" height="200" src="https://mdn.github.io/learning-area/html/forms/pseudo-classes/radios-checked-indeterminate.html" loading="lazy"></iframe> <div class="notecard note"> <p><strong>Note:</strong> You can also find the example live on GitHub at <a href="https://mdn.github.io/learning-area/html/forms/pseudo-classes/radios-checked-indeterminate.html" class="external" target="_blank">radios-checked-indeterminate.html</a> (also see the <a href="https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/radios-checked-indeterminate.html" class="external" target="_blank">source code</a>.)</p> </div> <div class="notecard note"> <p><strong>Note:</strong> You can find an <a href="/en-US/docs/Web/HTML/Element/input/checkbox#indeterminate_state_checkboxes">interesting example involving <code>indeterminate</code> states</a> on the <a href="/en-US/docs/Web/HTML/Element/input/checkbox"><code><input type="checkbox"></code></a> reference page.</p> </div></div></section><section aria-labelledby="more_pseudo-classes"><h2 id="more_pseudo-classes"><a href="#more_pseudo-classes">More pseudo-classes</a></h2><div class="section-content"><p>There are a number of other pseudo-classes of interest, and we don't have space to write about them all in detail here. Let's talk about a few more that you should take the time to investigate.</p> <ul> <li>The <a href="/en-US/docs/Web/CSS/:focus-within"><code>:focus-within</code></a> pseudo-class matches an element that has received focus or <em>contains</em> an element that has received focus. This is useful if you want a whole form to highlight in some way when an input inside it is focused.</li> <li>The <a href="/en-US/docs/Web/CSS/:focus-visible"><code>:focus-visible</code></a> pseudo-class matches focused elements that received focus via keyboard interaction (rather than touch or mouse) — useful if you want to show a different style for keyboard focus compared to mouse (or other) focus.</li> <li>The <a href="/en-US/docs/Web/CSS/:placeholder-shown"><code>:placeholder-shown</code></a> pseudo-class matches <a href="/en-US/docs/Web/HTML/Element/input"><code><input></code></a> and <a href="/en-US/docs/Web/HTML/Element/textarea"><code><textarea></code></a> elements that have their placeholder showing (i.e. the contents of the <a href="/en-US/docs/Web/HTML/Element/input#placeholder"><code>placeholder</code></a> attribute) because the value of the element is empty.</li> </ul> <p>The following are also interesting, but as yet not well-supported in browsers:</p> <ul> <li>The <a href="/en-US/docs/Web/CSS/:blank"><code>:blank</code></a> pseudo-class selects empty form controls. <a href="/en-US/docs/Web/CSS/:empty"><code>:empty</code></a> also matches elements that have no children, like <a href="/en-US/docs/Web/HTML/Element/input"><code><input></code></a>, but it is more general — it also matches other <a href="/en-US/docs/Glossary/Void_element">void elements</a> like <a href="/en-US/docs/Web/HTML/Element/br"><code><br></code></a> and <a href="/en-US/docs/Web/HTML/Element/hr"><code><hr></code></a>. <code>:empty</code> has reasonable browser support; the <code>:blank</code> pseudo-class's specification is not yet finished, so it is not yet supported in any browser.</li> <li>The <a href="/en-US/docs/Web/CSS/:user-invalid"><code>:user-invalid</code></a> pseudo-class, when supported, will be similar to <a href="/en-US/docs/Web/CSS/:invalid"><code>:invalid</code></a>, but with better user experience. If the value is valid when the input receives focus, the element may match <code>:invalid</code> as the user enters data if the value is temporarily invalid, but will only match <code>:user-invalid</code> when the element loses focus. If the value was originally invalid, it will match both <code>:invalid</code> and <code>:user-invalid</code> for the whole duration of the focus. In a similar manner to <code>:invalid</code>, it will stop matching <code>:user-invalid</code> if the value does become valid.</li> </ul></div></section><section aria-labelledby="test_your_skills!"><h2 id="test_your_skills!"><a href="#test_your_skills!">Test your skills!</a></h2><div class="section-content"><p>You've reached the end of this article, but can you remember the most important information? You can find some further tests to verify that you've retained this information before you move on — see <a href="/en-US/docs/Learn_web_development/Extensions/Forms/Test_your_skills:_Advanced_styling">Test your skills: Advanced styling</a>.</p></div></section><section aria-labelledby="summary"><h2 id="summary"><a href="#summary">Summary</a></h2><div class="section-content"><p>This completes our look at UI pseudo-classes that relate to form inputs. Keep playing with them, and create some fun form styles! Next up, we'll move on to something different — <a href="/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation">client-side form validation</a>.</p> <ul class="prev-next"><li><a class="button secondary" href="/en-US/docs/Learn_web_development/Extensions/Forms/Advanced_form_styling"><span class="button-wrap"> Previous </span></a></li><li><a class="button secondary" href="/en-US/docs/Learn_web_development/Extensions/Forms"><span class="button-wrap"> Overview: Web forms</span></a></li><li><a class="button secondary" href="/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation"><span class="button-wrap"> Next </span></a></li></ul></div></section><section aria-labelledby="advanced_topics"><h3 id="advanced_topics"><a href="#advanced_topics">Advanced Topics</a></h3><div class="section-content"><ul> <li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/How_to_build_custom_form_controls">How to build custom form controls</a></li> <li><a href="/en-US/docs/Learn_web_development/Extensions/Forms/Sending_forms_through_JavaScript">Sending forms through JavaScript</a></li> </ul></div></section></article><aside class="article-footer"><div class="article-footer-inner"><div class="svg-container"><svg xmlns="http://www.w3.org/2000/svg" width="162" height="162" viewBox="0 0 162 162" fill="none" role="none"><mask id="b" fill="#fff"><path d="M97.203 47.04c8.113-7.886 18.004-13.871 28.906-17.492a78 78 0 0 1 33.969-3.39c11.443 1.39 22.401 5.295 32.024 11.411s17.656 14.28 23.476 23.86c5.819 9.579 9.269 20.318 10.083 31.385a69.85 69.85 0 0 1-5.387 32.44c-4.358 10.272-11.115 19.443-19.747 26.801-8.632 7.359-18.908 12.709-30.034 15.637l-6.17-21.698c7.666-2.017 14.746-5.703 20.694-10.773 5.948-5.071 10.603-11.389 13.606-18.467a48.14 48.14 0 0 0 3.712-22.352c-.561-7.625-2.938-15.025-6.948-21.625s-9.544-12.226-16.175-16.44-14.181-6.904-22.065-7.863a53.75 53.75 0 0 0-23.405 2.336c-7.513 2.495-14.327 6.62-19.918 12.053z"></path></mask><path stroke="url(#a)" stroke-dasharray="6, 6" stroke-width="2" d="M97.203 47.04c8.113-7.886 18.004-13.871 28.906-17.492a78 78 0 0 1 33.969-3.39c11.443 1.39 22.401 5.295 32.024 11.411s17.656 14.28 23.476 23.86c5.819 9.579 9.269 20.318 10.083 31.385a69.85 69.85 0 0 1-5.387 32.44c-4.358 10.272-11.115 19.443-19.747 26.801-8.632 7.359-18.908 12.709-30.034 15.637l-6.17-21.698c7.666-2.017 14.746-5.703 20.694-10.773 5.948-5.071 10.603-11.389 13.606-18.467a48.14 48.14 0 0 0 3.712-22.352c-.561-7.625-2.938-15.025-6.948-21.625s-9.544-12.226-16.175-16.44-14.181-6.904-22.065-7.863a53.75 53.75 0 0 0-23.405 2.336c-7.513 2.495-14.327 6.62-19.918 12.053z" mask="url(#b)" style="stroke:url(#a)" transform="translate(-63.992 -25.587)"></path><ellipse cx="8.066" cy="111.597" fill="var(--background-tertiary)" rx="53.677" ry="53.699" transform="matrix(.71707 -.697 .7243 .6895 0 0)"></ellipse><g clip-path="url(#c)" transform="translate(-63.992 -25.587)"><path fill="#9abff5" d="m144.256 137.379 32.906 12.434a4.41 4.41 0 0 1 2.559 5.667l-9.326 24.679a4.41 4.41 0 0 1-5.667 2.559l-8.226-3.108-2.332 6.17c-.466 1.233-.375 1.883-1.609 1.417l-2.253-.527c-.411-.155-.95-.594-1.206-1.161l-4.734-10.484-12.545-4.741a4.41 4.41 0 0 1-2.559-5.667l9.325-24.679a4.41 4.41 0 0 1 5.667-2.559m9.961 29.617 8.227 3.108 3.264-8.638-.498-6.768-4.113-1.555.548 7.258-4.319-1.632zm-12.339-4.663 8.226 3.108 3.264-8.637-.498-6.769-4.113-1.554.548 7.257-4.319-1.632z"></path></g><g clip-path="url(#d)" transform="translate(-63.992 -25.587)"><path fill="#81b0f3" d="M135.35 60.136 86.67 41.654c-3.346-1.27-7.124.428-8.394 3.775L64.414 81.938c-1.27 3.347.428 7.125 3.774 8.395l12.17 4.62-3.465 9.128c-.693 1.826-1.432 2.457.394 3.15l3.014 1.625c.609.231 1.637.274 2.477-.104l15.53-6.983 18.56 7.047c3.346 1.27 7.124-.428 8.395-3.775l13.862-36.51c1.27-3.346-.428-7.124-3.775-8.395M95.261 83.207l-12.17-4.62 4.852-12.779 7.19-7.017 6.085 2.31-7.725 7.51 6.389 2.426zm18.255 6.93-12.17-4.62 4.852-12.778 7.189-7.017 6.085 2.31-7.725 7.51 6.39 2.426z"></path></g><defs><clipPath id="c"><path fill="#fff" d="m198.638 146.586-65.056-24.583-24.583 65.057 65.056 24.582z"></path></clipPath><clipPath id="d"><path fill="#fff" d="m66.438 14.055 96.242 36.54-36.54 96.243-96.243-36.54z"></path></clipPath><linearGradient id="a" x1="97.203" x2="199.995" y1="47.04" y2="152.793" gradientUnits="userSpaceOnUse"><stop stop-color="#086DFC"></stop><stop offset="0.246" stop-color="#2C81FA"></stop><stop offset="0.516" stop-color="#5497F8"></stop><stop offset="0.821" stop-color="#80B0F6"></stop><stop offset="1" stop-color="#9ABFF5"></stop></linearGradient></defs></svg></div><h2>Help improve MDN</h2><fieldset class="feedback"><label>Was this page helpful to you?</label><div class="button-container"><button type="button" class="button primary has-icon yes"><span class="button-wrap"><span class="icon icon-thumbs-up "></span>Yes</span></button><button type="button" class="button primary has-icon no"><span class="button-wrap"><span class="icon icon-thumbs-down "></span>No</span></button></div></fieldset><a class="contribute" href="https://github.com/mdn/content/blob/main/CONTRIBUTING.md" title="This will take you to our contribution guidelines on GitHub." target="_blank" rel="noopener noreferrer">Learn how to contribute</a>.<p class="last-modified-date">This page was last modified on <time dateTime="2024-12-29T05:22:55.000Z">Dec 29, 2024</time> by <a href="/en-US/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes/contributors.txt" rel="nofollow">MDN contributors</a>.</p><div id="on-github" class="on-github"><a href="https://github.com/mdn/content/blob/main/files/en-us/learn_web_development/extensions/forms/ui_pseudo-classes/index.md?plain=1" title="Folder: en-us/learn_web_development/extensions/forms/ui_pseudo-classes (Opens in a new tab)" target="_blank" rel="noopener noreferrer">View this page on GitHub</a> • <a href="https://github.com/mdn/content/issues/new?template=page-report.yml&mdn-url=https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FLearn_web_development%2FExtensions%2FForms%2FUI_pseudo-classes&metadata=%3C%21--+Do+not+make+changes+below+this+line+--%3E%0A%3Cdetails%3E%0A%3Csummary%3EPage+report+details%3C%2Fsummary%3E%0A%0A*+Folder%3A+%60en-us%2Flearn_web_development%2Fextensions%2Fforms%2Fui_pseudo-classes%60%0A*+MDN+URL%3A+https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FLearn_web_development%2FExtensions%2FForms%2FUI_pseudo-classes%0A*+GitHub+URL%3A+https%3A%2F%2Fgithub.com%2Fmdn%2Fcontent%2Fblob%2Fmain%2Ffiles%2Fen-us%2Flearn_web_development%2Fextensions%2Fforms%2Fui_pseudo-classes%2Findex.md%0A*+Last+commit%3A+https%3A%2F%2Fgithub.com%2Fmdn%2Fcontent%2Fcommit%2Ff6844f5e30882a6a4843da9b026bc0166ade9c41%0A*+Document+last+modified%3A+2024-12-29T05%3A22%3A55.000Z%0A%0A%3C%2Fdetails%3E" title="This will take you to GitHub to file a new issue." target="_blank" rel="noopener noreferrer">Report a problem with this content</a></div></div></aside></main></div></div><footer id="nav-footer" class="page-footer"><div class="page-footer-grid"><div class="page-footer-logo-col"><a href="/" class="mdn-footer-logo" aria-label="MDN homepage"><svg width="48" height="17" viewBox="0 0 48 17" fill="none" xmlns="http://www.w3.org/2000/svg"><title id="mdn-footer-logo-svg">MDN logo</title><path d="M20.04 16.512H15.504V10.416C15.504 9.488 15.344 8.824 15.024 8.424C14.72 8.024 14.264 7.824 13.656 7.824C12.92 7.824 12.384 8.064 12.048 8.544C11.728 9.024 11.568 9.64 11.568 10.392V14.184H13.008V16.512H8.472V10.416C8.472 9.488 8.312 8.824 7.992 8.424C7.688 8.024 7.232 7.824 6.624 7.824C5.872 7.824 5.336 8.064 5.016 8.544C4.696 9.024 4.536 9.64 4.536 10.392V14.184H6.6V16.512H0V14.184H1.44V8.04H0.024V5.688H4.536V7.32C5.224 6.088 6.32 5.472 7.824 5.472C8.608 5.472 9.328 5.664 9.984 6.048C10.64 6.432 11.096 7.016 11.352 7.8C11.992 6.248 13.168 5.472 14.88 5.472C15.856 5.472 16.72 5.776 17.472 6.384C18.224 6.992 18.6 7.936 18.6 9.216V14.184H20.04V16.512Z" fill="currentColor"></path><path d="M33.6714 16.512H29.1354V14.496C28.8314 15.12 28.3834 15.656 27.7914 16.104C27.1994 16.536 26.4154 16.752 25.4394 16.752C24.0154 16.752 22.8954 16.264 22.0794 15.288C21.2634 14.312 20.8554 12.984 20.8554 11.304C20.8554 9.688 21.2554 8.312 22.0554 7.176C22.8554 6.04 24.0634 5.472 25.6794 5.472C26.5594 5.472 27.2794 5.648 27.8394 6C28.3994 6.352 28.8314 6.8 29.1354 7.344V2.352H26.9754V0H32.2314V14.184H33.6714V16.512ZM29.1354 11.04V10.776C29.1354 9.88 28.8954 9.184 28.4154 8.688C27.9514 8.176 27.3674 7.92 26.6634 7.92C25.9754 7.92 25.3674 8.176 24.8394 8.688C24.3274 9.2 24.0714 10.008 24.0714 11.112C24.0714 12.152 24.3114 12.944 24.7914 13.488C25.2714 14.032 25.8394 14.304 26.4954 14.304C27.3114 14.304 27.9514 13.96 28.4154 13.272C28.8954 12.584 29.1354 11.84 29.1354 11.04Z" fill="currentColor"></path><path d="M47.9589 16.512H41.9829V14.184H43.4229V10.416C43.4229 9.488 43.2629 8.824 42.9429 8.424C42.6389 8.024 42.1829 7.824 41.5749 7.824C40.8389 7.824 40.2709 8.056 39.8709 8.52C39.4709 8.968 39.2629 9.56 39.2469 10.296V14.184H40.6869V16.512H34.7109V14.184H36.1509V8.04H34.5909V5.688H39.2469V7.344C39.9669 6.096 41.1269 5.472 42.7269 5.472C43.7509 5.472 44.6389 5.776 45.3909 6.384C46.1429 6.992 46.5189 7.936 46.5189 9.216V14.184H47.9589V16.512Z" fill="currentColor"></path></svg></a><p>Your blueprint for a better internet.</p><ul class="social-icons"><li><a href="https://mastodon.social/@mdn" target="_blank" rel="me noopener noreferrer"><span class="icon icon-mastodon"></span><span class="visually-hidden">MDN on Mastodon</span></a></li><li><a href="https://twitter.com/mozdevnet" target="_blank" rel="noopener noreferrer"><span class="icon icon-twitter-x"></span><span class="visually-hidden">MDN on X (formerly Twitter)</span></a></li><li><a href="https://github.com/mdn/" target="_blank" rel="noopener noreferrer"><span class="icon icon-github-mark-small"></span><span class="visually-hidden">MDN on GitHub</span></a></li><li><a href="/en-US/blog/rss.xml" target="_blank"><span class="icon icon-feed"></span><span class="visually-hidden">MDN Blog RSS Feed</span></a></li></ul></div><div class="page-footer-nav-col-1"><h2 class="footer-nav-heading">MDN</h2><ul class="footer-nav-list"><li class="footer-nav-item"><a href="/en-US/about">About</a></li><li class="footer-nav-item"><a href="/en-US/blog/">Blog</a></li><li class="footer-nav-item"><a href="https://www.mozilla.org/en-US/careers/listings/?team=ProdOps" target="_blank" rel="noopener noreferrer">Careers</a></li><li class="footer-nav-item"><a href="/en-US/advertising">Advertise with us</a></li></ul></div><div class="page-footer-nav-col-2"><h2 class="footer-nav-heading">Support</h2><ul class="footer-nav-list"><li class="footer-nav-item"><a class="footer-nav-link" href="https://support.mozilla.org/products/mdn-plus">Product help</a></li><li class="footer-nav-item"><a class="footer-nav-link" href="/en-US/docs/MDN/Community/Issues">Report an issue</a></li></ul></div><div class="page-footer-nav-col-3"><h2 class="footer-nav-heading">Our communities</h2><ul class="footer-nav-list"><li class="footer-nav-item"><a class="footer-nav-link" href="/en-US/community">MDN Community</a></li><li class="footer-nav-item"><a class="footer-nav-link" href="https://discourse.mozilla.org/c/mdn/236" target="_blank" rel="noopener noreferrer">MDN Forum</a></li><li class="footer-nav-item"><a class="footer-nav-link" href="/discord" target="_blank" rel="noopener noreferrer">MDN Chat</a></li></ul></div><div class="page-footer-nav-col-4"><h2 class="footer-nav-heading">Developers</h2><ul class="footer-nav-list"><li class="footer-nav-item"><a class="footer-nav-link" href="/en-US/docs/Web">Web Technologies</a></li><li class="footer-nav-item"><a class="footer-nav-link" href="/en-US/docs/Learn">Learn Web Development</a></li><li class="footer-nav-item"><a class="footer-nav-link" href="/en-US/plus">MDN Plus</a></li><li class="footer-nav-item"><a href="https://hacks.mozilla.org/" target="_blank" rel="noopener noreferrer">Hacks Blog</a></li></ul></div><div class="page-footer-moz"><a href="https://www.mozilla.org/" class="footer-moz-logo-link" target="_blank" rel="noopener noreferrer"><svg xmlns="http://www.w3.org/2000/svg" width="137" height="32" fill="none" viewBox="0 0 267.431 62.607"><path fill="currentColor" d="m13.913 23.056 5.33 25.356h2.195l5.33-25.356h14.267v38.976h-7.578V29.694h-2.194l-7.264 32.337h-7.343L9.418 29.694H7.223v32.337H-.354V23.056Zm47.137 9.123c9.12 0 14.423 5.385 14.423 15.214s-5.33 15.214-14.423 15.214c-9.12 0-14.423-5.385-14.423-15.214 0-9.855 5.304-15.214 14.423-15.214m0 24.363c4.285 0 6.428-2.196 6.428-7.032v-4.287c0-4.836-2.143-7.032-6.428-7.032s-6.428 2.196-6.428 7.032v4.287c0 4.836 2.143 7.032 6.428 7.032m18.473-.157 15.47-18.01h-15.26v-5.647h24.352v5.646L88.616 56.385h15.704v5.646H79.523Zm29.318-23.657h11.183V62.03h-7.578V38.375h-3.632v-5.646zm3.605-9.672h7.578v5.646h-7.578zm13.17 0h11.21v38.976h-7.578v-33.33h-3.632zm16.801 0H153.6v38.976h-7.577v-33.33h-3.632v-5.646zm29.03 9.123c4.442 0 7.394 2.143 8.231 5.881h2.194v-5.332h9.276v5.646h-3.632v18.011h3.632v5.646h-4.442c-3.135 0-4.834-1.699-4.834-4.836V56.7h-2.194c-.81 3.738-3.789 5.881-8.23 5.881-6.978 0-11.916-5.829-11.916-15.214 0-9.384 4.938-15.187 11.915-15.187m2.3 24.363c4.284 0 6.192-2.196 6.192-7.032v-4.287c0-4.836-1.908-7.032-6.193-7.032-4.18 0-6.193 2.196-6.193 7.032v4.287c0 4.836 2.012 7.032 6.193 7.032m48.34 5.489h-7.577V0h7.577zm6.585-29.643h32.165v-2.196l-21.295-7.634v-6.143l21.295-7.633V6.588h-25.345V0h32.165v12.522l-17.35 5.881V20.6l17.35 5.882v12.521h-38.985zm0-25.801h6.794v6.796h-6.794z"></path></svg></a><ul class="footer-moz-list"><li class="footer-moz-item"><a href="https://www.mozilla.org/privacy/websites/" class="footer-moz-link" target="_blank" rel="noopener noreferrer">Website Privacy Notice</a></li><li class="footer-moz-item"><a href="https://www.mozilla.org/privacy/websites/#cookies" class="footer-moz-link" target="_blank" rel="noopener noreferrer">Cookies</a></li><li class="footer-moz-item"><a href="https://www.mozilla.org/about/legal/terms/mozilla" class="footer-moz-link" target="_blank" rel="noopener noreferrer">Legal</a></li><li class="footer-moz-item"><a href="https://www.mozilla.org/about/governance/policies/participation/" class="footer-moz-link" target="_blank" rel="noopener noreferrer">Community Participation Guidelines</a></li></ul></div><div class="page-footer-legal"><p id="license" class="page-footer-legal-text">Visit <a href="https://www.mozilla.org" target="_blank" rel="noopener noreferrer">Mozilla Corporation’s</a> not-for-profit parent, the <a target="_blank" rel="noopener noreferrer" href="https://foundation.mozilla.org/">Mozilla Foundation</a>.<br/>Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under <a href="/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license">a Creative Commons license</a>.</p></div></div></footer></div><script type="application/json" id="hydration">{"url":"/en-US/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes","doc":{"body":[{"type":"prose","value":{"id":null,"title":null,"isH3":false,"content":"<ul class=\"prev-next\"><li><a class=\"button secondary\" href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Advanced_form_styling\"><span class=\"button-wrap\"> Previous </span></a></li><li><a class=\"button secondary\" href=\"/en-US/docs/Learn_web_development/Extensions/Forms\"><span class=\"button-wrap\"> Overview: Web forms</span></a></li><li><a class=\"button secondary\" href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation\"><span class=\"button-wrap\"> Next </span></a></li></ul>\n<p>In the previous articles, we covered the styling of various form controls in a general manner. This included some usage of pseudo-classes, for example, using <code>:checked</code> to target a checkbox only when it is selected. In this article, we explore the different UI pseudo-classes available for styling forms in different states.</p>\n<figure class=\"table-container\"><table>\n <tbody>\n <tr>\n <th scope=\"row\">Prerequisites:</th>\n <td>\n A basic understanding of\n <a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content\">HTML</a> and\n <a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics\">CSS</a>, including general\n knowledge of\n <a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Pseudo_classes_and_elements\">pseudo-classes and pseudo-elements</a>.\n </td>\n </tr>\n <tr>\n <th scope=\"row\">Objective:</th>\n <td>\n To understand what parts of forms are hard to style, and why; to learn\n what can be done to customize them.\n </td>\n </tr>\n </tbody>\n</table></figure>"}},{"type":"prose","value":{"id":"what_pseudo-classes_do_we_have_available","title":"What pseudo-classes do we have available?","isH3":false,"content":"<p>The original pseudo-classes (from <a href=\"https://www.w3.org/TR/CSS21/selector.html#dynamic-pseudo-classes\" class=\"external\" target=\"_blank\">CSS 2.1</a>) that are relevant to forms are:</p>\n<ul>\n<li><a href=\"/en-US/docs/Web/CSS/:hover\"><code>:hover</code></a>: Selects an element only when it is being hovered over by a mouse pointer.</li>\n<li><a href=\"/en-US/docs/Web/CSS/:focus\"><code>:focus</code></a>: Selects an element only when it is focused (i.e. by being tabbed to via the keyboard).</li>\n<li><a href=\"/en-US/docs/Web/CSS/:active\"><code>:active</code></a>: selects an element only when it is being activated (i.e. while it is being clicked on, or when the <kbd>Return</kbd> / <kbd>Enter</kbd> key is being pressed down in the case of a keyboard activation).</li>\n</ul>\n<p>These basic pseudo-classes should be familiar to you now. <a href=\"/en-US/docs/Web/CSS/CSS_selectors\">CSS selectors</a> provide several other pseudo-classes related to HTML forms. These provide several useful targeting conditions that you can take advantage of. We'll discuss these in more detail in the sections below, but briefly, the main ones we'll be looking at are:</p>\n<ul>\n<li><a href=\"/en-US/docs/Web/CSS/:required\"><code>:required</code></a> and <a href=\"/en-US/docs/Web/CSS/:optional\"><code>:optional</code></a>: Target elements that can be required (e.g. elements that support the <a href=\"/en-US/docs/Web/HTML/Attributes/required\"><code>required</code></a> HTML attribute)), based on whether they are required or optional.</li>\n<li><a href=\"/en-US/docs/Web/CSS/:valid\"><code>:valid</code></a> and <a href=\"/en-US/docs/Web/CSS/:invalid\"><code>:invalid</code></a>, and <a href=\"/en-US/docs/Web/CSS/:in-range\"><code>:in-range</code></a> and <a href=\"/en-US/docs/Web/CSS/:out-of-range\"><code>:out-of-range</code></a>: Target form controls that are valid/invalid according to form validation constraints set on them, or in-range/out-of-range.</li>\n<li><a href=\"/en-US/docs/Web/CSS/:enabled\"><code>:enabled</code></a> and <a href=\"/en-US/docs/Web/CSS/:disabled\"><code>:disabled</code></a>, and <a href=\"/en-US/docs/Web/CSS/:read-only\"><code>:read-only</code></a> and <a href=\"/en-US/docs/Web/CSS/:read-write\"><code>:read-write</code></a>: Target elements that can be disabled (e.g. elements that support the <a href=\"/en-US/docs/Web/HTML/Attributes/disabled\"><code>disabled</code></a> HTML attribute), based on whether they are currently enabled or disabled, and read-write or read-only form controls (e.g. elements with the <a href=\"/en-US/docs/Web/HTML/Attributes/readonly\"><code>readonly</code></a> HTML attribute set).</li>\n<li><a href=\"/en-US/docs/Web/CSS/:checked\"><code>:checked</code></a>, <a href=\"/en-US/docs/Web/CSS/:indeterminate\"><code>:indeterminate</code></a>, and <a href=\"/en-US/docs/Web/CSS/:default\"><code>:default</code></a>: Respectively target checkboxes and radio buttons that are checked, in an indeterminate state (neither checked or not checked), and the default selected option when the page loads (e.g. an <a href=\"/en-US/docs/Web/HTML/Element/input/checkbox\"><code><input type=\"checkbox\"></code></a> with the <a href=\"/en-US/docs/Web/HTML/Element/input#checked\"><code>checked</code></a> attribute set, or an <a href=\"/en-US/docs/Web/HTML/Element/option\"><code><option></code></a> element with the <a href=\"/en-US/docs/Web/HTML/Element/option#selected\"><code>selected</code></a> attribute set).</li>\n</ul>\n<p>There are many others, but the ones listed above are the most obviously useful. Some of them are aimed at solving very specific niche problems. The UI pseudo-classes listed above have excellent browser support, but of course, you should test your form implementations carefully to ensure they work for your target audience.</p>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nA number of the pseudo-classes discussed here are concerned with styling form controls based on their validation state (is their data valid, or not?) You'll learn much more about setting and controlling validation constraints in our next article — <a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation\">Client-side form validation</a> — but for now we'll keep things simple regarding the form validation, so it doesn't confuse things.</p>\n</div>"}},{"type":"prose","value":{"id":"styling_inputs_based_on_whether_they_are_required_or_not","title":"Styling inputs based on whether they are required or not","isH3":false,"content":"<p>One of the most basic concepts regarding client-side form validation is whether a form input is required (it has to be filled in before the form can be submitted) or optional.</p>\n<p><a href=\"/en-US/docs/Web/HTML/Element/input\"><code><input></code></a>, <a href=\"/en-US/docs/Web/HTML/Element/select\"><code><select></code></a>, and <a href=\"/en-US/docs/Web/HTML/Element/textarea\"><code><textarea></code></a> elements have a <code>required</code> attribute available which, when set, means that you have to fill in that control before the form will successfully submit. For example:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">html</span></div><pre class=\"brush: html notranslate\"><code><form>\n <fieldset>\n <legend>Feedback form</legend>\n <div>\n <label for=\"fname\">First name: </label>\n <input id=\"fname\" name=\"fname\" type=\"text\" required />\n </div>\n <div>\n <label for=\"lname\">Last name: </label>\n <input id=\"lname\" name=\"lname\" type=\"text\" required />\n </div>\n <div>\n <label for=\"email\">\n Email address (include if you want a response):\n </label>\n <input id=\"email\" name=\"email\" type=\"email\" />\n </div>\n <div><button>Submit</button></div>\n </fieldset>\n</form>\n</code></pre></div>\n<p>Here, the first name and last name are required, but the email address is optional.</p>\n<p>You can match these two states using the <a href=\"/en-US/docs/Web/CSS/:required\"><code>:required</code></a> and <a href=\"/en-US/docs/Web/CSS/:optional\"><code>:optional</code></a> pseudo-classes. For example, if we apply the following CSS to the above HTML:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>input:required {\n border: 1px solid black;\n}\n\ninput:optional {\n border: 1px solid silver;\n}\n</code></pre></div>\n<p>The required controls would have a black border, and the optional control will have a silver border, like so:</p>\n<iframe width=\"100%\" height=\"400\" src=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/basic-required-optional.html\" loading=\"lazy\"></iframe>\n<p>You can also try submitting the form without filling it in, to see the client-side validation error messages browsers give you by default.</p>\n<p>The above form isn't bad, but it isn't great either. For a start, we are signaling required versus optional status using color alone, which isn't great for colorblind people. Second, the standard convention on the web for required status is an asterisk (<code>*</code>), or the word \"required\" being associated with the controls in question.</p>\n<p>In the next section, we'll look at a better example of indicating required fields using <code>:required</code>, which also digs into using generated content.</p>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nYou'll probably not find yourself using the <code>:optional</code> pseudo-class very often. Form controls are optional by default, so you could just do your optional styling by default, and add styles on top for required controls.</p>\n</div>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nIf one radio button in a same-named group of radio buttons has the <code>required</code> attribute set, all the radio buttons will be invalid until one is selected, but only the one with the attribute assigned will actually match <a href=\"/en-US/docs/Web/CSS/:required\"><code>:required</code></a>.</p>\n</div>"}},{"type":"prose","value":{"id":"using_generated_content_with_pseudo-classes","title":"Using generated content with pseudo-classes","isH3":false,"content":"<p>In previous articles, we've seen the usage of <a href=\"/en-US/docs/Web/CSS/CSS_generated_content\">generated content</a>, but we thought now would be a good time to talk about it in a bit more detail.</p>\n<p>The idea is that we can use the <a href=\"/en-US/docs/Web/CSS/::before\"><code>::before</code></a> and <a href=\"/en-US/docs/Web/CSS/::after\"><code>::after</code></a> pseudo-elements along with the <a href=\"/en-US/docs/Web/CSS/content\"><code>content</code></a> property to make a chunk of content appear before or after the affected element. The chunk of content is not added to the DOM, so it may be invisible to some screen readers. Because it is a pseudo-element, it can be targeted with styles in the same way that any actual DOM node can.</p>\n<p>This is really useful when you want to add a visual indicator to an element, such as a label or icon, when alternative indicators are also available to ensure accessibility for all users. For example, in our <a href=\"https://mdn.github.io/learning-area/html/forms/styling-examples/radios-styled.html\" class=\"external\" target=\"_blank\">custom radio buttons example</a>, we use generated content to handle the placement and animation of the custom radio button's inner circle when a radio button is selected:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>input[type=\"radio\"]::before {\n display: block;\n content: \" \";\n width: 10px;\n height: 10px;\n border-radius: 6px;\n background-color: red;\n font-size: 1.2em;\n transform: translate(3px, 3px) scale(0);\n transform-origin: center;\n transition: all 0.3s ease-in;\n}\n\ninput[type=\"radio\"]:checked::before {\n transform: translate(3px, 3px) scale(1);\n transition: all 0.3s cubic-bezier(0.25, 0.25, 0.56, 2);\n}\n</code></pre></div>\n<p>This is really useful — screen readers already let their users know when a radio button or checkbox they encounter is checked/selected, so you don't want them to read out another DOM element that indicates selection — that could be confusing. Having a purely visual indicator solves this problem.</p>\n<p>Not all <code><input></code> types support having generated content put on them. All input types that show dynamic text in them, such as <code>text</code>, <code>password</code>, or <code>button</code>, don't display generated content. Others, including <code>range</code>, <code>color</code>, <code>checkbox</code>, etc., display generated content.</p>\n<p>Back to our required/optional example from before, this time we'll not alter the appearance of the input itself — we'll use generated content to add an indicating label (<a href=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/required-optional-generated.html\" class=\"external\" target=\"_blank\">see it live here</a>, and see the <a href=\"https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/required-optional-generated.html\" class=\"external\" target=\"_blank\">source code here</a>).</p>\n<p>First of all, we'll add a paragraph to the top of the form to say what you are looking for:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">html</span></div><pre class=\"brush: html notranslate\"><code><p>Required fields are labeled with \"required\".</p>\n</code></pre></div>\n<p>Screen reader users will get \"required\" read out as an extra bit of information when they get to each required input, while sighted users will get our label.</p>\n<p>As previously mentioned, text inputs don't support generated content, so we add an empty <a href=\"/en-US/docs/Web/HTML/Element/span\"><code><span></code></a> to hang the generated content on:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">html</span></div><pre class=\"brush: html notranslate\"><code><div>\n <label for=\"fname\">First name: </label>\n <input id=\"fname\" name=\"fname\" type=\"text\" required />\n <span></span>\n</div>\n</code></pre></div>\n<p>The immediate problem with this was that the span was dropping onto a new line below the input because the input and label are both set with <code>width: 100%</code>. To fix this we style the parent <code><div></code> to become a flex container, but also tell it to wrap its contents onto new lines if the content becomes too long:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>fieldset > div {\n margin-bottom: 20px;\n display: flex;\n flex-flow: row wrap;\n}\n</code></pre></div>\n<p>The effect this has is that the label and input sit on separate lines because they are both <code>width: 100%</code>, but the <code><span></code> has a width of <code>0</code> so it can sit on the same line as the input.</p>\n<p>Now onto the generated content. We create it using this CSS:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>input + span {\n position: relative;\n}\n\ninput:required + span::after {\n font-size: 0.7rem;\n position: absolute;\n content: \"required\";\n color: white;\n background-color: black;\n padding: 5px 10px;\n top: -26px;\n left: -70px;\n}\n</code></pre></div>\n<p>We set the <code><span></code> to <code>position: relative</code> so that we can set the generated content to <code>position: absolute</code> and position it relative to the <code><span></code> rather than the <code><body></code> (The generated content acts as though it is a child node of the element it is generated on, for the purposes of positioning).</p>\n<p>Then we give the generated content the content \"required\", which is what we wanted our label to say, and style and position it as we want. The result is seen below.</p>\n<iframe width=\"100%\" height=\"430\" src=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/required-optional-generated.html\" loading=\"lazy\"></iframe>"}},{"type":"prose","value":{"id":"styling_controls_based_on_whether_their_data_is_valid","title":"Styling controls based on whether their data is valid","isH3":false,"content":"<p>The other really important, fundamental concept in form validation is whether a form control's data is valid or not (in the case of numerical data, we can also talk about in-range and out-of-range data). Form controls with <a href=\"/en-US/docs/Web/HTML/Constraint_validation\">constraint limitations</a> can be targeted based on these states.</p>"}},{"type":"prose","value":{"id":"valid_and_invalid","title":":valid and :invalid","isH3":true,"content":"<p>You can target form controls using the <a href=\"/en-US/docs/Web/CSS/:valid\"><code>:valid</code></a> and <a href=\"/en-US/docs/Web/CSS/:invalid\"><code>:invalid</code></a> pseudo-classes. Some points worth bearing in mind:</p>\n<ul>\n<li>Controls with no constraint validation will always be valid, and therefore matched with <code>:valid</code>.</li>\n<li>Controls with <code>required</code> set on them that have no value are counted as invalid — they will be matched with <code>:invalid</code> and <code>:required</code>.</li>\n<li>Controls with built-in validation, such as <code><input type=\"email\"></code> or <code><input type=\"url\"></code> are (matched with) <code>:invalid</code> when the data entered into them does not match the pattern they are looking for (but they are valid when empty).</li>\n<li>Controls whose current value is outside the range limits specified by the <a href=\"/en-US/docs/Web/HTML/Element/input#min\"><code>min</code></a> and <a href=\"/en-US/docs/Web/HTML/Element/input#max\"><code>max</code></a> attributes are (matched with) <code>:invalid</code>, but also matched by <a href=\"/en-US/docs/Web/CSS/:out-of-range\"><code>:out-of-range</code></a>, as you'll see later on.</li>\n<li>There are some other ways to make an element matched by <code>:valid</code>/<code>:invalid</code>, as you'll see in the <a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation\">Client-side form validation</a> article. But we'll keep things simple for now.</li>\n</ul>\n<p>Let's go in and look at an example of <code>:valid</code>/<code>:invalid</code> (see <a href=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/valid-invalid.html\" class=\"external\" target=\"_blank\">valid-invalid.html</a> for the live version, and also check out the <a href=\"https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/valid-invalid.html\" class=\"external\" target=\"_blank\">source code</a>).</p>\n<p>As in the previous example, we've got extra <code><span></code>s to generate content on, which we'll use to provide indicators of valid/invalid data:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">html</span></div><pre class=\"brush: html notranslate\"><code><div>\n <label for=\"fname\">First name: </label>\n <input id=\"fname\" name=\"fname\" type=\"text\" required />\n <span></span>\n</div>\n</code></pre></div>\n<p>To provide these indicators, we use the following CSS:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>input + span {\n position: relative;\n}\n\ninput + span::before {\n position: absolute;\n right: -20px;\n top: 5px;\n}\n\ninput:invalid {\n border: 2px solid red;\n}\n\ninput:invalid + span::before {\n content: \"✖\";\n color: red;\n}\n\ninput:valid + span::before {\n content: \"✓\";\n color: green;\n}\n</code></pre></div>\n<p>As before, we set the <code><span></code>s to <code>position: relative</code> so that we can position the generated content relative to them. We then absolutely position different generated content depending on whether the form's data is valid or invalid — a green check or a red cross, respectively. To add a bit of extra urgency to the invalid data, we've also given the inputs a thick red border when invalid.</p>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nWe've used <code>::before</code> to add these labels, as we were already using <code>::after</code> for the \"required\" labels.</p>\n</div>\n<p>You can try it below:</p>\n<iframe width=\"100%\" height=\"430\" src=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/valid-invalid.html\" loading=\"lazy\"></iframe>\n<p>Notice how the required text inputs are invalid when empty, but valid when they have something filled in. The email input on the other hand is valid when empty, as it is not required, but invalid when it contains something that is not a proper email address.</p>"}},{"type":"prose","value":{"id":"in-range_and_out-of-range_data","title":"In-range and out-of-range data","isH3":true,"content":"<p>As we hinted at above, there are two other related pseudo-classes to consider — <a href=\"/en-US/docs/Web/CSS/:in-range\"><code>:in-range</code></a> and <a href=\"/en-US/docs/Web/CSS/:out-of-range\"><code>:out-of-range</code></a>. These match numeric inputs where range limits are specified by the <a href=\"/en-US/docs/Web/HTML/Element/input#min\"><code>min</code></a> and <a href=\"/en-US/docs/Web/HTML/Element/input#max\"><code>max</code></a>, when their data is inside or outside the specified range, respectively.</p>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nNumeric input types are <code>date</code>, <code>month</code>, <code>week</code>, <code>time</code>, <code>datetime-local</code>, <code>number</code>, and <code>range</code>.</p>\n</div>\n<p>It is worth noting that inputs whose data is in-range will also be matched by the <code>:valid</code> pseudo-class and inputs whose data is out-of-range will also be matched by the <code>:invalid</code> pseudo-class. So why have both? The issue is really one of semantics — out-of-range is a more specific type of invalid communication, so you might want to provide a different message for out-of-range inputs, which will be more helpful to users than just saying \"invalid\". You might even want to provide both.</p>\n<p>Let's look at an example that does exactly this. Our <a href=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/out-of-range.html\" class=\"external\" target=\"_blank\">out-of-range.html</a> demo (see also the <a href=\"https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/out-of-range.html\" class=\"external\" target=\"_blank\">source code</a>) builds on top of the previous example to provide out-of-range messages for the numeric inputs, as well as saying whether they are required.</p>\n<p>The numeric input looks like this:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">html</span></div><pre class=\"brush: html notranslate\"><code><div>\n <label for=\"age\">Age (must be 12+): </label>\n <input id=\"age\" name=\"age\" type=\"number\" min=\"12\" max=\"120\" required />\n <span></span>\n</div>\n</code></pre></div>\n<p>And the CSS looks like this:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>input + span {\n position: relative;\n}\n\ninput + span::after {\n font-size: 0.7rem;\n position: absolute;\n padding: 5px 10px;\n top: -26px;\n}\n\ninput:required + span::after {\n color: white;\n background-color: black;\n content: \"Required\";\n left: -70px;\n}\n\ninput:out-of-range + span::after {\n color: white;\n background-color: red;\n width: 155px;\n content: \"Outside allowable value range\";\n left: -182px;\n}\n</code></pre></div>\n<p>This is a similar story to what we had before in the <code>:required</code> example, except that here we've split out the declarations that apply to any <code>::after</code> content into a separate rule, and given the separate <code>::after</code> content for <code>:required</code> and <code>:out-of-range</code> states their own content and styling. You can try it here:</p>\n<iframe width=\"100%\" height=\"430\" src=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/out-of-range.html\" loading=\"lazy\"></iframe>\n<p>It is possible for the number input to be both required and out-of-range at the same time, so what happens then? Because the <code>:out-of-range</code> rule appears later in the source code than the <code>:required</code> rule, the <a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Handling_conflicts#understanding_the_cascade\">cascade rules</a> come into play, and the out of range message is shown.</p>\n<p>This works quite nicely — when the page first loads, \"Required\" is shown, along with a red cross and border. When you've typed in a valid age (i.e. in the range of 12-120), the input turns valid. If however, you then change the age entry to one that is out of range, the \"Outside allowable value range\" message then pops up in place of \"Required\".</p>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nTo enter an invalid/out-of-range value, you'll have to actually focus the form and type it in using the keyboard. The spinner buttons won't let you increment/decrement the value outside the allowable range.</p>\n</div>"}},{"type":"prose","value":{"id":"styling_enabled_and_disabled_inputs_and_read-only_and_read-write","title":"Styling enabled and disabled inputs, and read-only and read-write","isH3":false,"content":"<p>An enabled element is an element that can be activated; it can be selected, clicked on, typed into, etc. A disabled element on the other hand cannot be interacted with in any way, and its data isn't even sent to the server.</p>\n<p>These two states can be targeted using <a href=\"/en-US/docs/Web/CSS/:enabled\"><code>:enabled</code></a> and <a href=\"/en-US/docs/Web/CSS/:disabled\"><code>:disabled</code></a>. Why are disabled inputs useful? Well, sometimes if some data does not apply to a certain user, you might not even want to submit that data when they submit the form. A classic example is a shipping form — commonly you'll get asked if you want to use the same address for billing and shipping; if so, you can just send a single address to the server, and might as well just disable the billing address fields.</p>\n<p>Let's have a look at an example that does just this. First of all, the HTML is a simple form containing text inputs, plus a checkbox to toggle disabling the billing address on and off. The billing address fields are disabled by default.</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">html</span></div><pre class=\"brush: html notranslate\"><code><form>\n <fieldset id=\"shipping\">\n <legend>Shipping address</legend>\n <div>\n <label for=\"name1\">Name: </label>\n <input id=\"name1\" name=\"name1\" type=\"text\" required />\n </div>\n <div>\n <label for=\"address1\">Address: </label>\n <input id=\"address1\" name=\"address1\" type=\"text\" required />\n </div>\n <div>\n <label for=\"zip-code1\">Zip/postal code: </label>\n <input id=\"zip-code1\" name=\"zip-code1\" type=\"text\" required />\n </div>\n </fieldset>\n <fieldset id=\"billing\">\n <legend>Billing address</legend>\n <div>\n <label for=\"billing-checkbox\">Same as shipping address:</label>\n <input type=\"checkbox\" id=\"billing-checkbox\" checked />\n </div>\n <div>\n <label for=\"name\" class=\"billing-label disabled-label\">Name: </label>\n <input id=\"name\" name=\"name\" type=\"text\" disabled required />\n </div>\n <div>\n <label for=\"address2\" class=\"billing-label disabled-label\">\n Address:\n </label>\n <input id=\"address2\" name=\"address2\" type=\"text\" disabled required />\n </div>\n <div>\n <label for=\"zip-code2\" class=\"billing-label disabled-label\">\n Zip/postal code:\n </label>\n <input id=\"zip-code2\" name=\"zip-code2\" type=\"text\" disabled required />\n </div>\n </fieldset>\n\n <div><button>Submit</button></div>\n</form>\n</code></pre></div>\n<p>Now onto the CSS. The most relevant parts of this example are as follows:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>input[type=\"text\"]:disabled {\n background: #eee;\n border: 1px solid #ccc;\n}\n\nlabel:has(+ :disabled) {\n color: #aaa;\n}\n</code></pre></div>\n<p>We've directly selected the inputs we want to disable using <code>input[type=\"text\"]:disabled</code>, but we also wanted to gray out the corresponding text labels. As the labels are right before their inputs, we selected those using the pseudo-class <a href=\"/en-US/docs/Web/CSS/:has\"><code>:has</code></a>.</p>\n<p>Now finally, we've used some JavaScript to toggle the disabling of the billing address fields:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">js</span></div><pre class=\"brush: js notranslate\"><code>// Wait for the page to finish loading\ndocument.addEventListener(\n \"DOMContentLoaded\",\n () => {\n // Attach `change` event listener to checkbox\n document\n .getElementById(\"billing-checkbox\")\n .addEventListener(\"change\", toggleBilling);\n },\n false,\n);\n\nfunction toggleBilling() {\n // Select the billing text fields\n const billingItems = document.querySelectorAll('#billing input[type=\"text\"]');\n\n // Toggle the billing text fields\n for (let i = 0; i < billingItems.length; i++) {\n billingItems[i].disabled = !billingItems[i].disabled;\n }\n}\n</code></pre></div>\n<p>It uses the <a href=\"/en-US/docs/Web/API/HTMLElement/change_event\"><code>change</code> event</a> to let the user enable/disable the billing fields, and toggle the styling of the associated labels.</p>\n<p>You can see the example in action below (also <a href=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/enabled-disabled-shipping.html\" class=\"external\" target=\"_blank\">see it live here</a>, and see the <a href=\"https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/enabled-disabled-shipping.html\" class=\"external\" target=\"_blank\">source code</a>):</p>\n<iframe width=\"100%\" height=\"600\" src=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/enabled-disabled-shipping.html\" loading=\"lazy\"></iframe>"}},{"type":"prose","value":{"id":"read-only_and_read-write","title":"Read-only and read-write","isH3":true,"content":"<p>In a similar manner to <code>:disabled</code> and <code>:enabled</code>, the <code>:read-only</code> and <code>:read-write</code> pseudo-classes target two states that form inputs toggle between. As with disabled inputs, the user can't edit read-only inputs. However, unlike disabled inputs, read-only input values will be submitted to the server. Read-write means they can be edited — their default state.</p>\n<p>An input is set to read-only using the <code>readonly</code> attribute. As an example, imagine a confirmation page where the developer has sent the details filled in on previous pages over to this page, with the aim of getting the user to check them all in one place, add any final data that is needed, and then confirm the order by submitting. At this point, all the final form data can be sent to the server in one go.</p>\n<p>Let's look at what a form might look like (see <a href=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/readonly-confirmation.html\" class=\"external\" target=\"_blank\">readonly-confirmation.html</a> for the live example; also <a href=\"https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/readonly-confirmation.html\" class=\"external\" target=\"_blank\">see the source code</a>).</p>\n<p>A fragment of the HTML is as follows — note the readonly attribute:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">html</span></div><pre class=\"brush: html notranslate\"><code><div>\n <label for=\"name\">Name: </label>\n <input id=\"name\" name=\"name\" type=\"text\" value=\"Mr Soft\" readonly />\n</div>\n</code></pre></div>\n<p>If you try the live example, you'll see that the top set of form elements are not editable, however, the values are submitted when the form is submitted. We've styled the form controls using the <code>:read-only</code> and <code>:read-write</code> pseudo-classes, like so:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>input:read-only,\ntextarea:read-only {\n border: 0;\n box-shadow: none;\n background-color: white;\n}\n\ntextarea:read-write {\n box-shadow: inset 1px 1px 3px #ccc;\n border-radius: 5px;\n}\n</code></pre></div>\n<p>The full example looks like this:</p>\n<iframe width=\"100%\" height=\"660\" src=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/readonly-confirmation.html\" loading=\"lazy\"></iframe>\n<div class=\"notecard note\">\n<p><strong>Note:</strong> <code>:enabled</code> and <code>:read-write</code> are two more pseudo-classes that you'll probably rarely use, given that they describe the default states of input elements.</p>\n</div>"}},{"type":"prose","value":{"id":"radio_and_checkbox_states_—_checked_default_indeterminate","title":"Radio and checkbox states — checked, default, indeterminate","isH3":false,"content":"<p>As we've seen in earlier articles in the module, <a href=\"/en-US/docs/Web/HTML/Element/input/radio\">radio buttons</a> and <a href=\"/en-US/docs/Web/HTML/Element/input/checkbox\">checkboxes</a> can be checked or unchecked. But there are a couple of other states to consider too:</p>\n<ul>\n<li><a href=\"/en-US/docs/Web/CSS/:default\"><code>:default</code></a>: Matches radios/checkboxes that are checked by default, on page load (i.e. by setting the <code>checked</code> attribute on them). These match the <a href=\"/en-US/docs/Web/CSS/:default\"><code>:default</code></a> pseudo-class, even if the user unchecks them.</li>\n<li><a href=\"/en-US/docs/Web/CSS/:indeterminate\"><code>:indeterminate</code></a>: When radios/checkboxes are neither checked nor unchecked, they are considered <em>indeterminate</em> and will match the <a href=\"/en-US/docs/Web/CSS/:indeterminate\"><code>:indeterminate</code></a> pseudo-class. More on what this means below.</li>\n</ul>"}},{"type":"prose","value":{"id":"checked","title":":checked","isH3":true,"content":"<p>When checked, they will be matched by the <a href=\"/en-US/docs/Web/CSS/:checked\"><code>:checked</code></a> pseudo-class.</p>\n<p>The most common use of this is to add a different style onto the checkbox or radio button when it is checked, in cases where you've removed the system default styling with <a href=\"/en-US/docs/Web/CSS/appearance\"><code>appearance: none;</code></a> and want to build the styles back up yourself. We saw examples of this in the previous article when we talked about <a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Advanced_form_styling#using_appearance_none_on_radioscheckboxes\">Using <code>appearance: none</code> on radios/checkboxes</a>.</p>\n<p>As a recap, the <code>:checked</code> code from our <a href=\"https://mdn.github.io/learning-area/html/forms/styling-examples/radios-styled.html\" class=\"external\" target=\"_blank\">Styled radio buttons</a> example looks like so:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>input[type=\"radio\"]::before {\n display: block;\n content: \" \";\n width: 10px;\n height: 10px;\n border-radius: 6px;\n background-color: red;\n font-size: 1.2em;\n transform: translate(3px, 3px) scale(0);\n transform-origin: center;\n transition: all 0.3s ease-in;\n}\n\ninput[type=\"radio\"]:checked::before {\n transform: translate(3px, 3px) scale(1);\n transition: all 0.3s cubic-bezier(0.25, 0.25, 0.56, 2);\n}\n</code></pre></div>\n<p>You can try it out here:</p>\n<iframe width=\"100%\" height=\"200\" src=\"https://mdn.github.io/learning-area/html/forms/styling-examples/radios-styled.html\" loading=\"lazy\"></iframe>\n<p>Basically, we build the styling for a radio button's \"inner circle\" using the <code>::before</code> pseudo-element, but set a <code>scale(0)</code> <a href=\"/en-US/docs/Web/CSS/transform\"><code>transform</code></a> on it. We then use a <a href=\"/en-US/docs/Web/CSS/transition\"><code>transition</code></a> to make the generated content on the label nicely animate into view when the radio is selected/checked. The advantage of using a transform rather than transitioning <a href=\"/en-US/docs/Web/CSS/width\"><code>width</code></a>/<a href=\"/en-US/docs/Web/CSS/height\"><code>height</code></a> is that you can use <a href=\"/en-US/docs/Web/CSS/transform-origin\"><code>transform-origin</code></a> to make it grow from the center of the circle, rather than having it appear to grow from the circle's corner, and there is no jumping behavior as no box model property values are updated.</p>"}},{"type":"prose","value":{"id":"default_and_indeterminate","title":":default and :indeterminate","isH3":true,"content":"<p>As mentioned above, the <a href=\"/en-US/docs/Web/CSS/:default\"><code>:default</code></a> pseudo-class matches radios/checkboxes that are checked by default, on page load, even when unchecked. This could be useful for adding an indicator to a list of options to remind the user what the defaults (or starting options) were, in case they want to reset their choices.</p>\n<p>Also, the radios/checkboxes mentioned above will be matched by the <a href=\"/en-US/docs/Web/CSS/:indeterminate\"><code>:indeterminate</code></a> pseudo-class when they are in a state where they are neither checked nor unchecked. But what does this mean? Elements that are indeterminate include:</p>\n<ul>\n<li><a href=\"/en-US/docs/Web/HTML/Element/input/radio\"><code><input/radio></code></a> inputs, when all radio buttons in a same-named group are unchecked</li>\n<li><a href=\"/en-US/docs/Web/HTML/Element/input/checkbox\"><code><input/checkbox></code></a> inputs whose <code>indeterminate</code> property is set to <code>true</code> via JavaScript</li>\n<li><a href=\"/en-US/docs/Web/HTML/Element/progress\"><code><progress></code></a> elements that have no value.</li>\n</ul>\n<p>This isn't something you'll likely use very often. One use case could be an indicator to tell users that they really need to select a radio button before they move on.</p>\n<p>Let's look at a couple of modified versions of the previous example that remind the user what the default option was, and style the labels of radio buttons when indeterminate. Both of these have the following HTML structure for the inputs:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">html</span></div><pre class=\"brush: html notranslate\"><code><p>\n <input type=\"radio\" name=\"fruit\" value=\"cherry\" id=\"cherry\" />\n <label for=\"cherry\">Cherry</label>\n <span></span>\n</p>\n</code></pre></div>\n<p>For the <code>:default</code> example, we've added the <code>checked</code> attribute to the middle radio button input, so it will be selected by default when loaded. We then style this with the following CSS:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>input ~ span {\n position: relative;\n}\n\ninput:default ~ span::after {\n font-size: 0.7rem;\n position: absolute;\n content: \"Default\";\n color: white;\n background-color: black;\n padding: 5px 10px;\n right: -65px;\n top: -3px;\n}\n</code></pre></div>\n<p>This provides a little \"Default\" label on the item that was originally selected when the page loaded. Note here we are using the subsequent-sibling combinator (<code>~</code>) rather than the Next-sibling combinator (<code>+</code>) — we need to do this because the <code><span></code> does not come right after the <code><input></code> in the source order.</p>\n<p>See the live result below:</p>\n<iframe width=\"100%\" height=\"200\" src=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/radios-checked-default.html\" loading=\"lazy\"></iframe>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nYou can also find the example live on GitHub at <a href=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/radios-checked-default.html\" class=\"external\" target=\"_blank\">radios-checked-default.html</a> (also see the <a href=\"https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/radios-checked-default.html\" class=\"external\" target=\"_blank\">source code</a>.)</p>\n</div>\n<p>For the <code>:indeterminate</code> example, we've got no default selected radio button — this is important — if there was, then there would be no indeterminate state to style. We style the indeterminate radio buttons with the following CSS:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">css</span></div><pre class=\"brush: css notranslate\"><code>input[type=\"radio\"]:indeterminate {\n outline: 2px solid red;\n animation: 0.4s linear infinite alternate outline-pulse;\n}\n\n@keyframes outline-pulse {\n from {\n outline: 2px solid red;\n }\n\n to {\n outline: 6px solid red;\n }\n}\n</code></pre></div>\n<p>This creates a fun little animated outline on the radio buttons, which hopefully indicates that you need to select one of them!</p>\n<p>See the live result below:</p>\n<iframe width=\"100%\" height=\"200\" src=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/radios-checked-indeterminate.html\" loading=\"lazy\"></iframe>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nYou can also find the example live on GitHub at <a href=\"https://mdn.github.io/learning-area/html/forms/pseudo-classes/radios-checked-indeterminate.html\" class=\"external\" target=\"_blank\">radios-checked-indeterminate.html</a> (also see the <a href=\"https://github.com/mdn/learning-area/blob/main/html/forms/pseudo-classes/radios-checked-indeterminate.html\" class=\"external\" target=\"_blank\">source code</a>.)</p>\n</div>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nYou can find an <a href=\"/en-US/docs/Web/HTML/Element/input/checkbox#indeterminate_state_checkboxes\">interesting example involving <code>indeterminate</code> states</a> on the <a href=\"/en-US/docs/Web/HTML/Element/input/checkbox\"><code><input type=\"checkbox\"></code></a> reference page.</p>\n</div>"}},{"type":"prose","value":{"id":"more_pseudo-classes","title":"More pseudo-classes","isH3":false,"content":"<p>There are a number of other pseudo-classes of interest, and we don't have space to write about them all in detail here. Let's talk about a few more that you should take the time to investigate.</p>\n<ul>\n<li>The <a href=\"/en-US/docs/Web/CSS/:focus-within\"><code>:focus-within</code></a> pseudo-class matches an element that has received focus or <em>contains</em> an element that has received focus. This is useful if you want a whole form to highlight in some way when an input inside it is focused.</li>\n<li>The <a href=\"/en-US/docs/Web/CSS/:focus-visible\"><code>:focus-visible</code></a> pseudo-class matches focused elements that received focus via keyboard interaction (rather than touch or mouse) — useful if you want to show a different style for keyboard focus compared to mouse (or other) focus.</li>\n<li>The <a href=\"/en-US/docs/Web/CSS/:placeholder-shown\"><code>:placeholder-shown</code></a> pseudo-class matches <a href=\"/en-US/docs/Web/HTML/Element/input\"><code><input></code></a> and <a href=\"/en-US/docs/Web/HTML/Element/textarea\"><code><textarea></code></a> elements that have their placeholder showing (i.e. the contents of the <a href=\"/en-US/docs/Web/HTML/Element/input#placeholder\"><code>placeholder</code></a> attribute) because the value of the element is empty.</li>\n</ul>\n<p>The following are also interesting, but as yet not well-supported in browsers:</p>\n<ul>\n<li>The <a href=\"/en-US/docs/Web/CSS/:blank\"><code>:blank</code></a> pseudo-class selects empty form controls. <a href=\"/en-US/docs/Web/CSS/:empty\"><code>:empty</code></a> also matches elements that have no children, like <a href=\"/en-US/docs/Web/HTML/Element/input\"><code><input></code></a>, but it is more general — it also matches other <a href=\"/en-US/docs/Glossary/Void_element\">void elements</a> like <a href=\"/en-US/docs/Web/HTML/Element/br\"><code><br></code></a> and <a href=\"/en-US/docs/Web/HTML/Element/hr\"><code><hr></code></a>. <code>:empty</code> has reasonable browser support; the <code>:blank</code> pseudo-class's specification is not yet finished, so it is not yet supported in any browser.</li>\n<li>The <a href=\"/en-US/docs/Web/CSS/:user-invalid\"><code>:user-invalid</code></a> pseudo-class, when supported, will be similar to <a href=\"/en-US/docs/Web/CSS/:invalid\"><code>:invalid</code></a>, but with better user experience. If the value is valid when the input receives focus, the element may match <code>:invalid</code> as the user enters data if the value is temporarily invalid, but will only match <code>:user-invalid</code> when the element loses focus. If the value was originally invalid, it will match both <code>:invalid</code> and <code>:user-invalid</code> for the whole duration of the focus. In a similar manner to <code>:invalid</code>, it will stop matching <code>:user-invalid</code> if the value does become valid.</li>\n</ul>"}},{"type":"prose","value":{"id":"test_your_skills!","title":"Test your skills!","isH3":false,"content":"<p>You've reached the end of this article, but can you remember the most important information? You can find some further tests to verify that you've retained this information before you move on — see <a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Test_your_skills:_Advanced_styling\">Test your skills: Advanced styling</a>.</p>"}},{"type":"prose","value":{"id":"summary","title":"Summary","isH3":false,"content":"<p>This completes our look at UI pseudo-classes that relate to form inputs. Keep playing with them, and create some fun form styles! Next up, we'll move on to something different — <a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation\">client-side form validation</a>.</p>\n<ul class=\"prev-next\"><li><a class=\"button secondary\" href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Advanced_form_styling\"><span class=\"button-wrap\"> Previous </span></a></li><li><a class=\"button secondary\" href=\"/en-US/docs/Learn_web_development/Extensions/Forms\"><span class=\"button-wrap\"> Overview: Web forms</span></a></li><li><a class=\"button secondary\" href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation\"><span class=\"button-wrap\"> Next </span></a></li></ul>"}},{"type":"prose","value":{"id":"advanced_topics","title":"Advanced Topics","isH3":true,"content":"<ul>\n<li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/How_to_build_custom_form_controls\">How to build custom form controls</a></li>\n<li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Sending_forms_through_JavaScript\">Sending forms through JavaScript</a></li>\n</ul>"}}],"isActive":true,"isMarkdown":true,"isTranslated":false,"locale":"en-US","mdn_url":"/en-US/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes","modified":"2024-12-29T05:22:55.000Z","native":"English (US)","noIndexing":false,"other_translations":[{"locale":"de","title":"UI-Pseudoklassen","native":"Deutsch"},{"locale":"fr","title":"Pseudo-classes relatives à l'interface utilisateur","native":"Français"},{"locale":"ja","title":"UI 擬似クラス","native":"日本語"},{"locale":"zh-CN","title":"UI 伪类","native":"中文 (简体)"}],"pageTitle":"UI pseudo-classes - Learn web development | MDN","parents":[{"uri":"/en-US/docs/Learn_web_development","title":"Learn"},{"uri":"/en-US/docs/Learn_web_development/Extensions","title":"Extension modules"},{"uri":"/en-US/docs/Learn_web_development/Extensions/Forms","title":"Web forms"},{"uri":"/en-US/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes","title":"UI pseudo-classes"}],"popularity":null,"short_title":"UI pseudo-classes","sidebarHTML":"<ol><li class=\"section\"><a href=\"/en-US/docs/Learn_web_development/Getting_started\">Getting started modules</a></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Getting_started/Environment_setup\">Environment setup</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Environment_setup/Installing_software\">Installing basic software</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Environment_setup/Browsing_the_web\">Browsing the web</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Environment_setup/Code_editors\">Code editors</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Environment_setup/Dealing_with_files\">Dealing with files</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Environment_setup/Command_line\">Command line crash course</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Getting_started/Your_first_website\">Your first website</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Your_first_website/What_will_your_website_look_like\">What will your website look like?</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Your_first_website/Creating_the_content\">HTML: Creating the content</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Your_first_website/Styling_the_content\">CSS: Styling the content</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Your_first_website/Adding_interactivity\">JavaScript: Adding interactivity</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Your_first_website/Publishing_your_website\">Publishing your website</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Getting_started/Web_standards\">Web standards</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Web_standards/How_the_web_works\">How the web works</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Web_standards/The_web_standards_model\">The web standards model</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Web_standards/How_browsers_load_websites\">How browsers load websites</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Getting_started/Soft_skills\">Soft skills</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Soft_skills/Research_and_learning\">Research and learning</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Soft_skills/Collaboration_and_teamwork\">Collaboration and teamwork</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Soft_skills/Workflows_and_processes\">Workflows and processes</a></li><li><a href=\"/en-US/docs/Learn_web_development/Getting_started/Soft_skills/Job_interviews\">Succeeding in job interviews</a></li></ol></details></li><li class=\"section\"><a href=\"/en-US/docs/Learn_web_development/Core\">Core modules</a></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content\">Structuring content with HTML</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Basic_HTML_syntax\">Basic HTML syntax</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Webpage_metadata\">What's in the head? Webpage metadata</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Headings_and_paragraphs\">Headings and paragraphs in HTML</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Emphasis_and_importance\">Emphasis and importance</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Lists\">Lists</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Structuring_documents\">Structuring documents</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Advanced_text_features\">Advanced text features</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Creating_links\">Creating links</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Marking_up_a_letter\">Challenge: Marking up a letter</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Structuring_a_page_of_content\">Challenge: Structuring a page of content</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_images\">HTML images</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_video_and_audio\">HTML video and audio</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Mozilla_splash_page\">Challenge: Mozilla splash page</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_table_basics\">HTML table basics</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Table_accessibility\">HTML table accessibility</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Planet_data_table\">Challenge: Structuring a planet data table</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_forms\">Forms and buttons in HTML</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Structuring_content/Debugging_HTML\">Debugging HTML</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics\">CSS styling basics</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/What_is_CSS\">What is CSS?</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Getting_started\">Getting started with CSS</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Styling_a_bio_page\">Challenge: Styling a biography page</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Basic_selectors\">Basic CSS selectors</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Attribute_selectors\">Attribute selectors</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Pseudo_classes_and_elements\">Pseudo-classes and pseudo-elements</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Combinators\">Combinators</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Box_model\">The box model</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Handling_conflicts\">Handling conflicts</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Values_and_units\">CSS values and units</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Sizing\">Sizing items in CSS</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Backgrounds_and_borders\">Backgrounds and borders</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Overflow\">Overflowing content</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Images_media_forms\">Images, media, and form elements</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Tables\">Styling tables</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Debugging_CSS\">Debugging CSS</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Fundamental_CSS_comprehension\">Challenge: Fundamental CSS comprehension</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Fancy_letterheaded_paper\">Challenge: Creating fancy letterheaded paper</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Styling_basics/Cool-looking_box\">Challenge: A cool-looking box</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Core/Text_styling\">CSS text styling</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Core/Text_styling/Fundamentals\">Fundamental text and font styling</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Text_styling/Styling_lists\">Styling lists</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Text_styling/Styling_links\">Styling links</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Text_styling/Web_fonts\">Web fonts</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Text_styling/Typesetting_a_homepage\">Challenge: Typesetting a community school homepage</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Core/CSS_layout\">CSS layout</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Core/CSS_layout/Introduction\">Introduction to CSS layout</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/CSS_layout/Floats\">Floats</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/CSS_layout/Positioning\">Positioning</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/CSS_layout/Flexbox\">Flexbox</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/CSS_layout/Grids\">CSS grid layout</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/CSS_layout/Responsive_Design\">Responsive design</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/CSS_layout/Media_queries\">Media query fundamentals</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/CSS_layout/Fundamental_Layout_Comprehension\">Challenge: Fundamental layout comprehension</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Core/Scripting\">Dynamic scripting with JavaScript</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/What_is_JavaScript\">What is JavaScript?</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/A_first_splash\">A first splash into JavaScript</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/What_went_wrong\">What went wrong? Troubleshooting JavaScript</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Variables\">Storing the information you need — Variables</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Math\">Basic math in JavaScript — numbers and operators</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Strings\">Handling text — strings in JavaScript</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Useful_string_methods\">Useful string methods</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Arrays\">Arrays</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Silly_story_generator\">Challenge: Silly story generator</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Conditionals\">Making decisions in your code — conditionals</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Loops\">Looping code</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Functions\">Functions — reusable blocks of code</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Build_your_own_function\">Build your own function</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Return_values\">Function return values</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Events\">Introduction to events</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Event_bubbling\">Event bubbling</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Image_gallery\">Challenge: Image gallery</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Object_basics\">JavaScript object basics</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/DOM_scripting\">DOM scripting introduction</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Network_requests\">Making network requests with JavaScript</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/JSON\">Working with JSON</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Scripting/Debugging_JavaScript\">Debugging JavaScript and handling errors</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Core/Frameworks_libraries\">JavaScript frameworks and libraries</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Core/Frameworks_libraries/Introduction\">Introduction to client-side frameworks</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Frameworks_libraries/Main_features\">Framework main features</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_getting_started\">Getting started with React</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_todo_list_beginning\">Beginning our React todo list</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_components\">Componentizing our React app</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_interactivity_events_state\">React interactivity: Events and state</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_interactivity_filtering_conditional_rendering\">React interactivity: Editing, filtering, conditional rendering</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_accessibility\">Accessibility in React</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Frameworks_libraries/React_resources\">React resources</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Core/Accessibility\">Accessibility</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Core/Accessibility/What_is_accessibility\">What is accessibility?</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Accessibility/Tooling\">Accessibility tooling and assistive technology</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Accessibility/HTML\">HTML: A good basis for accessibility</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Accessibility/CSS_and_JavaScript\">CSS and JavaScript accessibility best practices</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Accessibility/WAI-ARIA_basics\">WAI-ARIA basics</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Accessibility/Multimedia\">Accessible multimedia</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Accessibility/Mobile\">Mobile accessibility</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Accessibility/Accessibility_troubleshooting\">Challenge: Accessibility troubleshooting</a></li></ol></details></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Design_for_developers\">Design for developers</a></li><li><a href=\"/en-US/docs/Learn_web_development/Core/Version_control\">Version control</a></li><li class=\"section\"><a href=\"/en-US/docs/Learn_web_development/Extensions\">Extension modules</a></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects\">Advanced JavaScript objects</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects/Object_prototypes\">Object prototypes</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects/Object-oriented_programming\">Object-oriented programming</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects/Classes_in_JavaScript\">Classes in JavaScript</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects/Object_building_practice\">Object building practice</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Advanced_JavaScript_objects/Adding_bouncing_balls_features\">Challenge: Adding features to our bouncing balls demo</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_APIs\">Client-side web APIs</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_APIs/Introduction\">Introduction to web APIs</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_APIs/Video_and_audio_APIs\">Video and Audio APIs</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_APIs/Drawing_graphics\">Drawing graphics</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_APIs/Client-side_storage\">Client-side storage</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_APIs/Third_party_APIs\">Third-party APIs</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Async_JS\">Asynchronous JavaScript</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Async_JS/Introducing\">Introducing asynchronous JavaScript</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Async_JS/Promises\">How to use promises</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Async_JS/Implementing_a_promise-based_API\">How to implement a promise-based API</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Async_JS/Introducing_workers\">Introducing workers</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Async_JS/Sequencing_animations\">Challenge: Sequencing animations</a></li></ol></details></li><li class=\"toggle\"><details open=\"\"><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms\">Web forms</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Your_first_form\">Your first form</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/How_to_structure_a_web_form\">How to structure a web form</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Basic_native_form_controls\">Basic native form controls</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/HTML5_input_types\">The HTML5 input types</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Other_form_controls\">Other form controls</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Styling_web_forms\">Styling web forms</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Advanced_form_styling\">Advanced form styling</a></li><li><em><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/UI_pseudo-classes\" aria-current=\"page\">UI pseudo-classes</a></em></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation\">Client-side form validation</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Forms/Sending_and_retrieving_form_data\">Sending form data</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_tools\">Understanding client-side tools</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_tools/Overview\">Client-side tooling overview</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_tools/Package_management\">Package management basics</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_tools/Introducing_complete_toolchain\">Introducing a complete toolchain</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Client-side_tools/Deployment\">Deploying our app</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side\">Server-side websites</a></summary><ol><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/First_steps\">Server-side first steps</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/First_steps/Introduction\">Introduction to the server side</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/First_steps/Client-Server_overview\">Client-Server Overview</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/First_steps/Web_frameworks\">Server-side web frameworks</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/First_steps/Website_security\">Website security</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django\">Django web framework (Python)</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Introduction\">Django introduction</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/development_environment\">Setting up a Django development environment</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Tutorial_local_library_website\">Django Tutorial: The Local Library website</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/skeleton_website\">Django Tutorial Part 2: Creating a skeleton website</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Models\">Django Tutorial Part 3: Using models</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Admin_site\">Django Tutorial Part 4: Django admin site</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Home_page\">Django Tutorial Part 5: Creating our home page</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Generic_views\">Django Tutorial Part 6: Generic list and detail views</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Sessions\">Django Tutorial Part 7: Sessions framework</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Authentication\">Django Tutorial Part 8: User authentication and permissions</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Forms\">Django Tutorial Part 9: Working with forms</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Testing\">Django Tutorial Part 10: Testing a Django web application</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/Deployment\">Django Tutorial Part 11: Deploying Django to production</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/web_application_security\">Django web application security</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Django/django_assessment_blog\">Assessment: DIY Django mini blog</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs\">Express web framework (Node.js)</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/Introduction\">Express/Node introduction</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/development_environment\">Setting up a Node development environment</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/Tutorial_local_library_website\">Express Tutorial: The Local Library website</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/skeleton_website\">Express Tutorial Part 2: Creating a skeleton website</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/mongoose\">Express Tutorial Part 3: Using a Database (with Mongoose)</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/routes\">Express Tutorial Part 4: Routes and controllers</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/Displaying_data\">Express Tutorial Part 5: Displaying library data</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/forms\">Express Tutorial Part 6: Working with forms</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Server-side/Express_Nodejs/deployment\">Express Tutorial Part 7: Deploying to production</a></li></ol></details></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance\">Web performance</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance/why_web_performance\">The \"why\" of web performance</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance/What_is_web_performance\">What is web performance?</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance/Perceived_performance\">Perceived performance</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance/Measuring_performance\">Measuring performance</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance/Multimedia\">Multimedia: Images</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance/video\">Multimedia: video</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance/JavaScript\">JavaScript performance optimization</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance/HTML\">HTML performance optimization</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance/CSS\">CSS performance optimization</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Performance/business_case_for_performance\">The business case for web performance</a></li></ol></details></li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Extensions/Testing\">Testing</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Testing/Introduction\">Introduction to cross-browser testing</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Testing/Testing_strategies\">Strategies for carrying out testing</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Testing/HTML_and_CSS\">Handling common HTML and CSS problems</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Testing/Feature_detection\">Implementing feature detection</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Testing/Automated_testing\">Introduction to automated testing</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Testing/Your_own_automation_environment\">Setting up your own test automation environment</a></li></ol></details></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Transform_animate\">Transform and animate CSS</a></li><li><a href=\"/en-US/docs/Learn_web_development/Extensions/Security_privacy\">Security and privacy</a></li><li class=\"section\">Further resources</li><li class=\"toggle\"><details><summary><a href=\"/en-US/docs/Learn_web_development/Howto\">How to solve common problems</a></summary><ol><li><a href=\"/en-US/docs/Learn_web_development/Howto/Solve_HTML_problems\">Solve common HTML problems</a></li><li><a href=\"/en-US/docs/Learn_web_development/Howto/Solve_CSS_problems\">Solve common CSS problems</a></li><li><a href=\"/en-US/docs/Learn_web_development/Howto/Solve_JavaScript_problems\">Solve common JavaScript problems</a></li><li><a href=\"/en-US/docs/Learn_web_development/Howto/Web_mechanics\">Web mechanics</a></li><li><a href=\"/en-US/docs/Learn_web_development/Howto/Tools_and_setup\">Tools and setup</a></li><li><a href=\"/en-US/docs/Learn_web_development/Howto/Design_and_accessibility\">Design and accessibility</a></li></ol></details></li><li><a href=\"/en-US/docs/Learn_web_development/About\">About</a></li><li><a href=\"/en-US/docs/Learn_web_development/Educators\">Resources for educators</a></li><li><a href=\"/en-US/docs/Learn_web_development/Changelog\">Changelog</a></li></ol>","source":{"folder":"en-us/learn_web_development/extensions/forms/ui_pseudo-classes","github_url":"https://github.com/mdn/content/blob/main/files/en-us/learn_web_development/extensions/forms/ui_pseudo-classes/index.md","last_commit_url":"https://github.com/mdn/content/commit/f6844f5e30882a6a4843da9b026bc0166ade9c41","filename":"index.md"},"summary":"In the previous articles, we covered the styling of various form controls in a general manner. This included some usage of pseudo-classes, for example, using :checked to target a checkbox only when it is selected. In this article, we explore the different UI pseudo-classes available for styling forms in different states.","title":"UI pseudo-classes","toc":[{"text":"What pseudo-classes do we have available?","id":"what_pseudo-classes_do_we_have_available"},{"text":"Styling inputs based on whether they are required or not","id":"styling_inputs_based_on_whether_they_are_required_or_not"},{"text":"Using generated content with pseudo-classes","id":"using_generated_content_with_pseudo-classes"},{"text":"Styling controls based on whether their data is valid","id":"styling_controls_based_on_whether_their_data_is_valid"},{"text":"Styling enabled and disabled inputs, and read-only and read-write","id":"styling_enabled_and_disabled_inputs_and_read-only_and_read-write"},{"text":"Radio and checkbox states — checked, default, indeterminate","id":"radio_and_checkbox_states_—_checked_default_indeterminate"},{"text":"More pseudo-classes","id":"more_pseudo-classes"},{"text":"Test your skills!","id":"test_your_skills!"},{"text":"Summary","id":"summary"}],"pageType":"learn-module-chapter"}}</script></body></html>