Launching your website · Lanzar tu sitio web
| English | Español |
|---|---|
| hosting/ˈhəʊstɪŋ/ | alojamiento web |
| domain name/dəˈmeɪn neɪm/ | nombre de dominio |
| accessibility/ækˌsesəˈbɪlɪti/ | accesibilidad |
The published link works for you, but not for your reader
- Your browser may have cached files or an account permission that the intended reader does not have. Local success is only one check.
- Hosting 托管 makes the website available from a server; a domain name 域名 identifies a name visitors can use. Availability and access still need verification.
Test the important user journeys
- Check navigation, downloads and any form using a safe test destination. Confirm both the success path and useful error messages; do not submit personal data just to test.
- Use a narrow desktop view during development and a real phone when available. These reveal different issues, such as touch behaviour, viewport sizing and device-specific rendering.
Which approach gives useful evidence about mobile behaviour?
Resizing helps test layout; a real device adds evidence about touch and device-specific behaviour.
Check access through more than one route
- Accessibility 无障碍 includes readable content, useful labels and keyboard operation. Test Tab order, visible focus and whether every needed action can be completed without a mouse.
- Check enlarged text and image alternatives. Contrast guidance concerns foreground/background luminance, not a promise that content will be readable in every sunlight condition.
A visually correct screenshot proves that keyboard operation works.
A screenshot does not establish focus order, visible focus through the journey or activation behaviour.
Gather evidence for a release decision
- Record the device or browser, task, expected result, actual result and any issue. Use a fresh browser context for access checks when possible.
- Prioritise blockers: a broken joining link matters more than a minor spacing preference. Re-test the failing task after a repair.
Task: open the joining page as a reader. Expected: instructions load without an editing account. Actual: an account prompt blocks access. Repair the intended sharing or route configuration, then repeat the reader check.
Write one release test that a screenshot alone cannot prove, including its expected result.
Example: “Open the joining page as the intended reader and confirm instructions load without an editing account.”
Match each test-log field to the information it records.
Separating expectation, observation and environment makes a failure reproducible.
Check publication rights and privacy
- Check reuse terms and credits for borrowed images, fonts and music. Citation acknowledges a source; it does not automatically grant permission to publish it.
- Check consent for identifiable people and avoid exposing private records or credentials. Replace misleading placeholders and remove actions that pretend to work.
A contact form that displays “Sent” without delivering anything misleads visitors. Make the feature work with appropriate testing, or give honest instructions for contacting the club another way.
Which borrowed assets need their reuse terms checked before publication? Select all that apply.
Check the applicable rights and credits for each borrowed asset. Giving a source does not itself grant permission.
A contact form always says “Sent” but sends nothing. What is the most useful repair?
The problem is misleading functionality. A visual change does not establish delivery.
Plan what happens after launch
- Keep a recoverable copy and record the released version. Know how to report a problem and restore a working version if necessary.
- Prepare a launch log with completed checks and unresolved issues. Follow your teacher's approval and submission process; this lesson does not promise a particular mark.
Verify the reader's actual tasks, keyboard access, layout and permissions. Record evidence, repair blockers and keep a recovery route.
The joining link is broken and a heading has slightly uneven spacing. Which should you fix first?
Prioritise failures that prevent the intended task, then re-test the repair.
A link working for an editor proves it works for every intended reader.
An editor may have permissions the reader lacks. Verify intended access directly without exposing private information.