A solid UI/UX course in 2026 takes 4–9 months part-time and covers six things in order: usability fundamentals, user research, wireframing and information architecture, high-fidelity UI with design systems, accessibility, and usability testing. It ends with a portfolio of two or three case studies. The tool you must know is Figma, with FigJam or Miro for workshops, Maze or Lookback for testing, and Lighthouse or Stark for accessibility checks. Typical jobs afterwards are UI/UX designer, product designer, UX researcher or content designer. In the US, the Bureau of Labor Statistics puts the median pay for web and digital interface designers at $104,000 (May 2025) and projects 6% employment growth from 2025 to 2035. Entry-level roles are competitive, and your portfolio decides most hiring outcomes.

What does the roadmap look like, stage by stage?

Stage What you learn What you produce
1. Foundations Usability heuristics, cognitive load, UI vs UX, common patterns A heuristic review of an existing app
2. Research Stakeholder and user interviews, Jobs To Be Done, task analysis, journey mapping An interview synthesis and a journey map
3. Structure Information architecture, user flows, low-fidelity wireframes A clickable wireframe prototype
4. Visual UI Grids, type scales, colour, hierarchy, microinteractions Responsive screens for web and mobile
5. Design systems Components, variants, design tokens, documentation A small component library
6. Content and accessibility Microcopy, error and empty states, WCAG success criteria An accessibility audit and rewritten copy
7. Testing Moderated and unmoderated tests, A/B tests, iteration A test plan, findings and a revised design
8. Portfolio Case-study structure, presenting your decisions 2–3 case studies

Testing does not need a big budget. Nielsen Norman Group’s analysis shows that a round of about five users finds most of the usability problems. Several small rounds beat one large round, and a good course makes you run at least two.

Which tools will you actually use?

  • Design and prototyping: Figma is the industry default. In May 2025 Figma added Figma Make, which turns prompts into prototypes, and Figma Sites, which publishes websites from the canvas (Config 2025 announcements). Sketch is still used in some Mac-only teams.
  • Workshops: FigJam and Miro.
  • Testing: Maze (unmoderated), Lookback or UserTesting (moderated), Optimal Workshop (card sorting and tree tests), Hotjar (heatmaps).
  • Accessibility: Stark, Chrome Lighthouse and manual screen-reader checks with VoiceOver or NVDA.
  • AI: Figma’s built-in AI and Google Stitch for generating first-draft layouts. Use them to explore ideas quickly, not to make final decisions.

What has changed since older roadmaps were written?

  • Adobe XD is no longer worth learning. Adobe says XD is in maintenance mode, with bug and security fixes but no new features. Drop any course that still teaches it as a core tool.
  • Galileo AI is now Stitch. Google bought it in May 2025 and relaunched it as Stitch, so syllabi that list “Galileo AI” are out of date.
  • The accessibility standard is WCAG 2.2. The current version is WCAG 2.2. It adds criteria such as minimum target size and accessible authentication. Courses still teaching only 2.0 are behind.
  • Accessibility is now a legal requirement in more places. US state and local governments must meet WCAG 2.1 AA under the Department of Justice’s ADA Title II rule. After a 2026 extension, the deadlines are April 2027 for large entities and April 2028 for smaller ones. The European Accessibility Act has applied to many consumer digital services since June 2025. Employers increasingly expect juniors to audit accessibility, not only know the word.

What goes wrong when course work meets real production?

We commission interface work for landing pages, interactive video and product launch campaigns. New designers tend to fail on the same three points:

  • Missing states. Polished happy-path screens arrive without loading, error, empty or long-text states. A developer then makes those decisions, which usually adds a revision round.
  • Motion with no spec. A microinteraction that looks good in a Figma prototype often can’t be built as shown. Designers who can hand over timing and easing values, or export to Lottie or Rive, save days of back-and-forth.
  • Ignoring real content. Layouts built on placeholder text break when real headlines, translations or captions arrive. Design with real copy from the wireframe stage.

A course that grades only finished screens won’t teach any of this. Look for one that includes a developer handoff project.

Which jobs can you get, and what do they pay?

  • UI/UX designer: the most common entry role. Covers flows, wireframes and UI.
  • Product designer: UX and UI plus business metrics and product decisions. Usually a step up after 2–3 years.
  • UX researcher: interviews, testing and synthesis. Often favours people with psychology or social-science backgrounds.
  • Content designer / UX writer: interface language, microcopy and content structure.
  • Design systems designer: component libraries and tokens. Common in larger organisations.

Pay depends on location, company size and whether the role is “product designer” (higher) or “UI designer” (lower). The BLS median of $104,000 is a mid-career benchmark for the US, not a starting salary. Juniors outside major tech hubs, or outside the US, usually start well below it.

How do you choose a course?

  • Projects with real users: you should interview and test with people outside your cohort.
  • Current tools: Figma with variables and Dev Mode, WCAG 2.2, no Adobe XD.
  • Feedback from working designers: ask how many portfolio reviews are included and who gives them.
  • Honest outcome data: ask for placement rates with the time window and the definition of “placed”. If a provider won’t share this, treat that as an answer.
  • Cost against support: self-paced certificates cost a monthly subscription. Mentored bootcamps cost thousands, and most of what you pay for is the feedback.

Before you pay for anything, spend two weeks on free Figma tutorials and run a heuristic review of an app you use every day. If you enjoyed finding the problems more than drawing the screens, choose a research-heavy course. If you enjoyed the screens, choose one strong on UI and design systems. Either way, judge the course by the two or three case studies it will help you build, because that is what employers hire from.

Case Studies

Clients we worked with.