This article draws on the Vitaver Playbook’s distinction between signal and noise. Give a reviewer evidence that changes their assessment of your work.
Choose a task with a visible outcome
If you are applying for frontend, QA, or technical product roles, show one accessibility fix someone else can reproduce. Choose a small task with a clear end state, such as booking a fictional appointment or submitting a service request. A reviewer should be able to reproduce the barrier, inspect the change, and complete the same task after applying it. Use your own demonstration or an open-source project that permits the work, with fictional records and no production credentials or user data.
For a useful exercise, build a form with a date field, a required reason, and a confirmation state. Start from a baseline in which invalid fields are indicated only by color and a sticky bar can obscure the next focused control. Write down the expected behavior before changing the code. A keyboard user should be able to reach each control, see their focus, understand which entry needs correction, and complete the submission while keeping valid information they already entered.
Show the steps you actually tested
W3C’s Web Content Accessibility Guidelines 2.2 include criteria for keyboard operation, visible focus, keeping a focused component at least partly visible when page content overlaps it, and text identification of automatically detected input errors. Pick the criteria that fit the specific behavior you are testing. W3C’s Easy Checks can help you organize a first manual review. Treat the checks below as evidence about the selected task and configurations.
- Keyboard path. Start from a known point, navigate forward and backward, and submit without a pointer. Record the keys, the controls reached, where focus becomes hard to see, and what happens after submit. Repeat in the narrow layout where the sticky bar is active.
- Recovery from an error. Enter an invalid date, leave the reason blank, and submit. Record whether you can identify each field in error, what the messages say, and how you return to the affected inputs. Correct the date and submit again with the reason blank. Verify the corrected date stays in place, then enter a reason and confirm the form reaches the success state.
- Assistive technology spot check. Use one browser and screen reader combination you can document. Check whether labels identify fields, invalid entries are understandable and the success state is perceivable. Record what the screen reader conveyed and how you navigated. List the browser, operating system, and assistive technology versions so the next reviewer knows what was tested.
Explain the fix and how it could regress
For example, if the sticky footer covers a focused button on a narrow viewport, fix how the layout reserves space and keep a visible focus indicator. For the error state, add text identifying the problem, associate the field with that text, and make the path back to the input clear. If you add an error summary, test what happens when it appears and whether its links take users to the fields they need. Explain why you chose that interaction and what users must do after the failure.
Keep the patch inspectable. Include one before-and-after record with the task, steps, expected result, observed result, and code change. Add a focused automated test where it can catch a repeatable failure, such as a missing field error after an invalid submit. Keep the manual keyboard and assistive technology steps in the test record. Mark other configurations or flows as untested and give a reviewer a concrete reason to expand coverage.
Present a five-minute walkthrough
In your README or interview packet, link the baseline and final commits and include one issue report with the evidence. Open the demo on the baseline and reproduce the barrier. Switch to the final version and perform the same task. Show the code that changed and identify the person who should own the next verification if the component is shared. For example, the component maintainer can own the regression test while QA verifies the form in the app’s supported configurations before release.
Describe the contribution you made and the limits of the result. If someone else found the original issue or reviewed your approach, say what they did. Before adding the work to your portfolio, ask a peer to follow the instructions without coaching. If they can reproduce the original problem, see the fix in action, and tell what remains untested, you have a work sample a hiring reviewer can evaluate.