Careers & Jobs
Web Design Careers: Building a Portfolio and Comparing Training
Compare web design training and build a portfolio that explains user tasks, responsive layouts, accessibility checks and your own design decisions.

At a glance
Compare the actual duties behind web design job titles.
Build a small brief with clear content and mobile layouts.
Show revisions, accessibility checks and your own contribution.
On this page
- Understand what the employer means by web design
- Compare training through its practical work
- Choose a small, believable portfolio brief
- Consider access and different screen sizes early
- Use feedback to explain your decisions
- Prepare the portfolio for applications
- Common questions
- Sources and further reading
Web designers help people find information and complete tasks through a website. The work involves layout, navigation, typography, images and interaction, but a convincing design does more than look attractive in a screenshot. It should respond to a real need and remain understandable across different devices and ways of using the web.
This guide explores UK career routes and a practical first portfolio project. Job titles overlap: one employer may separate design, research and development, while another expects a broader mix. Check the actual duties and support before choosing a course or applying for a role.
Understand what the employer means by web design
Read several entry-level vacancies and compare their requirements. Some emphasise visual design and prototypes, others content management, HTML and CSS, or maintaining an existing site. A role may also involve working with clients, interpreting feedback and coordinating with developers.
Our guide to reading job advertisements helps distinguish essential skills from a broad wish list. Record repeated requirements and the type of work you would produce. Do not assume every designer must be an expert in every tool mentioned across unrelated adverts.
Ask how work is reviewed and who makes decisions about content, accessibility and technical implementation. A junior designer should understand the wider process, but the responsibilities and supervision available can differ substantially between a small agency and a large in-house team.
Compare training through its practical work
The National Careers Service describes university, college, apprenticeship and work-based routes into web design. Compare the exact curriculum and assessment rather than relying on a course title. Look for opportunities to develop ideas, receive criticism and improve a design through several iterations. (National Careers Service: web designer)
Ask whether you will work on realistic briefs, design for mobile screens and explain your decisions. Check how accessibility, content and basic technical constraints are covered. A course focused mainly on operating one design tool may leave other important aspects of the job underdeveloped.
For an apprenticeship or assistant role, examine the actual job and learning support together. For a short private course, clarify the full cost, feedback and any employment claims. A portfolio review service or access to vacancies is different from a guaranteed job.
| Area | What to investigate | Useful evidence |
|---|---|---|
| Design process | How ideas are developed and revised | Early sketches and reasons for changes |
| User tasks | How the design supports a practical purpose | A clear brief and task walkthrough |
| Responsive layout | How content works at different widths | Mobile and desktop examples |
| Accessibility | How barriers are identified and addressed | Documented checks and remaining limitations |
| Feedback | Who reviews the work and how often | Specific revisions based on evidence |
| Delivery | What is handed to a developer or client | Organised files and clear component notes |
Choose a small, believable portfolio brief
Create a fictional project with a defined audience and purpose. For example, a local walking group might need visitors to find a suitable walk, understand the meeting point and see what to bring. Use invented details and clearly identify the project as a concept rather than implying that a real organisation commissioned it.
Write the essential content before concentrating on decoration. Decide which information a first-time visitor needs and which action matters most. Sketch a simple structure and test whether the key task is understandable without explaining the page aloud.
Our guide to digital portfolios helps present the result as a case study. Show the brief, your role, a few decisions and the final outcome. A reviewer should be able to follow why the design changed, not only see a polished final image.
Consider access and different screen sizes early
W3C’s design guidance highlights clear navigation, identifiable controls, sufficient contrast and ways to communicate information without relying only on colour. Use those principles while developing the layout rather than treating accessibility as a final visual check. (W3C WAI: designing for web accessibility)
Think about long headings, enlarged text, keyboard focus and forms that need clear labels and feedback. A static mockup cannot prove that the implemented site works with assistive technology. State what you checked and what would still need testing during development.
Compare a narrow-screen version with the desktop layout. Decide how navigation, images and information order should adapt. Avoid shrinking everything until it fits; the goal is a readable, usable arrangement that preserves the important content and actions.
Use feedback to explain your decisions
Ask a few people to attempt a specific task in the prototype, such as finding the next beginner-friendly walk. Observe where they hesitate and ask neutral questions. A small informal exercise can reveal problems, but do not present it as representative research proving that all users will succeed.
Record the issue, the evidence and the change you made. For example, if participants overlook the meeting information, consider its label, location and hierarchy. Explain why the revision addresses the problem rather than simply saying that the second version looks cleaner.
Keep feedback proportionate to the project’s scope. You do not need a lengthy research report for a small concept, but you should distinguish a personal aesthetic preference from an observed difficulty with the task. That distinction helps a reviewer understand your judgement.
Prepare the portfolio for applications
Choose a few examples you can discuss well. State whether you designed, coded, wrote content or collaborated, and credit templates, assets and other contributors appropriately. Do not imply that a ready-made component library or generated image was entirely your own creation.
If you build a working site, check links, mobile layout and basic interaction before sharing it. If the work remains a prototype, label it clearly. Use images and content you have permission to publish, and remove private information from client or workplace examples unless sharing is authorised.
Our guide to interviews with limited experience can help you prepare a short explanation of the project. Discuss one constraint, one revision and what you would improve next. Honest reasoning about a modest brief is useful evidence of how you work.
- Define the task
Choose an audience, useful content and a clear purpose.
- Design and check
Consider mobile layout, accessibility and practical feedback.
- Explain the work
Show your contribution, revisions and remaining limitations.
Common questions
Do web designers need to code?
Requirements vary. Some roles focus on design and handover, while others include implementation or site maintenance. Basic technical understanding can improve collaboration, but check the vacancy rather than assuming one universal requirement. Choose learning that matches the work you want to do and be clear about your current skills.
Do I need a degree to enter web design?
There are several routes, including college, higher education, apprenticeships and relevant assistant work. Employers and courses set their own requirements. Investigate realistic vacancies and the quality of practical learning available, rather than deciding solely from the qualification level or assuming a portfolio replaces every formal entry condition.
Can my portfolio use fictional projects?
Yes, if they are clearly labelled and demonstrate a believable process. Define the audience and task, use appropriate invented content and explain your decisions. Do not suggest that a real organisation hired you or that a concept produced measured business results when it was a personal learning exercise.
How many design tools should I learn?
Start with tools that let you complete and explain useful work for the roles you are considering. Learn the underlying design process as well as the interface. A long list of software names is less helpful than evidence that you can organise content, respond to feedback and deliver a clear design.
Does a good screenshot prove the site is accessible?
No. A screenshot can show some visual choices, but it cannot establish how the implemented site behaves with a keyboard, enlarged text or assistive technology. Explain the checks completed and the tests still needed. Avoid claiming full accessibility compliance from a prototype or a single automated result.
Can I redesign a real organisation’s website for practice?
You can make a clearly labelled independent concept, while respecting rights in any content or assets used. Do not imply endorsement, a client relationship or measured results. A fictional brief may be simpler when you want to focus on design reasoning without relying on a real organisation’s brand or materials.
What should I include in a case study?
Explain the purpose, audience, your role, important constraints and a few meaningful decisions. Show how feedback or checking changed the work and identify limitations. Keep it focused enough for a recruiter to understand quickly, with additional detail available if they want to discuss the project in an interview.
How can I improve a portfolio after feedback?
Look for specific problems that affect clarity, relevance or usability. Decide which changes serve the brief and explain why you made them. You do not need to follow every aesthetic preference, but you should be able to distinguish a reasoned decision from simply dismissing feedback you do not like.
Sources and further reading
- National Careers Service: web designer — career routes and portfolio context.
- W3C WAI: designing for web accessibility — practical design considerations and further guidance.





