Frontend development

Stage 1 · Lesson 4 of 9

Accessible forms

How the web works, HTML and CSS

Forms are where most accessibility failures hurt real people, because a form nobody can fill in is a dead end. Every needs a visible tied to it. Do this with matching for and id attributes, or by wrapping the input inside the label.

Use the right input type (email, tel, number, date) so phones show the right keyboard. Group related radio buttons in a fieldset, with a legend that names the group. Write error messages in text next to the field, not only as a red border.

Placeholder text is not a label: it disappears when you type and is often too faint to read. Get accessible forms right now, and every framework form you build later starts accessible.

A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock

Resources for this stage

Start with· follow one of these

  • CourseFree
    The Odin Project

    The Odin Project · Beginner

    Foundations course: HTML, CSS and the web built in your own editor, not a sandbox

  • GuideFree
    web.dev

    Google · Intermediate

    Free Learn HTML, Learn CSS and Learn Accessibility courses explain the why behind layout

Practise

  • Real designs to rebuild, which is where CSS layout finally sticks

Keep handy

  • The reference for every HTML element and CSS property, with browser support notes

  • Quick syntax lookups and try it editors when you only need a reminder

Also worth your time

Mark this stage as not done?