search
Enter at least two characters without personal information.

    LibraryArticles and FAQs Your projectRequest a quote
    LanguageEN ▾
    Methods and learning

    Web design: responsibilities and practical exercise

    Web design composes pages around content, visual identity and the visitor’s decisions. It organises reading, evidence and actions into reusable layouts. A composition should remain understandable with longer copy, a missing image or a change in available space.

    These sheets describe activities and teaching exercises. They do not constitute job offers, certifying courses or recruitment promises.

    All job descriptions
    Illustration of design and review work on a computer
    AI-generated illustration

    Explore all 28 review cases — A translated heading overflows

    Missions and responsibilities

    Combine visual identity, editorial structure and visitor journeys in page layouts whose information and actions remain understandable.

    Typical activities

    • Design page templates using content actually available.
    • Choose authorised visuals and plan cropping across screens.
    • Define layout variations without unnecessary templates.

    Responsibilities to agree with the team

    Visual design does not replace content approval, image rights or functional checks. Work with editorial owners and developers on complete pages.

    A first piece of work to demonstrate

    Show a homepage and an internal page with long content, mobile navigation and a testable contact journey.

    This is an editorial description of common activities. Job titles and scope vary across teams; it is not a certification framework.

    W3C: organising accessibility responsibilities across a team

    Practice exercise

    Prepare a service page and its mobile version with real texts and authorized media.

    Work on a copy or demo environment. Define the data used and the expected result before you begin. Keep your decisions and the difficulties encountered in order to be able to explain the process.

    1. Identify the main question to which each page answers.
    2. Organize titles, proof and action before decorative details.
    3. Compare rendering with missing image and longer texts.
    4. Transmit visual choices and content constraints to the team.

    Deliverable and checks

    Provide the service page with full copy, authorised media and screen variants. Annotate reading order, reusable elements and cropping rules. Also show the intended layout when the main image is unavailable.

    Ask someone to find the service, an important condition and the contact route in each variant. Check that adaptations retain this information without requiring factual copy to be shortened merely to hide a space problem.

    Prepare website checks

    Risks and collaboration

    An attractive screenshot demonstrates neither the understanding of the offer nor the quality of a course. Check the hierarchy with a real task.

    Collaboration to explore: Design UI.

    Fictional deliverable excerpt : A mock-up specifies heading hierarchy, image treatment and card variants. It describes what happens when a title is long or an image is missing.

    What passes between the roles : Share the visual proposal and the question to check together: mock-up version, target task, constraints and observations. Agree who continues the tests and who decides on changes.

    View the role comparison : Web designer and digital Product designer →

    Employment, trades and training
    An example to examine

    Explain a layout decision

    Fictional teaching material: this excerpt illustrates part of a deliverable. It is not a client reference, a complete specification or evidence of professional qualification.

    Sample excerpt
    Goal: compare two services on a phone.
    Choice: one column, with title, scope, then action.
    Test content: a long title and three exclusions.
    Check: reading without truncated text or hidden actions.
    Review: spacing with the actual content.

    What the author should be able to explain

    1. The rationale connects layout to a specific task.
    2. Test content probes a limit rather than an ideal presentation.
    3. The visual direction must still be checked with the copy and images that will be published.
    Why retain long content in the presentation?

    It reveals whether the composition works with less predictable information. Artificially shortening every title can conceal a problem that will reappear during implementation.

    Assess the quality of the work

    For the exercise, a service page combines an important condition with a dominant visual. Webdesign should help readers find that condition and the appropriate action from a direct link on phones and larger screens. Examine understanding before judging only block balance or photograph size.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Assess the quality of the work
    SkillEvidence to examineFailure to spot
    Decision hierarchyShow the page’s subject, conditions affecting the choice and next action. Describe block order when columns disappear.An image pushes every condition below a consequential action, or equally prominent buttons offer contradictory next steps.
    Media purposeDistinguish informative imagery from decoration, plan cropping and retain useful information in accessible content. Document credit and publication rights.Cropping removes the detail explaining the service, or decisive information exists only as text embedded in an image.
    JourneyThe page works from a direct link and with keyboard navigation.Understanding depends on having seen the homepage.
    Small-screen priorityDescribe content order and what remains essential when columns stack.At 320 CSS pixels, text and actions remain available without page-wide horizontal scrolling.

    A focused next step

    Ask a reader to identify the offer, one limitation and the next step from the narrow layout. Compare answers with approved content, then adjust order and wording. Check cropping and reading with longer text afterward: moving a block should not conceal a condition elsewhere on the page.

    W3C WAI: page structure. · Source consulted

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    WCAG 2.2 · 1.4.10
    320 CSS pxVertical content without two-dimensional scrolling; exceptions cover inherently two-dimensional content.
    WCAG 2.2 · 1.4.3
    4.5:1 / 3:1Normal / large text (18 pt or 14 pt bold); criterion exceptions apply.

    Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.

    A review case to reproduce

    A translated heading overflows

    Situation to examine
    A template works with a short heading but a longer translation hides an action or becomes unreadable on mobile.
    Proposed check
    Insert a long heading, enlarged text and a missing image. Check reading priorities, block order and access to actions across widths. Adjust the template without arbitrarily shortening useful content.
    Evidence to retain
    Annotated captures identify tested constraints and the chosen solution. The template retains readable hierarchy when real content varies.
    Fictional finding example
    The template receives “Maintenance”, then “Maintenance and support for your website after launch”. On a phone, the second title overlaps the button.
    Interpret this outcome
    Retain useful words and allow wrapping. Compare both texts in the same template instead of shortening every translation to hide the fault.

    Three complementary checks

    Fictional cases: adapt these expectations to your test contract and retain the limits of the check.

    1. Demanding content
    2. Tested composition
    3. Annotated choice

    Scroll the table horizontally if needed; with a keyboard, focus it and use the arrow keys.

    Scenario variations and expected evidence
    Variation to testExpected result in this caseEvidence to hand over
    Very long translated titleWrapping with the action still accessibleComparison of both title lengths
    Image unavailableReading and action remain understandableView without image and block order
    Text enlarged to 200%Information and controls remain availableWidth, zoom and annotated screenshot

    Decision to hand over : Justify the composition using difficult content as well as the ideal screen.

    Method reference : W3C WAI — Page Structure

    Learning scenario

    Extended exercise and expected deliverables

    Extended exercise: Set up a service page with introduction, photo, available evidence and contact. Compare rendering at 390, 768, 1440 and 1920 pixels wide. Use a long title and a paragraph twice the length provided to test the columns. Explain how the reading width, title size and photo place change. Keep the same editorial priorities between smartphone and computer, even when the layout changes.

    What to deliver with your work

    • Validated content and block priority
    • Mockups with short text and long text
    • Width Rules, Columns and Spacings
    • List of framing choices and responsive variants

    Acceptance criteria

    These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.

    1. The title maintains a clear hierarchy at all widths.
    2. A photo does not push back the useful text in an excessive space.
    3. Columns rearrange in an understandable reading order.
    4. Long contents do not produce truncation or horizontal overflow.

    Understand pre-launch checks

    Ongoing management and handover

    Pass the layout rules with the mockups. Specify the width limits, column change points and the framing of each image. Check the integration on the real content and on a longer translation. Keep a capture by format to discuss a concrete discrepancy: an indication such as “making it more balanced” is not enough to reproduce a layout decision.

    Organize site maintenance

    Compare two approaches

    A visual proposal must work within the website’s constraints. An exploratory visual direction and an implementation-ready mockup require different levels of detail.

    Visual direction exploration

    When to choose it
    Useful for discussing hierarchy, atmosphere and media treatment. Use representative content and identify exploratory elements.
    What to plan for
    Prepare several reading situations. Selected photographs must be available and their permitted use compatible with the project.

    Mockup with adaptation rules

    When to choose it
    Suitable when workflows and content are defined. Document widths, spacing, cropping and layout changes.
    What to plan for
    Show long content and missing elements. Discuss behaviours with the implementation team when they cannot be inferred from a static image.

    A risk to anticipate

    A mockup can hide a heavy photograph, an unsustainable short title or a column that cannot accommodate translations. Test these constraints before approval.

    How to decide

    Build a representative page in HTML or a suitable prototype. Compare reading on phones and large screens, then record shared rules.

    Explore this decision further

    Compare scope and costs

    Setup
    Compare actual pages and variants with their content. Separate media preparation, mobile adaptation and behaviour specifications from simple visual presentation.
    Recurring operation
    Identify who adapts mock-ups for new copy and sections. Separate editorial revision, design and implementation; one change may need all three.
    Exit and handover
    Request source files, typography, permitted media and specifications. A screenshot alone cannot reconstruct a website or recover its layout rules.

    Compare the costs of three web solutions

    Frequently asked questions

    How can a layout demonstrate that it serves the content?

    Use a real long title, a difficult image crop and complete service conditions. Check hierarchy on a phone and at high zoom. Explain choices that help readers find the offer and its action, together with constraints the layout has not yet resolved.

    Is a mock-up needed for every screen width?

    Choose cases that expose layout changes and describe the rules between them: stacking, text width, cropping and navigation. Test an intermediate width too. Two screenshots alone do not define the behaviour of the whole interface.

    Is a mockup needed for every screen width?

    Define the rules connecting layouts and show significant changes. Then check implementation between the illustrated widths, using real content and interactions. Screenshots alone cannot describe every behaviour.

    Further reading

    Browse other resources