FREE WEB ACCESSIBILITY LEARNING PATH

WikiFree original practice workbook

The access trail

CASE STATUS: fictional/synthetic teaching material. Do not present the example as real research, employment experience or measured business performance.

OUTCOME
Repair a small HTML form and page structure, then document keyboard, labeling, contrast and error-feedback checks.

BEFORE YOU START
Basic HTML and CSS. A modern browser and text editor; no paid audit service.

CASE
The fictional Hawthorn Workshop signup page has an unlabeled email field, a clickable div used as a button, low-contrast helper text and an error shown only in red. The supplied local fixture contains these intentional issues and uses no real personal data.

INPUTS
Issue,Required outcome
Unlabeled email field,Programmatic visible label
Clickable div,Native keyboard-operable button
Low-contrast text,Measured readable contrast
Red-only error,Text explanation linked to the field


ENTRY CHECK

Question: Does a placeholder replace a label?

Self-check: No.

Question: Does an automated scan prove full accessibility?

Self-check: No. Manual and task-based checks remain necessary.

Question: Should focus remain visible?

Self-check: Yes.

STAGE 1: Repair document structure

Prerequisite: Basic HTML and CSS. A modern browser and text editor; no paid audit service.

Instruction: Semantic structure helps people navigate by headings and landmarks. Use one clear page topic, a logical heading hierarchy and native HTML elements for their intended purpose. The practice page should identify its language and give the main content a meaningful structure. More ARIA is not automatically better; begin with appropriate native markup.

Practice task: Inspect the fixture and repair its page language, headings and main landmark. Write a short navigation outline.

Deliverable: A semantic page structure and heading map.

Acceptance check: The outline describes the page without relying on font size alone.

If stuck: Do not choose heading levels solely to get a desired visual size.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 2: Make the form operable by keyboard

Prerequisite: Bring your previous output: A semantic page structure and heading map.

Instruction: Native buttons and inputs provide expected keyboard behavior. Follow the tab order through the whole task and keep focus visibly distinguishable. A control that responds only to a mouse click is not an equivalent interaction. Avoid positive tabindex values as a shortcut for a confusing document order; fix the underlying sequence.

Practice task: Replace the clickable div with a button and complete the form using only the keyboard. Record the focus sequence.

Deliverable: A keyboard-operable form and test log.

Acceptance check: Every interactive control is reachable, focus is visible and no keyboard trap occurs.

If stuck: Do not remove outlines without providing a clearly visible replacement.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 3: Label inputs and explain errors

Prerequisite: Bring your previous output: A keyboard-operable form and test log.

Instruction: Associate a visible label with each field using matching for and id values. Instructions and errors should explain what the user must do and be programmatically associated where appropriate. Color can reinforce an error but cannot be its only signal. Preserve valid user input after an error so correction does not require starting again.

Practice task: Add the email label, useful instructions and a text error linked to the input. Test blank and invalid values.

Deliverable: A labeled form with understandable feedback.

Acceptance check: The field has an accessible name, the error is readable without color and valid input is retained.

If stuck: A red border alone does not explain why submission failed.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 4: Review contrast and non-text content

Prerequisite: Bring your previous output: A labeled form with understandable feedback.

Instruction: Measure text contrast rather than judging it by eye. For this exercise, use the common WCAG AA thresholds of 4.5:1 for normal text and 3:1 for large text, applying the definitions in the referenced guidance. Meaningful images need an appropriate text alternative; decorative images should not create redundant noise. A single ratio does not settle the accessibility of the whole page.

Practice task: Check the supplied color pairs, replace the failing helper text color and classify any images as informative or decorative.

Deliverable: A contrast record and image-alternative review.

Acceptance check: The report includes actual foreground/background values and distinguishes image purpose.

If stuck: Do not add repetitive alt text to a purely decorative shape.

Record your work, decisions and evidence:




Record your result against the acceptance check:



STAGE 5: Combine automated and manual review

Prerequisite: Bring your previous output: A contrast record and image-alternative review.

Instruction: Automated tools can find some markup and contrast problems, while keyboard behavior and the clarity of instructions require human judgment. Record the tool and version if one is used, then repeat the actual signup task manually. A screen-reader check is valuable when available, but do not claim it was performed if you only inspected HTML.

Practice task: Run an available browser accessibility check, repeat the keyboard task and write an issue log with resolved and remaining items.

Deliverable: A repaired page and bounded accessibility report.

Acceptance check: The report separates automated findings, manual checks and tests not performed.

If stuck: Do not label the page fully compliant based on a clean automated report.

Record your work, decisions and evidence:




Record your result against the acceptance check:



WORKED CASE
A visible label connected with for/id gives the email field a meaningful name. A native button restores expected keyboard activation. A linked text error explains the correction even when the red border is not perceived.

FINAL PROJECT
Deliver the original and repaired HTML, a change log, keyboard sequence, contrast checks and residual-issue report. Have another reviewer attempt the task if possible and label that evidence accurately.

REQUIRED CRITICAL CHECK
The form can be completed by keyboard and errors and labels do not depend on color or placeholders alone.

SCORING
Score each of the five stage acceptance checks from 0–16 (0 missing/incorrect; 8 partially supported; 16 complete and evidenced). Score the final integrated project from 0–20 (0 missing; 10 incomplete handover; 20 complete, reproducible and consistent with the case). Target: at least 80/100 AND the critical check must pass. A total score never overrides a failed critical check.

SCOPE LIMIT
This is a focused repair and testing exercise, not a legal opinion or a conformance certification for an entire website.

SOURCES AND ACCESS
The written course is public and free. The project uses a local HTML file, browser and text editor. Optional automated tools and assistive technologies depend on your environment.

Google Learn Accessibility: Free Web Accessibility Course
WikiFree: https://wikifree.com/courses/google-learn-accessibility/
Official source: https://web.dev/learn/accessibility
Why selected: Google web.dev provides the public written accessibility curriculum. Assigned reading groups follow its published topics; time allocations are editorial estimates.

Stage 1 assigned focus: The document and content structure; 30 minutes (WikiFree reading estimate).

Stage 2 assigned focus: Keyboard focus and JavaScript; 35 minutes (WikiFree reading estimate).

Stage 3 assigned focus: Forms and patterns/components; 40 minutes (WikiFree reading estimate).

Stage 4 assigned focus: Color and contrast; images; 35 minutes (WikiFree reading estimate).

Stage 5 assigned focus: Automated, manual and assistive technology testing; 40 minutes (WikiFree reading estimate).

web.dev accessibility course
https://web.dev/learn/accessibility/

W3C form labeling tutorial
https://www.w3.org/WAI/tutorials/forms/labels/

REUSE
Original WikiFree teaching text and synthetic fixtures are supplied for personal learning and adaptation with attribution. Provider lessons remain on their original sites and retain their own terms. No provider certificate is included.