Skip to content
Home/Resources/Software Development/Frontend developer roadmap
Roadmap · Software Development

Frontend Developer Roadmap: From HTML and CSS to React, TypeScript, Accessibility and Testing

By Younus FardeenUpdated 11 Nov 20267 min read
Short answer

A frontend developer builds the part of an app that runs in the browser. Learn semantic HTML and CSS layout, then JavaScript, then React and Next.js with TypeScript. Add accessibility, performance and testing early, because they separate working screens from good ones. Build three interfaces, deploy them and check each with a keyboard and Lighthouse.

This page is for students and career switchers who want to build what people see and touch in the browser. Resource links were opened on 11 November 2026, and the performance thresholds come from Google's web.dev.

The first four stages are the same in every frontend job. The last stage, quality, is where AI-generated interfaces most often fall short and where a junior can stand out.

  1. 1
    HTMLsemantic structure, forms
  2. 2
    CSSflexbox, grid, responsive
  3. 3
    JavaScriptDOM, async, modules
  4. 4
    ToolingGit, npm, Vite
  5. 5
    Reactcomponents and state
  6. 6
    TypeScripttypes for props and data
  7. 7
    Next.jsrouting and data fetching
  8. 8
    Qualitya11y, speed, tests
Eight frontend stages. Quality is a stage of its own, not an afterthought.

The eight stages

  1. HTML. Headings, lists, links, images, tables and forms with the right elements. Done when your page makes sense with CSS switched off.
  2. CSS. The box model, flexbox, grid, media queries and custom properties. Done when a layout survives a 320 pixel phone and a wide monitor.
  3. JavaScript. Functions, closures, array methods, the DOM, events, fetch, promises and async and await. Build apps with no framework first.
  4. Tooling. Git, npm, a bundler such as Vite and your browser's developer tools. Learn to read a stack trace and the network tab.
  5. React. Components, props, state, effects and lists. Build a few apps that fetch and change data.
  6. TypeScript. Types for props, API responses and events. It turns many runtime surprises into editor warnings.
  7. Next.js. File-based routing, server and client components, data fetching and deployment. See the full stack developer roadmap for the backend half.
  8. Quality. Accessibility, performance and tests, covered below.

Masai's 10 creative HTML and CSS projects is a good first practice list, and its frontend vs backend comparison explains where the roles split.

Skills, why they matter and a free place to start

SkillWhy it mattersFree first resource
Semantic HTML and formsScreen readers, search engines and browsers read structureMDN Learn web development
CSS layoutResponsive screens without hacksMDN CSS layout
JavaScriptAll browser behaviour runs on itjavascript.info
ReactThe common way to build stateful interfacesreact.dev Learn
TypeScriptCatches type errors before users doTypeScript Handbook
Next.jsRouting, data loading and rendering in one frameworkNext.js Learn
AccessibilityKeyboard and screen reader users must be able to finish tasksweb.dev Learn Accessibility and the WCAG 2.2 quick reference
PerformanceSlow pages lose usersCore Web Vitals on web.dev and Lighthouse
TestingProtects behaviour while you refactorVitest, Testing Library and Playwright

The quality stage: accessibility, performance and tests

Google's web.dev defines three Core Web Vitals and treats a page as passing when the 75th percentile of visits meets all three: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less. Interaction to Next Paint replaced First Input Delay as a stable metric in 2024.

For accessibility, start with what you can test yourself: use only the keyboard, check focus order and visible focus, give every input a label and every image meaningful alt text, and test colour contrast. The W3C's WCAG 2.2 quick reference lists the success criteria to test against.

For tests, cover logic with unit tests, components with Testing Library and the main user flow with one Playwright test. Keep them few and reliable.

What to build

Hiring and pay: what the data shows as of 11 November 2026

Pay: Levels.fyi had no India page for front-end focus when we read it. For all software engineers in India it lists a median of ₹30.5 lakh from 21,353 self-reported salaries (updated 10 November 2026), and a 25th to 75th percentile range of ₹17.6 lakh to ₹49.4 lakh. First-job offers are lower.

2027 outlook

PrepNPlaced's October 2026 count of 18,752 tech postings has no frontend row; Software Engineer is the largest (20.3%) and only 4.3% of postings were entry or junior. Naukri's September 2026 JobSpeak shows fresher hiring up 1% and IT and software services down 4%.

AI tools generate interfaces fast, and the 2026 Stack Overflow survey found coding assistants and agents are the most common AI use (66%). That moves the junior's value towards what generated screens often miss: keyboard access, contrast, layout shift, state bugs and tests. Show them in your projects. We found no Indian data on how many frontend jobs AI has removed, so we do not claim a number.

Interview preparation notes

  • JavaScript questions come first: closures, this, promises and the event loop. Predict the output of the snippet below before you run it.
  • React questions cover state versus props, effects and cleanup, keys in lists, controlled inputs and why a component re-renders.
  • CSS rounds ask flexbox versus grid, specificity and how you would make a card layout responsive.
  • Many rounds include building a small UI in under an hour. Practise with a timer and review data structures and algorithms for the online test.
console.log('1 sync');
setTimeout(() => console.log('4 timeout'), 0);
Promise.resolve().then(() => console.log('3 promise'));
console.log('2 sync');

The output is 1, 2, 3, 4. Synchronous code runs first, then promise callbacks (microtasks), then timers, even with a zero delay. Being able to say why is the point of the question.

Frequently asked questions

What does a frontend developer do?

A frontend developer builds the part of a website or app that runs in the browser: layout, styling, interaction, data loading and state. They also care about accessibility, speed and testing, and work with designers and backend developers.

What should I learn first for frontend development?

Learn HTML first, then CSS layout, then JavaScript, in that order. Skip frameworks until you can build a small interactive page without one. Then learn React, followed by TypeScript and Next.js. Test every project on a real phone and with a keyboard so accessibility becomes a habit.

Is frontend development hard to learn?

The basics are approachable, and the hard part is breadth: layout, JavaScript, state, accessibility and performance all matter. Learn them through small projects instead of long courses, and test each one on a real phone and with a keyboard. Most beginners stall when they jump to frameworks too early.

Do I need to learn TypeScript?

You can start React without it, but add it early. Editor warnings for type errors save debugging time, and many teams use TypeScript. Learn JavaScript properly first, then convert a project you already built to TypeScript so you see exactly what the types catch.

What are the Core Web Vitals?

Three page-experience metrics from Google: Largest Contentful Paint (loading, within 2.5 seconds), Interaction to Next Paint (responsiveness, 200 milliseconds or less) and Cumulative Layout Shift (visual stability, 0.1 or less). A page passes when the 75th percentile of visits meets all three targets.

Will AI replace frontend developers?

No source we read shows that. AI tools generate interfaces quickly, but accessibility, performance, state handling and testing still need a person who can check the result. Entry-level openings are tight, with 4.3% of one October 2026 set of tech postings tagged entry or junior, so show quality in your projects.

Frontend or backend: which should a beginner choose?

Neither is better. Frontend gives visible results sooner, while backend teaches data modelling and system design. Spend two weeks on a small project in each and notice which problems you enjoy. The backend and full stack roadmaps on this site cover the other paths.

Sources checked

Learn this with mentors

Programmes for builders and engineers with admissions open: live classes, mentors and project work.

Continue learning

Roadmap

Full stack developer roadmap

Eight stages from HTML to deployed apps, each with a free resource

Open →
Roadmap

Backend developer roadmap

Pick a stack, then SQL, APIs, auth, queues and Docker, in order

Open →
Project guide · JavaScript

JavaScript practice projects

19 small test-first builds to get fluent.

Open guide →19 ideas