Record what automation may miss.
Capture accessibility observations from hands-on testing, with enough page and test context for your team to investigate and follow up.
For manual review.
Describe the issue so someone can repeat the test
Capture the observation and the context needed for another person to investigate it.
01
Page or area
Name the page, section, or control involved.
02
Reproduction steps
Write the sequence that led to the behavior.
03
Expected and actual
State what you expected and what happened.
04
Test context
Add device, browser, assistive technology, or input method as useful.
Capture experiences that need a person
Manual review can help describe behavior that automated checks may not fully evaluate.
Keyboard navigation
Can you reach and use each control?
Focus visibility
Can you see which element is active?
Screen-reader behavior
Are names, instructions, and order clear?
Dynamic interactions
Do dialogs, updates, and feedback work?
Automated checks cannot catch every problem. Always review your website manually.
Review before you decide what to change
A manual note records what you observed. Confirm the behavior and consider its context before choosing a fix.
01
Observe
Test the experience
02
Document
Capture steps and context
03
Review
Confirm and assess impact
04
Follow up
Change and test again
Repeat the relevant test after a change, using the same steps and input method where possible.
Two views of accessibility work
Manual observations complement automated findings. Use both to decide what needs investigation, then verify the experience with the relevant tools and methods.
Automated scans — Supported patterns
Can highlight patterns in content the scanner can access. Results may need human verification.
Manual review — Behavior and context
Can capture keyboard, focus, screen-reader, and interaction observations. Retest after changes.
Make each observation useful to your team
01
Choose a page or task
Decide what experience to review.
02
Test hands-on
Use keyboard, screen reader, or another method.
03
Locate the behavior
Note the page, section, and affected control.
04
Write reproduction steps
Describe the sequence clearly.
05
Record expected behavior
Say what you thought should happen.
06
Record what happened
Keep the observation specific and factual.
07
Add useful test context
Include device, browser, assistive technology, or input if relevant.
08
Review and retest
Decide next steps and verify changes later.
Webflow note: A recorded observation does not change or publish your website; publish updates separately through Webflow.
A quick quality check for manual notes
- Page or area is identified
- Steps can be repeated by a teammate
- Expected and observed behavior are clear
- Relevant device or input context is included
- Notes exclude unrelated sensitive details
- Retest plan is clear after a change
Frequently asked questions
It is a note about an accessibility issue or concern identified through human testing rather than an automated check.
Describe the page or area, the steps to reproduce the behavior, what happened, and what you expected. Include device, browser, assistive technology, or input details when useful.
Manual review can capture observations about keyboard navigation, focus visibility, screen-reader behavior, dynamic content, interaction flows, and other experiences that automated checks may not fully evaluate.
No. Recording a finding documents the observation. Your team must review it, decide on an appropriate change, and test the result.
Yes. Manual review complements automated findings by capturing behavior and context that supported automated checks may not cover.
Keep notes focused on the issue. Do not include personal or sensitive visitor information unless it is necessary and appropriate for your review process.
Not by itself. It records an observation for review. Assess the issue against the relevant accessibility criteria and context before drawing a conclusion.
Repeat the relevant test after making a change. Use the same steps, input method, and assistive technology where possible, and record the outcome according to your team’s process.
No matching FAQs found.