HTML preprocessors can make writing HTML more powerful or convenient. For instance, Markdown is designed to be easier to write and read for text documents and you could write a loop in Pug.
In CodePen, whatever you write in the HTML editor is what goes within the <body>
tags in a basic HTML5 template. So you don't have access to higher-up elements like the <html>
tag. If you want to add classes there that can affect the whole document, this is the place to do it.
In CodePen, whatever you write in the HTML editor is what goes within the <body>
tags in a basic HTML5 template. If you need things in the <head>
of the document, put that code here.
The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https.
CSS preprocessors help make authoring CSS easier. All of them offer things like variables and mixins to provide convenient abstractions.
It's a common practice to apply CSS to a page that styles elements such that they are consistent across all browsers. We offer two of the most popular choices: normalize.css and a reset. Or, choose Neither and nothing will be applied.
To get the best cross-browser support, it is a common practice to apply vendor prefixes to CSS properties and values that require them to work. For instance -webkit-
or -moz-
.
We offer two popular choices: Autoprefixer (which processes your CSS server-side) and -prefix-free (which applies prefixes via a script, client-side).
Any URLs added here will be added as <link>
s in order, and before the CSS in the editor. You can use the CSS from another Pen by using its URL and the proper URL extension.
You can apply CSS to your Pen from any stylesheet on the web. Just put a URL to it here and we'll apply it, in the order you have them, before the CSS in the Pen itself.
You can also link to another Pen here (use the .css
URL Extension) and we'll pull the CSS from that Pen and include it. If it's using a matching preprocessor, use the appropriate URL Extension and we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
JavaScript preprocessors can help make authoring JavaScript easier and more convenient.
Babel includes JSX processing.
Any URL's added here will be added as <script>
s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.
You can apply a script from anywhere on the web to your Pen. Just put a URL to it here and we'll add it, in the order you have them, before the JavaScript in the Pen itself.
If the script you link to has the file extension of a preprocessor, we'll attempt to process it before applying.
You can also link to another Pen here, and we'll pull the JavaScript from that Pen and include it. If it's using a matching preprocessor, we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
Search for and use JavaScript packages from npm here. By selecting a package, an import
statement will be added to the top of the JavaScript editor for this package.
Using packages here is powered by esm.sh, which makes packages from npm not only available on a CDN, but prepares them for native JavaScript ESM usage.
All packages are different, so refer to their docs for how they work.
If you're using React / ReactDOM, make sure to turn on Babel for the JSX processing.
If active, Pens will autosave every 30 seconds after being saved once.
If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.
If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.
Visit your global Editor Settings.
<h1>A Button with an SVG Icon</h1>
<p>The following buttons are examples on how to make a button fully accessible.</p>
<h2>An inaccessible Button – Bad Example</h2>
<p>The first example shows an <em>inaccessible</em> button and should <strong>not be used</strong>! The button misses any textual explanation on what it is going to do on activation and the icon alone is not helpful for people without sight and also for those, who will not recognize its meaning.</p>
<button type="button">
<svg viewBox="0 0 10 10"
height="10"
width="10"
role="img"
class="svg-icon"
focusable="false">
<path d="m1 7h8v2h-8zm0-3h8v2h-8zm0-3h8v2h-8z"/>
</svg>
</button>
<h2>An accessible Button – Good Example</h2>
<p>Here we provide non-sighted users with a textual explanation in form of a title text inside the SVG. This text will be available to assistive technology and in Firefox, users with sight can hover over the button to see a tooltip with the text inside.</p>
<button type="button">
<svg class="svg-icon"
height="10"
width="10"
viewBox="0 0 10 10"
aria-labelledby="button-label"
focusable="false">
<title id="button-label">Menu</title>
<path d="m1 7h8v2h-8zm0-3h8v2h-8zm0-3h8v2h-8z"/>
</svg>
</button>
<h2>An accessible Button – Good Example</h2>
<p>In this example we moved the text from the SVG to a visually hidden span element inside the button. This will also be available to assistive technology, just like above, and invisible to sighted users.</p>
<button type="button">
<svg class="svg-icon"
role="img"
height="10"
width="10"
viewBox="0 0 10 10"
aria-hidden="true"
focusable="false">
<path d="m1 7h8v2h-8zm0-3h8v2h-8zm0-3h8v2h-8z"/>
</svg>
<span class="visually-hidden">
Menu
</span>
</button>
<h2>An accessible Button – Ideal Example</h2>
<p>In this last example the text is not only accessible to assistive technology but also displayed next to the icon. Thereby we ensure that sighted users not being able to recognize the icon to understand the purpose of the button.</p>
<button type="button">
Menu
<svg class="svg-icon"
role="img"
height="10"
width="10"
viewBox="0 0 10 10"
aria-hidden="true"
focusable="false">
<path d="m1 7h8v2h-8zm0-3h8v2h-8zm0-3h8v2h-8z"/>
</svg>
</button>
/**
Note that all these styles are just examplatory.
**/
body {
font-family: sans-serif;
line-height: 1.5;
text-align: center;
box-sizing: border-box;
margin: 2em auto;
max-width: 35em;
color: #2b2b2b;
background: #fafafa;
* {
box-sizing: border-box;
}
}
h2 {
margin: 1.5em 0 .5em;
}
p {
font-size: 1.125em;
margin: 0 0 .5em;
+ p {
margin-top: 1.5em;
}
}
button {
font-size: 1.25em;
font-weight: bold;
line-height: 1;
text-transform: uppercase;
position: relative;
border: .1875em solid;
padding: 1em;
color: rebeccapurple;
background: transparent;
border-radius: .125em;
transition: background .3s;
&:hover,
&:focus {
color: white;
background: rebeccapurple;
border-color: rebeccapurple;
}
&:active {
top: .08em;
}
}
.svg-icon {
/* Place the icon on the text baseline. */
position: relative;
top: .125em;
/* Prevent the icon from shrinking inside a flex container. */
flex-shrink: 0;
/* Scale the icon to match the font-size of the parent element. */
height: 1em;
width: 1em;
/* Let the icon take whatever color the parent has. */
fill: currentColor;
/*
* If the icon is used on a link, which has a color transition,
* we can also use a transition on the fill value.
*/
transition: fill .3s;
}
/* Helper Class to hide text visually but keep it accessible for screen reader or other assistive software. */
.visually-hidden {
// Move the text out of the flow of the container.
position: absolute;
// Reduce its height and width to just one pixel.
height: 1px;
width: 1px;
// Hide any overflowing elements or text.
overflow: hidden;
// Clip the box to zero pixels.
clip: rect(0, 0, 0, 0);
// Text won't wrap to a second line.
white-space: nowrap;
}
Also see: Tab Triggers