Coursya Editorial

Web Accessibility Specialist Career Path: Courses and Portfolio Project

Build a web accessibility specialist portfolio with course resources, five practical stages, exercises and a project review rubric.

Career studio / Web Development

Build evidence for the Web Accessibility Specialist role

A workshop registration page has missing labels, weak focus visibility and unclear validation feedback. Audit a local sample, propose fixes and record exactly what was tested.

Intermediate3 course resources5 practical stages1 portfolio project

Your outcome: Accessibility audit, prioritized remediation backlog and retest evidence.

Table of Contents

Start with the right expectations

Who this is for

HTML and CSS basics; access to a browser and preferably a screen reader.

This path develops a demonstrable work sample for the named role. It does not replace employer-specific experience, professional qualifications or supervised practice.

Plan your study time

Use a flexible six-week project schedule: one week for each of the first four stages and two weeks for the portfolio and review. Allow roughly 3–5 hours per week for the case work, in addition to course study. This is a planning suggestion, not a measured course duration or a promise of job readiness.

Read the course access notes before starting. Free viewing or reading does not automatically include certificates, graded assessments, software licences or paid cloud resources. Core case work can be documented with a free editor and spreadsheet; optional implementation tools may have additional requirements.

Your course sequence

Start in the order below. Use the course outline to select the sections relevant to the stage tasks, and complete foundation exercises before moving on. Full provider courses can be substantially longer than this project schedule. These are course resources, not a claimed count of individual lessons.

Resource 01 / Google

Google Learn Accessibility: Free Web Accessibility Course

Purpose: Build the foundations. Connect your notes to the case tasks below rather than only collecting completion marks.

  • Understand digital accessibility: consider how disability and different interaction needs affect the use of a website.
  • Create meaningful structure: explore content organisation, semantic HTML and appropriate use of ARIA.
  • Improve interface details: examine keyboard focus, images, colour contrast, motion and typography.

Access: Free public lessons and practice using browser/local code, Chrome DevTools Lighthouse and a free compatible screen reader such as NVDA; no paid toolkit required. No account needed to read; optional standard Google developer profile for badge collection is free.

Certificate: Accessibility developer-profile badge offered through the course quiz. No formal certificate, credit, accreditation or website-compliance certification promised.

Open the Coursya course · Provider learning source

Resource 02 / Google

Google Learn Forms: Free HTML Forms Course

Purpose: Develop the role-specific method. Connect your notes to the case tasks below rather than only collecting completion marks.

  • Build an appropriate form structure: understand the form element and choose controls for the information being requested.
  • Guide data entry: use labels, relevant input types, autocomplete and suitable attributes to reduce avoidable effort.
  • Explain validation: explore browser constraints and communicate requirements before someone encounters an error.

Access: Free public lessons and local mock HTML/CSS/JavaScript form practice using a browser and text editor. The route does not require paid hosting/software, a real payment processor, a real purchase, card, trial or subscription. CodePen demos are optional for independent local practice. No account needed to read; free Standard profile is optional for badge.

Certificate: Learn Forms developer-profile badge offered after course completion confirmation. No formal certificate, academic credit, accreditation or website accessibility/security certification promised.

Open the Coursya course · Provider learning source

Resource 03 / Google

Google Tech Writing for Accessibility: Free Self-Study Course

Purpose: Strengthen practical application. Connect your notes to the case tasks below rather than only collecting completion marks.

  • Recognise how permanent, temporary and situational barriers affect the way people use documentation.
  • Write concise alternative text that explains an image’s purpose in its surrounding context.
  • Measure foreground and background contrast instead of relying on how colours look to you.

Access: Free public self-study lessons and exercises using a browser, editor and contrast checker. No account or paid tools required.

Certificate: No completion certificate provided.

Open the Coursya course · Provider learning source

Learn, make, check

Keep a decision log as you work. For each stage, capture the assumption, your work product, a check and the change you made after that check. The acceptance criterion is the stopping condition for the stage.

Stage 1 / suggested project week 1

Understand the interaction

Understand: Accessibility includes structure, operation and understandable feedback.

Make: Map the registration task and identify controls, headings and status messages.

Check before moving on: Do not treat a single automated score as a complete audit.

Study companion: Google Learn Accessibility: Free Web Accessibility Course. Use its relevant lessons and examples; the independent Coursya task is not a provider assessment.

Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.

Stage 2 / suggested project week 2

Inspect manually

Understand: Keyboard and assistive-technology checks reveal different issues.

Make: Check tab order, visible focus, labels, heading hierarchy and error association.

Check before moving on: Record actual tools and methods rather than claiming universal device coverage.

Study companion: Google Learn Forms: Free HTML Forms Course. Use its relevant lessons and examples; the independent Coursya task is not a provider assessment.

Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.

Stage 3 / suggested project week 3

Fix the causes

Understand: Remediation should address semantics and behavior.

Make: Correct three issues in a local HTML sample and explain each change.

Check before moving on: A visual label must also be programmatically associated when needed.

Study companion: Google Tech Writing for Accessibility: Free Self-Study Course. Use its relevant lessons and examples; the independent Coursya task is not a provider assessment.

Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.

Stage 4 / suggested project week 4

Retest and report

Understand: An audit result should be bounded by scope.

Make: Retest changed interactions and write a report with remaining issues and limitations.

Check before moving on: Do not issue a legal compliance guarantee from this learning exercise.

Study companion: Google Tech Writing for Accessibility: Free Self-Study Course. Use its relevant lessons and examples; the independent Coursya task is not a provider assessment.

Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.

Stage 5 / suggested project weeks 5–6

Present your portfolio

Assemble the four work products into Accessibility audit, prioritized remediation backlog and retest evidence. Write a README explaining the problem, your assumptions, the decisions you made, tests actually performed and what remains incomplete.

Give a five-minute walkthrough: one minute for the problem, two for the work and evidence, one for trade-offs and one for the next improvement. If you have not implemented a proposed system, label it a design or prototype rather than a deployed solution.

Acceptance: a reviewer can locate each work product, reproduce the key reasoning and identify the limits without a private explanation from you.

Web Accessibility Specialist portfolio roadmap and a review question from the fictional case
The working roadmap for this case. The answer is explained in the self-check below.

The portfolio brief

A workshop registration page has missing labels, weak focus visibility and unclear validation feedback. Audit a local sample, propose fixes and record exactly what was tested.

Deliver: Accessibility audit, prioritized remediation backlog and retest evidence.

Fictional practice inputs
issue id component observation
A 1 Email input No associated label
A 2 Submit button Focus outline removed
A 3 Error message Not connected to invalid field

Use these small inputs to make the reasoning visible. They are not a representative dataset, a real client engagement or evidence of production performance. Where the brief requires additional sample records, create them yourself, label them synthetic and explain why you added them.

Download the portfolio kit

The ZIP includes the case CSV, four stage worksheets, course sequence, decision log, test log, portfolio README template, review rubric and reference reasoning. It is a starter kit for your work, not a completed application, professional report or proprietary project file.

Check your reasoning

An automated scanner reports no errors. Does that establish that keyboard interaction works?

Write your answer and assumptions before opening the reference.

Read the reference reasoning

No. Manually test the task with a keyboard and inspect focus, operation and feedback. Automated checks cover only part of accessibility.

Portfolio review rubric

Criterion Points Evidence required
Problem and scope 4 A clear user, need, boundary and assumptions
Role-specific work 8 2 points for each of the four stage acceptance checks
Reasoning and validation 4 Independent checks, actual results and uncertainty
Communication and reproducibility 4 A usable README, source links and reviewable work products

Aim for at least 16/20 as a self-review target, with no missing stage acceptance check. This is a Coursya practice rubric, not an industry credential or a hiring assessment.

Interview practice

Which issue required manual testing to discover?

Answer using the case: context, your action, evidence and limitation. Describe this honestly as a self-directed project. Do not present fictional organizations, invented interviews or practice results as paid work experience.

Your progress

Use this checklist as a personal study aid. Progress is stored in this browser when local storage is available; it is not an account record or a certificate.

0 of 5 milestones complete

The lessons and projects remain readable without JavaScript. Automatic progress saving requires JavaScript.

Questions before you start

Will this path qualify me for a job?

It helps you study relevant foundations and produce a work sample. Employers may require additional skills, qualifications and experience. Review actual role requirements before applying; no job or certification is guaranteed.

Are all tools and certificates free?

The linked learning routes were selected for free viewing or reading. Follow the separate access and certificate notes on each course. Paid tools and cloud deployment are optional; document a local design when implementation resources are unavailable.

Can I follow this on a phone?

You can read the path and many learning resources on a phone. Coding, detailed spreadsheet work, design tools and mobile-app development are easier or require a suitable computer. The page is designed to reflow; that is not a claim that every physical device has been tested.

Created by Coursya.com. Course references were selected from the published catalog snapshot checked on 13 October 2026. Access can change; consult each current course page. The case, exercises and rubric are original Coursya learning materials.

Share this article

Questions & discussion

Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.

Add to the discussion

Your email address will not be published. Required fields are marked *