roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Go into frontend interviews able to explain the markup you write and why it is right. Covers semantic structure, forms and media, metadata and SEO, ARIA and accessibility practice, and safe embedding.
203 of 203 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 203 new. 0 cut, outside your plan.
Questions on HTML are folded into other rounds of a frontend loop: the fundamentals conversation, a markup review that puts a flawed snippet in front of you, and the debrief on a take-home, where reviewers often tab through the page before they open the JavaScript. Design system and public-facing product teams give it the most time.
The questions are about the behavior native elements bring for free. What does a div with a click handler lose that a button has: a place in the tab order, activation from the keyboard, a role a screen reader announces? Why does a button inside a form submit it when nobody asked it to? Why does loading="lazy" on the hero image slow the page it was meant to speed up?
Level changes where the follow-up goes more than the question. Shown the clickable div, a junior is expected to name its replacement; a senior is asked about a component library full of them: how to find them all, how to stop new ones, and what an automated checker cannot catch. At that end HTML turns into policy, such as moving a site full of inline scripts and third-party tags onto a Content Security Policy without breaking checkout.
The plan opens on the markup itself and follows a file the way the browser meets it. Document structure leads because the parser's recovery from bad nesting decides what tree the later sections work on, and where a script tag sits decides when that tree is ready. Semantic elements and forms come next as the elements with built-in behavior, so that ARIA arrives as what you add when native elements run out, not a replacement for them. The hub closes on what reaches beyond the visible page: the head as crawlers and link previews read it, and embedded media and frames, where page weight and third-party content enter.
The accessibility module is not written for HTML alone, which is why it follows the hub: once you have chosen your elements, it supplies the standard that judges them, WCAG, and then the result as assistive technology receives it, from the role, name and state each control exposes to what a screen reader makes of the page. It ends on audits, where senior conversations tend to settle.
Content Security Policy closes the plan, after embedding, because frames and third-party scripts are what a policy restrains. It treats the policy as a rollout rather than a header to paste: nonces or hashes in place of 'unsafe-inline', a report-only phase before enforcement, and the inline onclick attributes in older markup that block the switch.
The plan is short enough to read whole at any level, so the choice is which questions to drill. A junior posting can drop the upper bands of level, whose questions concern audits and policy rollouts nobody will ask you to own yet. A senior one should keep every band, because the markup review that opens the round is built from junior questions. A backend developer moving toward full stack should begin with forms, where markup meets a server they already know: which `method` and `enctype` produce which request, and why a disabled field never arrives. If accessibility is the job, switch study order to by topics, give the second module the same depth as the first, and answer its questions with a screen reader running on a page you built. The plan stops at markup and the policy around it. Layout, the cascade and responsive design belong to the [CSS roadmap](/roadmaps/css); the [Frontend Developer roadmap](/roadmaps/frontend) sets these questions among the JavaScript and framework rounds of a full loop.
The plan is short enough to read whole at any level, so the choice is which questions to drill. A junior posting can drop the upper bands of level, whose questions concern audits and policy rollouts nobody will ask you to own yet. A senior one should keep every band, because the markup review that opens the round is built from junior questions.
A backend developer moving toward full stack should begin with forms, where markup meets a server they already know: which method and enctype produce which request, and why a disabled field never arrives. If accessibility is the job, switch study order to by topics, give the second module the same depth as the first, and answer its questions with a screen reader running on a page you built.
The plan stops at markup and the policy around it. Layout, the cascade and responsive design belong to the CSS roadmap; the Frontend Developer roadmap sets these questions among the JavaScript and framework rounds of a full loop.