HTML Custom Element Labels and Accessibility Semantics

Small interactions can make a webpage easier to use: opening a tip, changing a setting, or reusing an interface component.

What You Need to Know

Custom components still need clear labels, names, and states. Use native controls within the component when possible, and test how its name appears in the accessibility tree.

Try the Example

Take a look at the example. We’ll explain the important lines right below it.

<form action="/save" method="post">
    <label for="rating">Rating</label>
    <input id="rating" name="rating" type="number" min="1" max="5" required>
    <button type="submit">Save</button>
</form>

Let’s Read the Code

<form>: The form groups controls and identifies where submitted data goes.
<label>: The label tells people what the input is for. A matching for/id pair makes the label clickable.
for: For connects a label or output with a control by ID.
id: An id uniquely identifies an element on this page.

Read the named elements and attributes together. They explain how the browser connects this feature to the rest of the page.

What Happens in the Browser?

When this example includes JavaScript, it supplies behavior that ordinary HTML does not automatically provide. Always think about a fallback.

Start with native behavior. Details, dialog, and popover each solve a different interface problem. Choose the simplest control that actually matches what a visitor wants to do, then test focus and dismissal as well as appearance.

Your Turn

Run this on a local development server if it loads modules or resources. Change the visible text or trigger and check what still works with scripts disabled.

Common Beginner Mistakes

Assuming new HTML syntax works in every browser without testing.
HTML supplies structure; JavaScript is necessary for the scripted behavior in this example. Check keyboard access and focus movement too.

Key Takeaways

Custom components still need clear labels, names, and states.
<form>: The form groups controls and identifies where submitted data goes.
A meaningful HTML element is usually a stronger starting point than adding an ARIA role to a generic div. Also check what happens using only the keyboard.