Skip to main content

Free CometWeb ebook

Website accessibility starts with a task people can finish.

Open a menu. Fill in a form. Correct an error. This guide helps you find barriers in everyday journeys and describe what the team should change and how to check the fix.

29 pages, PDF + HTML, in English

Cover: Web accessibility in practice

In the guide

Before-and-after component examples

Explore the guide and materials

Get the ebook and worksheets

We will send a link to verify your email address.

Use your regular mailbox. Temporary email addresses are not supported.

We use these details to provide the materials. No newsletter subscription. Privacy policy.

Materials prepared by CometWeb.edition 1.3

Where should a website accessibility check begin?

Choose one important task and try completing it with a keyboard. Check whether you can see the focused element, operate controls and return from an open dialog. Record where progress stops.

Then review form labels, instructions and error messages. Visible text beside a field is not enough to assess its accessibility. The guide connects the symptom to reproduction steps, a relevant criterion and a follow-up check.

Method example
Contact form
Email address
anna@example.org
Send enquiry

The field has focus. Can you see it?

Compare two states

Accessibility in specific interface elements.

Leave with a documented barrier and a clear condition for retesting.

Method example
Use the keyboard
Contact form
Journey starts here

Keyboard and visible focus

Check access to controls and complete a task without a mouse. See why something that looks like a button may be skipped.

Method example
Contact form
Keyboard test result
Connect the starting point to the result.

Labels, names and instructions

Work through fields, icons and close buttons. Distinguish visible text from information communicated to assistive technology.

Method example
Before
!Evidence missing
After checking
Result recorded

Text, zoom and messages

Check readability and the page at increased zoom. Describe a form error so the location and correction are clear.

Method example
Describe the barrier
✓What was checked
✓Evidence and result
Next action
Ready to share with the team

Reporting and retesting

Connect the barrier to a journey and criterion. Repeat the task after deployment instead of relying on a completion claim.

Page 8: form field labels. Visible text alone is not enough.
Page 8: form field labels. Visible text alone is not enough.Open the excerpt at full size

Put the mouse aside. Keep a concrete result.

The public excerpt examines form labels. The package also includes before-and-after component examples. Compare their behaviour, then check the same kind of element on your website.

  • Choose a task, such as sending an enquiry.
  • Record the keys used and where progress stops.
  • Report the barrier and repeat the journey after the fix.
Get the free ebook

Read it. Put it to work.

Free materials in English. Verify your email, choose a format and download your files.

PDF guide

29 pages. For reading, saving for later or printing.

Online reading version

HTML for reading in your browser. Revisit the guide on your phone or computer.

Barrier report and component examples

Connect reproduction steps, evidence and the expected result. The examples show specific interface behaviours that can be compared.

A shared language for design, code and delivery.

Designers get interface checks, developers get behaviour examples and reviewers get a way to verify fixes. The material starts a review; it does not replace a complete audit or user research.

No. The exercises help you find and describe selected barriers. They are not a certificate or a complete accessibility audit, and they do not replace research with users.

About the publisher: CometWeb

Find one barrier. Give your team an issue they can act on.

Get the free ebook

Free, no newsletter subscription