search
Enter at least two characters without personal information.

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

    Web integration: responsibilities and practical exercise

    Web integration assembles templates, content and media into usable pages. It checks that structure and components work with real headings, tables and translations. Assess its contribution through the rendered page and its use, beyond resemblance to a mock-up.

    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 — Styling removes structural landmarks

    Missions and responsibilities

    Turn content and mockups into consistent HTML and CSS while preserving reading structure, responsive presentation and the design system with real content.

    Typical activities

    • Use headings, lists, tables and forms according to their meaning.
    • Prepare image dimensions and appropriate variants.
    • Check templates with zoom, keyboard and translated content.

    Responsibilities to agree with the team

    Integration may include simple interactions; the boundary with front-end work varies by team. Assign API, application-state and server responsibilities explicitly.

    A first piece of work to demonstrate

    Integrate a credited photo, table and form, then check mobile overflow and zoom.

    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

    Integrate an article with table, captioned image, links and translated version.

    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. Structure titles, lists and tables according to their role in content.
    2. Prepare the media with appropriate dimensions and alternatives.
    3. Check the keyboard and screen and language variations.
    4. Identify the gaps between model and truly integrated content.

    Deliverable and checks

    Deliver the article with its table, captioned media and translation. Identify content sources, image dimensions and alternative-text decisions. Record resolved differences and those still requiring a design or editorial decision.

    Compare both languages with a long heading, unavailable image and table on a narrow screen. Check heading order, link names and table-header associations. The table should remain scrollable without forcing the whole page to scroll horizontally.

    Prepare website checks

    Risks and collaboration

    The actual content is often longer than that of the model. Do not reduce the information to hide a template problem.

    Collaboration to explore: Webdesign.

    Fictional deliverable excerpt : A template associates labels with fields, organises headings and covers empty, loading and error states. Long content is checked on small screens and with a keyboard.

    What passes between the roles : Share display states, data formats and a common test dataset. An interface using mock data does not validate the real exchange; a working server alone does not validate the interface either.

    View the role comparison : Full-stack developer and Web integrator →

    Employment, trades and training
    An example to examine

    Preserve content structure during implementation

    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
    Page title: choose a service.
    Section: compare scopes.
    Subsection: included services.
    Subsection: conditions and exclusions.
    Next section: prepare the first conversation.

    What the author should be able to explain

    1. Heading levels describe organisation rather than text size alone.
    2. Two subsections at the same level belong to the same group.
    3. Reading order and presentation should remain understandable with changed styles.
    Can a heading level be chosen just to obtain a size?

    Structure should remain consistent with the content. Use styles for presentation. Inspect the heading outline, reading order and implemented components, including empty states.

    Technical reference : W3C WAI · Headings · . The excerpt is an original teaching example.

    Try a small filtered list

    These three fictional entries show a result, an empty state and a return to the full list. Try “mobile”, then an absent word. No network request is made.

    3 of 3 examples shown.

    • Images and alternativesPrepare an image and its description.
    • Mobile checksCheck a journey on a phone.
    • Writing a service pageClarify an offer and its scope.

    For review: use the keyboard, test an accented word and check the count after clearing. This local list demonstrates neither server loading nor network failure. Input is not saved or sent.

    Assess the quality of the work

    The exercise uses a long editorial page containing a table, links and an informative image. Integration should preserve content structure while adapting presentation. Examine actual document order, heading levels and overflowing areas: visually reproducing a mock-up is insufficient to verify reading.

    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
    Headings and regionsAssociate headings with the sections they introduce and use understandable regions. Preserve reading order when columns change arrangement.Large text is styled as a heading without structural meaning, or visual repositioning produces incoherent keyboard order.
    Table and widthRetain the caption, headers and relationships needed for understanding. Provide local keyboard-accessible scrolling where a table cannot fit the narrow view.The entire page overflows horizontally or essential columns disappear on phones without another way to consult the data.
    MediaDimensions, loading and alternatives match the purpose.Decoration is described as information or a useful image lacks an alternative.
    Document orderKeep meaningful headings and reading order before applying columns.Without CSS the page still makes sense; keyboard focus follows the reading journey and remains identifiable.

    A focused next step

    Integrate real text and a longer label, then check the page without columns and at narrow width. Focus the table and verify access to its final column. Fix the issue in the originating component so other pages sharing the model benefit from the correction.

    W3C WAI: page structure. · Source consulted

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    W3C · HTML language
    <html lang="fr">The default language is declared on html; local language changes are marked.
    WCAG 2.2 · 1.4.3
    4.5:1 / 3:1Normal / large text (18 pt or 14 pt bold); criterion exceptions apply.
    WCAG 2.2 · 1.4.10
    320 CSS pxVertical content without two-dimensional scrolling; exceptions cover inherently two-dimensional content.
    W3C Internationalization · HTML direction
    lang="ar" dir="rtl"Language and reading direction are separate information. Declaring ar alone does not establish the base direction; dir="rtl" does. Logical CSS properties adapt spacing without hard-coding left and right throughout the layout.

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

    A review case to reproduce

    Styling removes structural landmarks

    Situation to examine
    Headings become visually bold text. A field retains its appearance but loses its label after template integration.
    Proposed check
    Check heading structure, label associations and keyboard order. Compare rendered HTML with template intent, then test enlarged and long text. Review reused components after the fix.
    Evidence to retain
    A DOM review and documented keyboard journey show restored landmarks. Visual presentation retains understandable assistive-technology structure.
    Fictional finding example
    The label uses for="contact-email", while the field has id="email". It looks correct, but the explicit association does not match.
    Interpret this outcome
    Match the identifiers, then check the accessible name and field activation from its label. Inspect other instances of the component too.

    Three complementary checks

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

    1. Preserved structure
    2. Associated landmarks
    3. Checked reading

    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
    Click a labelActivate its control through matching for and idIdentifier pair and label test
    Change a heading’s visual sizeKeep its appropriate semantic levelHeading outline and style rule
    Visually reorder blocksCheck actual reading and tab orderDocument order and keyboard sequence

    Decision to hand over : Validate reading landmarks in the integrated document beyond visual resemblance.

    Method reference : W3C WAI — Page Structure

    Method reference : W3C WAI · Labeling Controls · Source consulted

    Learning scenario

    Extended exercise and expected deliverables

    In-depth exercise: Turn a model into a structured page containing navigation, article, image and frame. Start with an understandable reading order without CSS, then add the columns. Test the zoom, keyboard and longer text. Compare calculated font sizes to the mockup's intentions. A layout obtained with fixed heights may seem correct on a capture and break as soon as a translation adds a few lines; Check this case explicitly.

    What to deliver with your work

    • HTML with properly ordered titles and areas
    • CSS Columns and Responsive Adaptations
    • Images with declared sizes and suitable loading
    • Commented captures of long text and zoom cases

    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 order of HTML retains meaning when the columns overlap.
    2. The text can grow without being cut by a fixed height.
    3. Margins and paddings follow an explainable rule.
    4. An image does not create any significant shift or overflow when loading.

    Understand pre-launch checks

    Ongoing management and handover

    Attach files width rules, change points and cases that motivated an exception. Specify the shared styles and page ones to avoid competing corrections. A new file must be able to reuse the template without copying arbitrary values. Control integration into the browser after any changes to the content or common component.

    Organize site maintenance

    Compare two approaches

    Implementation turns visual intentions into rules. Compare a bespoke page with a reusable template according to content diversity and publishing frequency.

    Page tailored to defined content

    When to choose it
    Useful for a distinct presentation with approved content. Define semantic structure and significant layout variations.
    What to plan for
    Check cropping, zoom and intermediate widths. Avoid forced spacing that only works with mockup text.

    Data-driven template

    When to choose it
    Suitable for repeated entries or articles. Describe required and optional fields, and when blocks should disappear.
    What to plan for
    Test long titles, missing images and large lists. Preserve a readable hierarchy without empty columns.

    A risk to anticipate

    Fixed text heights can cut off translations or enlarged fonts. Use imposed proportions for media only when cropping is appropriate.

    How to decide

    Create several content samples and compare them at different widths. Document shared rules before correcting exceptions.

    Explore this decision further

    Compare scope and costs

    Setup
    Compare templates, real copy, interactive states and adaptation. Implementing an empty mock-up differs from checking long text or missing images.
    Recurring operation
    Define template upkeep and checks on newly added content. Separate editorial replacement from shared-component correction and assign retesting.
    Exit and handover
    Request templates, content rules and known gaps. A team should be able to create a suitable page without reproducing a mock-up error.

    Compare the costs of three web solutions

    Frequently asked questions

    How does integrating a page differ from reproducing a screenshot?

    Integration must support real content and its variations. Try a long title, a missing image, a translation and enlarged text. Check document order and keyboard controls too; visual similarity in one screenshot does not cover these uses.

    What should be checked when a shared CSS rule changes?

    Find the components using it and select representative content, including the most demanding case. After changing it, check those pages and the relevant focus, error and mobile states. A rule fixed in one card may move or hide information elsewhere.

    How should a missing image in an entry be handled?

    Remove the block and redistribute space, or use a clearly identified placeholder. Do not keep a large empty column or imply that a generic image depicts the subject. Check alternative text.

    Further reading

    Browse other resources