HTML Project: Build an Accessible Settings Dialog

Ready to build something with HTML? In this exercise you will create a native settings dialog with clear labels, open/close behavior and save/cancel buttons. 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: create a native settings dialog with clear labels, open/close behavior and save/cancel buttons
• showModal opens a modal dialog and moves it into the top layer
• The title has a real heading connected with aria-labelledby

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.

<button id="open-settings" type="button">Open settings</button>
<dialog id="settings-dialog" aria-labelledby="settings-title">
    <h2 id="settings-title">Learning preferences</h2>
    <form method="dialog">
        <label for="lesson-speed">Lesson pace</label>
        <select id="lesson-speed" name="pace">
            <option value="slow">Relaxed</option>
            <option value="normal">Normal</option>
        </select>
        <button value="save">Save</button>
        <button value="cancel">Cancel</button>
    </form>
</dialog>
<script>
    const settingsDialog = document.querySelector('#settings-dialog');
    document.querySelector('#open-settings').addEventListener('click', () => {
        settingsDialog.showModal();
    });
</script>

Step 3: Understand what the example does

• showModal opens a modal dialog and moves it into the top layer.
• The title has a real heading connected with aria-labelledby.
• A method=dialog form can close the dialog, but saving preferences requires application logic.

The JavaScript in the example opens the dialog, but saving settings requires additional application logic.

Step 4: Finish the project

1. Replace the example words and sample data with your own original content that fits the assignment.
2. Add every section and control described in the project goals. Keep a clear heading order and meaningful labels.
3. Save your work, open it in a browser, and check actual behavior with both mouse and keyboard.
4. Check that linked files, images, form destinations, and IDs really exist; fix any broken paths or duplicate identifiers.
5. 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: Create a native settings dialog with clear labels, open/close behavior and save/cancel buttons
• Any HTML validator warnings or browser console problems have been reviewed and fixed.

Common Beginner Mistakes

• Focus handling must be tested with both keyboard and screen reader.
• 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 create a native settings dialog with clear labels, open/close behavior and save/cancel buttons.
• showModal opens a modal dialog and moves it into the top layer.
• A successful project is understandable, valid, accessible, and tested—not merely visually attractive.