Coursya learning paths / 09 · The browser workshop
The browser workshop
Structure first. Style with intent. Test the experience.
Build a responsive, accessible five-section website with semantic HTML, reusable CSS and a documented browser test checklist.
Local build / browser workshop
A page that holds together.
another chapter.Semantic structure. Flexible layout.
- Beginner
- starting level
- 3
- core courses
- ≈23h
- learning + practice estimate
- 5 + 1
- stages + final project
Table of Contents
The practical outcome
What you will be able to show
Build a responsive, accessible five-section website with semantic HTML, reusable CSS and a documented browser test checklist.
For: Beginners who can save files and use a web browser.
Before you begin: A computer, a text editor and a modern browser. No framework, paid hosting, build system or JavaScript is required for this first website.
Original pathway and exercises by Coursya Editorial. Course pages and official source metadata reviewed on 12 October 2026. Version 1.0.
A ten-minute starting check
Try these before opening a lesson
Answer in your own words, then reveal the guidance. If you can already demonstrate a stage’s completion gate with evidence, skim its lesson assignment and move to the next stage.
What should a link do when its text says “View the schedule”?
Move to the actual schedule, using a real destination rather than an empty # link.
Should a page need CSS to reveal its main information?
No. Its headings, text and link order should still make sense without styling.
Does checking one phone width prove responsiveness?
No. Test narrow and wide layouts, zoom, long content and keyboard navigation.
Sequence with a purpose
Build one layer at a time
- 01Write meaningful HTMLA semantic HTML page with working section links.
- 02Create a small CSS systemA maintainable style foundation.
- 03Arrange components without rigid widthsFlexible components and a keyboard test note.
- 04Adapt to screens and reading needsA responsive page and a test log.
- 05Finish content and verify the handoverA final site folder and a short README.
Finish with the capstone. Progress means a reviewable output, not simply a watched video.
A deliberately short course list
Use these courses for these reasons
Google Learn HTML: Free Web Development Course
Google · Beginner · English
HTML comes first so that structure, headings and links work before styling.
Assigned viewing: written modules; no verified video duration. The full source course contains additional material.
Open the Coursya course and official learning route ↗Google Learn CSS: Free Web Styling Course
Google · Beginner · English
Selected CSS modules add the box model, selectors, layout and focus styling to that structure.
Assigned viewing: written modules; no verified video duration. The full source course contains additional material.
Open the Coursya course and official learning route ↗Google Learn Responsive Design: Free Responsive Web Design Course
Google · Beginner · English
Responsive-design modules then address small screens, readable type and interaction.
Assigned viewing: written modules; no verified video duration. The full source course contains additional material.
Open the Coursya course and official learning route ↗Free learning, clearly defined
All selected web.dev reading modules are public and free. Local files in a browser are enough to complete the project. No paid hosting or formal certificate is required or promised; optional provider badges are separate from the Coursya project.
Skills and evidence
| Stage / skill | Learning support | Evidence to produce |
|---|---|---|
| 01 · Write meaningful HTML | Google selected lessons | A semantic HTML page with working section links. |
| 02 · Create a small CSS system | Google selected lessons | A maintainable style foundation. |
| 03 · Arrange components without rigid widths | Google selected lessons | Flexible components and a keyboard test note. |
| 04 · Adapt to screens and reading needs | Google selected lessons | A responsive page and a test log. |
| 05 · Finish content and verify the handover | Google selected lessons | A final site folder and a short README. |
Stage 1 / The browser workshop
Write meaningful HTML
You will: Create a document that works before styling.
Assigned learning
Google Learn HTML: Free Web Development Course
- Document structureRead
- Semantic HTMLRead
- Headings and sectionsRead
- LinksRead
Use the names if the provider later changes the order. Only these assignments enter the core estimate.
Start with the document language, a descriptive title and a viewport declaration. Use header, nav, main, section and footer where their meanings fit. One clear page heading should describe the page; section headings should expose its structure.
Use links for destinations and buttons for actions. A schedule link should target a real section ID. Put the content in a logical reading order before choosing columns or colors.
Make something reviewable
Build the five-section page from the supplied brief. Add a skip link, section navigation and meaningful headings. Disable CSS and check whether the order remains understandable.
Deliver: A semantic HTML page with working section links.
Completion gate
Every navigation link resolves, the page has one H1, and its purpose remains clear without styles.
If you get stuck: If headings are chosen only for size, fix the hierarchy and style their appearance separately. If links use # without a destination, supply the real section ID.
Stage 2 / The browser workshop
Create a small CSS system
You will: Control spacing and type consistently.
Assigned learning
Google Learn CSS: Free Web Styling Course
- Box ModelRead
- SelectorsRead
- The cascadeRead
- Sizing UnitsRead
Use the names if the provider later changes the order. Only these assignments enter the core estimate.
Use border-box sizing so padding does not unexpectedly expand a declared width. Set a readable base font, line height and a limited content width. Start with a few reusable spacing values rather than a different number for every element.
The cascade explains why a rule wins; adding increasingly specific selectors can hide the original mistake. Inspect the applied styles, then simplify the selector or remove the conflicting rule.
Make something reviewable
Create a stylesheet with color and spacing variables, a reusable container, readable paragraphs and consistent section spacing. Explain the box model of one service card.
Deliver: A maintainable style foundation.
Completion gate
Text remains readable when enlarged and repeated components share rules rather than copied inline styles.
If you get stuck: If widths overflow after padding, inspect box-sizing. If a style seems ignored, use browser inspection to find the winning rule before adding !important.
Stage 3 / The browser workshop
Arrange components without rigid widths
You will: Build flexible navigation and service layouts.
Assigned learning
Google Learn CSS: Free Web Styling Course
- FlexboxRead
- GridRead
- FocusRead
Use the names if the provider later changes the order. Only these assignments enter the core estimate.
Use flexbox for a row of navigation items that can wrap, and grid for repeated service cards. Let content determine height. Avoid fixed card heights that clip a longer description or enlarged text.
Keep visible focus on links and controls. A custom style must remain recognizable against its background and should not depend on hover alone. The supplied reference uses a high-contrast outline and leaves native link behavior intact.
Make something reviewable
Build a wrapping navigation and a service-card grid. Replace one short service description with a paragraph twice as long. Tab through every link and open the details element without a mouse.
Deliver: Flexible components and a keyboard test note.
Completion gate
Long content fits; keyboard focus is visible; navigation order follows the document.
If you get stuck: If equal-height styling cuts text, remove the fixed height. If keyboard focus disappears, restore a clear :focus-visible outline instead of using outline: none.
Stage 4 / The browser workshop
Adapt to screens and reading needs
You will: Test layout changes at meaningful breakpoints.
Assigned learning
Google Learn Responsive Design: Free Responsive Web Design Course
- Media queriesRead
- Macro layoutsRead
- TypographyRead
- AccessibilityRead
- InteractionRead
Use the names if the provider later changes the order. Only these assignments enter the core estimate.
Choose a breakpoint where the content stops working, not because a device name sounds standard. Start with a single-column layout, then add columns when there is enough space. Keep text measures comfortable and allow navigation to wrap.
Check at 360, 768 and 1280 CSS pixels, plus 200% browser zoom on a desktop viewport. These are practical sample checks, not a promise that every browser or assistive technology has been tested.
Make something reviewable
Test the page at the three widths and at zoom. Fix unintended horizontal scrolling, clipped text and cramped links. Record the browser and actual observations, including any unresolved problem.
Deliver: A responsive page and a test log.
Completion gate
There is no page-level horizontal overflow in the tested layouts; content stays available at zoom; links have usable spacing.
If you get stuck: If one element creates overflow, inspect its minimum width, long text and grid sizing. Use min-width: 0 on shrinking grid children where needed.
Stage 5 / The browser workshop
Finish content and verify the handover
You will: Deliver a usable static site with honest behavior.
Assigned learning
Google Learn HTML: Free Web Development Course
- MetadataRead
- ImagesRead
- FocusRead
- Details and summaryRead
Use the names if the provider later changes the order. Only these assignments enter the core estimate.
Write a useful title and description, and supply alt text for informative images. A decorative image can have an empty alternative. The reference uses CSS shapes and text, so no image download or attribution dependency is required.
Use details/summary for the “What to bring” disclosure. Do not add a form that claims to send a booking when no backend exists. Describe the demo’s limits in the footer and remove unfinished placeholder content before handover.
Make something reviewable
Complete the copy, metadata, link check and keyboard check. Open index.html from a clean folder containing only the deliverable files. Ask a peer to find the schedule and visit information.
Deliver: A final site folder and a short README.
Completion gate
All local resources load, all five sections are complete, and no control promises an unimplemented service.
If you get stuck: If the page works only in your editor preview, check file paths and filename case. If a form is cosmetic, remove it or clearly implement and test the actual behavior in a later project.
Original practice material
Your case pack and reference checks
Download the editable plain-text workbook, or open the full copy below. It contains the case inputs, templates and reference guidance. Try the exercises before reading the answers.
Download the practice workbook ↓ Download project files (ZIP) ↓Open the complete workbook in this page
WIKIFREE / THE BROWSER WORKSHOP
Original fictional website brief and reference. 12 October 2026.
BRIEF
Hilltop Repair Cafe is a training demo, not a real event or booking service.
Build Welcome, Services, Schedule, What to bring and Visit. Use one H1,
semantic landmarks, meaningful links, a skip link and native details/summary.
Start from the starter section; finish your own CSS before reviewing the reference.
TEST LOG (record observations, do not prefill a pass)
Browser/version:
360px width: overflow, clipping, link spacing:
768px width:
1280px width:
200% desktop zoom:
Keyboard: skip link, navigation, visible focus, details Enter/Space:
CSS disabled: structure and main information:
Clean-folder local-file opening and resource paths:
Peer tasks: find schedule; explain demo limits:
Remaining problems and fixes:
REFERENCE FILES
Save web_reference.html and web_reference.css in the same folder and open the HTML.
The starter links to styles.css, which you create yourself. That is an intentional
student task, not a missing file in the reference solution.
===== web_starter.html =====
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>My repair café practice site</title><link rel="stylesheet" href="styles.css"></head><body>
<!-- Student starter: replace instructional text with your own complete content. -->
<a href="#main">Skip to main content</a><header><nav aria-label="Main navigation"><a href="#schedule">Schedule</a><a href="#visit">Visit</a></nav></header>
<main id="main"><section><h1>My fictional repair café</h1><p>Write the visitor promise and label this as a training demo.</p></section><section id="services"><h2>Services</h2><p>Describe three useful services.</p></section><section id="schedule"><h2>Schedule</h2><p>Provide the illustrative schedule.</p></section><section id="bring"><h2>What to bring</h2><p>Add a native details disclosure.</p></section><section id="visit"><h2>Visit</h2><p>Explain the fictional location and the limits of this demo.</p></section></main><footer><p>Training demo — no real bookings.</p></footer></body></html>
===== web_reference.html =====
<!doctype html>
<html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>Hilltop Repair Café — Training Demo</title><meta name="description" content="A fictional community repair event: explore services, the schedule, what to bring and visit information.">
<link rel="stylesheet" href="web_reference.css"></head><body>
<a class="skip" href="#main">Skip to main content</a>
<header class="container site-head"><strong>Hilltop Repair Café</strong><nav aria-label="Main navigation"><a href="#services">Services</a><a href="#schedule">Schedule</a><a href="#bring">What to bring</a><a href="#visit">Visit</a></nav></header>
<main id="main"><section class="hero" aria-labelledby="welcome"><div class="container"><p class="eyebrow">Fictional event · Web development practice</p><h1 id="welcome">Give a useful thing<br>another chapter.</h1><p>Learn how a simple repair works, ask questions and meet other curious makers. This is a training website for an imagined community event.</p><a class="button" href="#schedule">View the schedule</a></div></section>
<section class="container section" id="services" aria-labelledby="services-title"><p class="eyebrow">01 / Services</p><h2 id="services-title">Small repairs. Shared learning.</h2><div class="cards"><article><h3>Fabric basics</h3><p>Explore a loose seam, a missing button or a small patch. Bring one clean item and describe what you would like to learn.</p></article><article><h3>Everyday objects</h3><p>Discuss a loose handle or an item that needs a closer look. The demonstration starts with understanding the problem.</p></article><article><h3>Repair planning</h3><p>Not every item is suitable for the session. Learn what information to gather before asking a qualified specialist for help.</p></article></div></section>
<section class="container section" id="schedule" aria-labelledby="schedule-title"><p class="eyebrow">02 / Schedule</p><h2 id="schedule-title">An unhurried morning.</h2><dl class="schedule"><div><dt>10:00</dt><dd>Welcome and an introduction to the practice stations.</dd></div><div><dt>10:30</dt><dd>Small-group demonstrations and questions.</dd></div><div><dt>11:30</dt><dd>Share what you learned and plan a next step.</dd></div></dl><p class="note">This is an illustrative schedule. No real event or booking is offered.</p></section>
<section class="container section" id="bring" aria-labelledby="bring-title"><p class="eyebrow">03 / What to bring</p><h2 id="bring-title">Start with one item and a question.</h2><details><summary>Open the preparation checklist</summary><ul><li>One clean, manageable item for discussion.</li><li>A short description of the problem and anything already tried.</li><li>A notebook for your next steps.</li></ul><p>The fictional session does not cover hazardous materials or live electrical work.</p></details></section>
<section class="container section visit" id="visit" aria-labelledby="visit-title"><p class="eyebrow">04 / Visit</p><h2 id="visit-title">A place to learn together.</h2><p>For this exercise, imagine a step-free community room with seating and a quiet discussion area. A real event page would provide a verified address, access details and a contact route.</p><p><strong>Training demo:</strong> no real venue, booking form or personal-data collection is connected to this page.</p><a href="#welcome">Back to the introduction</a></section></main>
<footer class="container"><p>Coursya original learning example · Hilltop Repair Café is fictional.</p></footer></body></html>
===== web_reference.css =====
:root{--ink:#152f46;--accent:#274e9b;--paper:#f7f9fc;--space:clamp(1.2rem,3vw,2.5rem)}
*{box-sizing:border-box}html{scroll-behavior:smooth;scroll-padding-top:1rem}body{margin:0;background:var(--paper);color:var(--ink);font:1rem/1.7 Arial,sans-serif}a{color:var(--accent);text-underline-offset:.25em}a:focus-visible,summary:focus-visible{outline:3px solid #172d52;outline-offset:5px}.container{width:min(1100px,calc(100% - 2.5rem));margin-inline:auto}.skip{position:absolute;top:-100px;left:1rem;background:#fff;padding:.75rem;z-index:10}.skip:focus{top:1rem}.site-head{display:flex;justify-content:space-between;gap:1rem;align-items:center;padding-block:1.4rem;flex-wrap:wrap}nav{display:flex;flex-wrap:wrap;gap:.5rem 1.3rem}nav a{padding:.4rem 0}h1,h2,h3{line-height:1.15}h1{font:normal clamp(2.7rem,6vw,5rem)/1.08 Georgia,serif;max-width:14ch;margin:.7rem 0 1.4rem}h2{font:normal clamp(2rem,4vw,3rem)/1.2 Georgia,serif}h3{font-size:1.2rem}p{max-width:70ch}.hero{background:#dce8ff;padding:clamp(3rem,7vw,6rem) 0}.eyebrow{font-size:.75rem;letter-spacing:.12em;text-transform:uppercase;font-weight:bold}.button{display:inline-block;background:var(--accent);color:white;padding:.85rem 1.2rem;border-radius:4px;text-decoration:none;font-weight:bold}.section{padding-block:var(--space);border-bottom:1px solid #bdcadd;scroll-margin-top:1rem}.cards{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:1.2rem}.cards article{background:white;border:1px solid #bdcadd;padding:1.5rem;min-width:0}.schedule{max-width:800px}.schedule div{display:grid;grid-template-columns:5rem minmax(0,1fr);gap:1rem;border-top:1px solid #bdcadd;padding:1rem 0}.schedule dt{font-weight:bold}.schedule dd{margin:0}.note{font-size:.9rem;color:#445c71}details{background:white;border:1px solid #bdcadd;padding:1.2rem;max-width:800px}summary{cursor:pointer;font-weight:bold;min-height:2.5rem}footer{padding-block:2rem;font-size:.85rem}section,article{overflow-wrap:anywhere}@media(max-width:720px){.cards{grid-template-columns:1fr}.site-head{align-items:flex-start}nav{width:100%}.hero{padding-block:3rem}}@media(prefers-reduced-motion:reduce){html{scroll-behavior:auto}}
Case data, exercises and reference examples: Coursya Editorial, original training material. Provider lessons are linked, not reproduced.
Final project / 4h practice estimate
The Hilltop Repair Café website
Deliver a complete static site from the supplied brief. Use the reference as a comparison after your own attempt, then explain two design choices and one remaining limitation.
Your handover package
- index.html and a reusable stylesheet with five complete sections
- Real section navigation, a skip link and a native details interaction
- A test log for three widths, keyboard use, 200% zoom and local links
- A README explaining how to open the site and what is outside its scope
| Criterion | Points | Evidence expected |
|---|---|---|
| Structure and content | 25 | Semantic landmarks, heading order and complete information. |
| Responsive styling | 30 | Flexible layouts, readable type and no observed overflow in the required checks. |
| Interaction and accessibility | 30 | Keyboard focus, meaningful links and honest controls. |
| Handover | 15 | Files open independently and the actual test results are documented. |
Completion standard: aim for at least 80/100, with all critical gates met. A reviewer awards each row’s points in proportion to the evidence shown. This is a learning rubric, not a provider credential.
Missing main content, unusable keyboard navigation or a fake booking-success interaction must be corrected.
A pace that leaves room to practice
Plan the next few weeks
Assigned reading: about 5 hours, editorial estimate; the provider gives no verified total duration. Practice and capstone: 17.5 hours, editorial estimate. Budget about 23 hours overall. Replays and personal adaptations can take longer.
| Available time | Flexible estimate | How to use it |
|---|---|---|
| 2 hours/week | 12 weeks | Reserve time to make the output and pass its gate; split a long lesson across sessions. |
| 5 hours/week | 5 weeks | Reserve time to make the output and pass its gate; split a long lesson across sessions. |
| 10 hours/week | 3 weeks | Reserve time to make the output and pass its gate; split a long lesson across sessions. |
The calculation stays in your browser. The estimates above remain usable without JavaScript.
Checkbox progress is saved only in this browser when local storage is available. It is not sent to Coursya or synchronized to an account.
Questions before you continue
Why are there three courses but no video duration?
They cover distinct layers: HTML, CSS and responsive design. They are written courses without a verified total duration; the reading estimate is editorial and separate from practice.
When should I learn JavaScript?
After you can build and explain this static page. Add JavaScript when a real interaction requires it, then give that behavior its own tests.
Add interaction after the page works
When your HTML and CSS project is readable on a narrow screen and usable with a keyboard, continue with the JavaScript Programming learning path. Add one interaction to the page you already built instead of starting an unrelated large application.
- Choose a small task, such as filtering a short list or validating a practice form.
- Write the expected behaviour before coding, including an empty result and an invalid input.
- Test the control with a keyboard and verify that important content remains available if the script fails.
Finish when: you can explain the event, the data being read and the part of the page that changes. Give controls clear labels and make error messages understandable. This is an optional continuation after the existing web project; the beginner path does not require a framework or a paid tool.
Sources and honest boundaries
What was checked, and what comes next
This path builds a static website. JavaScript programming, backend services, authentication, payment processing and production hosting are outside its outcome. Accessibility checks here are a beginner practice, not a conformance certification.
The complete published Coursya course catalog was checked on 12 October 2026: 815 courses across nine API pages. Course pages and official playlist metadata or module headings were inspected. This does not mean every video was played to completion, every geographic region was tested, or a provider credential was earned.
- Google · official source for Google Learn HTML: Free Web Development Course
- Google · official source for Google Learn CSS: Free Web Styling Course
- Google · official source for Google Learn Responsive Design: Free Responsive Web Design Course
- web.dev Learn HTML
- web.dev Learn CSS
- web.dev Learn Responsive Design
Keep the published course pages as your route into provider material. Access, lesson order and tool interfaces can change. Report a broken route through Coursya’s correction page.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.