Usability, Accessibility, and Breaking Into UX

The previous lessons found the right problem and designed a solution. This closing lesson answers the question that decides whether the work succeeds: does it actually work well for real people? Evaluating and refining the design is the "deliver" end of the double diamond, and it is where the evidence-over-ego philosophy of UX becomes concrete practice.

A UX designer never assumes a design is good because it looks good or because the team likes it. They check, with real users and against known standards, and then improve. This lesson covers the main ways to do that:

• Usability testing: watching real users attempt tasks to find where the design fails.
• Heuristic evaluation: checking a design against established usability principles.
• Accessibility: ensuring the product works for people with disabilities, an ethical duty, often a legal one, and simply good design.
• Design systems: keeping the whole product consistent and coherent as it grows.

It then turns to the practical goal of the whole cursus for a switcher: how to break into UX, building the skills, assembling a portfolio, and landing the role. Evaluation is the fitting place to end, because it embodies what makes UX a discipline rather than decoration: the humility to test your work against reality and the rigor to fix what does not work.

Usability testing is the most direct way to evaluate a design: you give real users real tasks and watch what happens. It is the single most valuable evaluation method in UX, because it shows you the truth that opinions cannot.

How it works in practice:

• Give tasks, not a tour. Ask the user to accomplish something ("send an invoice to a client") rather than showing them around. You want to see them actually try.
• Watch and stay quiet. Observe where they hesitate, get confused, take a wrong path, or fail, without helping or explaining. Their struggle is the data. Biting your tongue while a user flounders is hard and essential.
• Ask them to think aloud. Having users narrate their thoughts ("I'm looking for a button to... where is it?") reveals why they struggle, not just that they do.

A liberating finding from usability research, associated with Jakob Nielsen of the Nielsen Norman Group, is that you do not need many testers. Testing with only about five users typically surfaces the large majority of usability problems, because serious issues trip up almost everyone. This means testing is cheap and fast, no excuse to skip it.

The payoff is humbling and invaluable: you always discover things you were blind to, because you knew how it was "supposed" to work and users did not. Usability testing turns "I think this is clear" into evidence, catches problems while they are cheap to fix, and is the practice that most reliably makes designs genuinely better. Watching just a few users struggle teaches more than weeks of internal debate.

Besides testing with users, designers evaluate a design against established principles, a heuristic evaluation. The most famous set is Jakob Nielsen's 10 usability heuristics, general rules of good interface design that catch many common problems without a full test. You do not need to memorize all ten, but several are worth knowing because they name things you feel constantly as a user:

• Visibility of system status. Always keep users informed about what is happening (loading indicators, confirmations, progress). Users should never wonder whether something worked.
• Match between system and the real world. Speak the users' language and follow real-world conventions, not internal jargon or developer logic.
• User control and freedom. Provide clear exits, undo, and "back", let users escape mistakes without feeling trapped.
• Consistency and standards. Do not make users wonder whether different words or actions mean the same thing; follow platform conventions.
• Error prevention. The best error message is one that never appears, design to prevent mistakes (confirmations, sensible constraints).
• Recognition rather than recall. Show options rather than making users remember information; minimize memory load.
• Help users recognize and recover from errors. Error messages in plain language that say what went wrong and how to fix it.

(The full list also includes flexibility for expert users, aesthetic and minimalist design, and help and documentation.) These heuristics are a practical checklist: an experienced designer can scan an interface against them and spot issues quickly. They complement usability testing, heuristics catch known problems by expert review, while testing catches the surprises only real users reveal. Together they are the two pillars of evaluation.

Accessibility (often abbreviated a11y) means designing products so that people with disabilities can use them, including those with visual, motor, hearing, or cognitive impairments. It is a core professional responsibility in UX, not an optional add-on, for three reasons: it is an ethical duty to not exclude people, it is increasingly a legal requirement, and it simply produces better design for everyone.

The standard reference is the Web Content Accessibility Guidelines (WCAG), published by the W3C. WCAG is organized around four principles, remembered as POUR, content must be:

• Perceivable: people must be able to perceive it, for example, text alternatives for images (so screen readers can describe them), captions for video, and sufficient color contrast.
• Operable: people must be able to operate it, for example, everything usable by keyboard alone (not just a mouse), and no traps.
• Understandable: content and operation must be clear, readable language, predictable behavior, helpful error handling.
• Robust: it must work with assistive technologies like screen readers, which means well-structured, standards-compliant implementation.

WCAG defines conformance levels A, AA, and AAA; most organizations target Level AA as the practical standard.

Many accessibility practices help everyone, not only people with disabilities, a principle called universal design. Good color contrast helps anyone reading on a bright screen outdoors; captions help people in noisy places; keyboard operability helps power users. This is why accessibility is not a constraint on good design but part of it: designing for the full range of human ability makes a product more usable, and more valuable, for all.

As a product grows beyond a few screens, keeping it coherent becomes its own challenge, and the answer is a design system. A design system is a reusable library of standardized components (buttons, form fields, cards, navigation) and rules (color palette, typography, spacing, usage guidelines) that a whole team designs and builds from.

Why this matters, tying back to the consistency principle from Lesson 3:

• Consistency at scale. When every designer and developer uses the same button component and color tokens, the product stays coherent across dozens of screens and multiple people, instead of drifting into a patchwork that feels unreliable.
• Efficiency. Reusing tested components means not redesigning a button for every screen; teams move faster and focus on the actual problem rather than reinventing basics.
• Quality and accessibility baked in. A well-made component can have good usability and accessibility built in once, so every use inherits it, raising the floor across the whole product.

Famous examples include large companies' public design systems, but even small teams benefit from a lightweight one. For a career switcher, the practical point is awareness: modern UX work usually happens within a design system, so understanding what they are and why they exist is part of speaking the language of the field. Design systems are how the consistency that good UX demands is achieved and maintained as a product and team scale, turning a principle into infrastructure.

You now have the full arc: what UX is, research, design, and evaluation. Here is how a career switcher turns that into a job.

Build the skills. Learn the process (this cursus), get hands-on with a tool like Figma, and practice the fundamentals of research, structure, and visual design. Free and paid courses abound, but doing beats watching.

Build a portfolio, the single most important thing. In UX, you are hired on your portfolio far more than your resume or degree. And a strong portfolio shows case studies, not just pretty screens: for each project, tell the story, the problem, your research, your design decisions and why, how you tested and iterated, and the outcome. This demonstrates the thinking employers actually want. Weak portfolios show only final visuals; strong ones show the process.

Get real practice to fill the portfolio:

• Redesign something. Take an app or site with poor UX, research and redesign it, and document your reasoning as a case study.
• Do real or volunteer projects. Design for a small business, a nonprofit, or an open-source project, real constraints make the strongest cases.
• Use your background. Your prior field (writing, research, teaching, support, marketing) is an asset and often a specialization, lean into it.

Speak the language. In your portfolio and interviews, frame everything around users, problems, evidence, and outcomes, exactly the mindset this cursus taught.

UX rewards empathy, curiosity, structured problem-solving, and evidence over ego, transferable strengths you can build deliberately, proven through a portfolio that shows how you think. The role is learnable, the demand is real, and you now have the map from problem to validated product.

Step back and see the entire cursus as one connected craft.

The thread through all of it: UX design is a disciplined, evidence-based process for making products that work for real people. You understand users, define the right problem, design a solution from structure to style, and validate it against real behavior and known standards, looping as you learn. The recurring stance is humility toward evidence: you are not your user, so you research, test, and refine rather than trust your own taste.

That stance is also the answer to the field's biggest misconception. UX is not making things pretty; it is making things work, grounded in understanding people, with visual craft as the layer that expresses a sound structure. The pretty part is real and learnable, but it sits on top of research, structure, and testing.

For a career switcher, the encouraging summary: UX is a learnable discipline built substantially on empathy and structured thinking, skills that transfer from many backgrounds, proven through a portfolio that shows your process. The best next step is to do it: take a product with poor UX, run the whole loop, research, define, design, prototype, test, and write it up as a case study. Do that once, deliberately, and you have not just learned UX, you have started practicing it, and begun the portfolio that gets you hired.

A designed solution is validated by usability testing with a few users and heuristic evaluation, checked for accessibility against WCAG, and kept consistent via a design system; problems loop back to refine the design before it ships.