Ready to build something with HTML? In this exercise you will build a collection of error notices with severity text, next steps and focusable help links. This is practice, so the goal is to understand your choices rather than just copy a finished design.
You can use a plain text editor and any current browser. Create a separate project folder and save your page as index.html unless the task calls for several pages. You do not need to finish every improvement on the first try. A small valid page is a better starting point than a complicated page that nobody can use.
What you will build
- Organize the content into a clear page title and sections related to the assignment
- Implement the feature described in the brief: build a collection of error notices with severity text, next steps and focusable help links
- role=status can announce nonurgent updates from scripts
- progress expresses a known portion of a task, unlike meter
Step 1: Plan the page
Before writing code, list the content your visitor needs to understand or complete the task. Mark the page title, navigation, major sections, and interactive parts. If the visitor should fill in a form, decide which fields are truly necessary. If the visitor needs to compare data, identify your row and column headings first.
Step 2: Start with working HTML
The following starter example focuses on the central HTML technique used in this project. Type it into a file, run it in your browser, and then expand it to meet the requirements above. The starter is not presented as the entire finished assignment.
<section aria-labelledby="status-heading">
<h2 id="status-heading">Current lesson status</h2>
<p role="status" id="lesson-status">Ready for practice.</p>
<label for="lesson-progress">Lesson progress</label>
<progress id="lesson-progress" max="10" value="7">7 of 10</progress>
<p>Next: complete the final three exercises.</p>
</section>Step 3: Understand what the example does
- role=status can announce nonurgent updates from scripts.
- progress expresses a known portion of a task, unlike meter.
- Visible explanatory text remains useful to all readers.
All file names and text are teaching examples. Replace placeholders with real files and meaningful project content.
Step 4: Finish the project
- Replace the example words and sample data with your own original content that fits the assignment.
- Add every section and control described in the project goals. Keep a clear heading order and meaningful labels.
- Save your work, open it in a browser, and check actual behavior with both mouse and keyboard.
- Check that linked files, images, form destinations, and IDs really exist; fix any broken paths or duplicate identifiers.
- If JavaScript, a web server, or another asset is necessary, add it explicitly or explain what remains a demonstration.
How to check your finished work
- The page clearly communicates its topic without relying on decorative styling.
- Headings are in a logical order, and important information remains readable at 200% zoom.
- Links and buttons work with the keyboard and have understandable labels.
- Images and media have appropriate accessible text alternatives; tabular data has proper header associations.
- The project-specific requirement is met: Build a collection of error notices with severity text, next steps and focusable help links
- Any HTML validator warnings or browser console problems have been reviewed and fixed.
Common Beginner Mistakes
- Do not depend on red/green color to convey a message.
- Skipping testing because the page looks correct at one window size.
- Using placeholder data or missing resources in a project presented as complete.
Key Takeaways
- The goal is to build a collection of error notices with severity text, next steps and focusable help links.
- role=status can announce nonurgent updates from scripts.
- A successful project is understandable, valid, accessible, and tested—not merely visually attractive.