I do accessibility reviews for our own product, not as a specialist hired from outside, but as the engineer who was willing to keep a checklist and a copy of a screen reader on their laptop. For a long time my review notes were a mess of screenshots and half sentences I had typed with one hand while listening with both ears. I would hear a problem, reach for the keyboard, lose my place in the page, and then write “button, somewhere near checkout, unclear” — which is a terrible ticket. In May I started recording the walkthrough as I spoke, and I ran audio to text afterward so the ticket could quote the moment I was actually in, not the moment I thought I had been in. This is that workflow, including the parts that did not work.
I only record my own voice, plus the screen reader’s output if it is coming through the same headphones I have looped back on purpose. I do not record teammates who happen to be in the room, and I do not record users. If someone sits in on a review, the recorder stays off unless they agree, and even then I prefer they not sit in. This is a private engineering artifact, not a research session.
The walkthrough I actually run
I use the same route every time, because a random wander makes a worse transcript and a worse ticket. Mine is boring on purpose:
- Land on the page with the screen reader running, and say the page title I hear
- Move through the main landmarks, and say each one out loud if the software does not
- Try the primary task (in this case, starting a checkout)
- Try the error state (submit the form empty)
- Stop, and say “end of walkthrough”
The last line is for me. It gives me a marker when I search the text later. I used to forget to say where I was on the page. The first transcript I got was a stream of complaints with no headings, and I had to play the audio back anyway. Now I announce the place: “I am on the shipping form. The field after postal code has no spoken label.” That sentence is already most of a ticket title.
I record with the in-browser recorder sometimes, and with a local m4a when I want the file next to the video I take of the session. Both have worked. The tool accepts thirty-plus audio and video formats, and it also accepts a public YouTube or TikTok or X link, which I do not use here; these reviews are not public videos. A typical walkthrough is fifteen or twenty minutes. In Standard mode that is 15 or 20 credits, against 240 free credits a day when I am signed in. I leave speaker identification off when it is only my voice. If the screen reader is in the same file and I want those lines marked separately, I will turn it on, at two credits a minute, and then I still relabel anything that looks off.
A one-hour file is described as often finishing in about two minutes, depending on quality and language. These short files are done before I have finished closing the extra tabs I opened for the review.
From transcript to tickets
I export SRT or VTT, not just a wall of TXT, because I want a timestamp I can paste into the ticket and, if needed, match to the video. I do not need a subtitle file for a public player. I need “at 06:12 I was on the shipping form.”
My issue template is small. I have pasted it at the bottom of this post. The only parts I take from the transcript are the spoken description and the timestamp. The rest — browser, screen reader version, expected result, actual result — I fill in by hand, looking at the page. I do not let the text invent an expected result. It is very willing, if I am not careful, to sound more precise than I was in the moment.
Accuracy is described as up to 99% on clear recordings. A headset mic in a quiet room is close to that. The screen reader’s voice can still be chopped, especially when I talk over it, which I try not to do and sometimes do. Control names, in particular, I check against the page. If I heard “continue” and the accessible name is “Continue to payment,” the ticket uses the name on the page.
I do not use an automatic summary for this. A summary of a walkthrough tends to smear three issues into one paragraph and drop the timestamp. I want three tickets, or one ticket with three numbered steps, and I want the clock on each.
When the tickets are filed, I delete the audio and the transcript from my machine and from the library in the tool. The tickets are the record. If a reviewer wants to hear the stretch, they can ask me to reproduce it; they should not need a copy of my voice sitting in a folder.
Here is the template I actually use:
## Title
[page] [control] [what I heard or didn’t hear]
## Environment
- Browser:
- Screen reader and version:
- URL (internal):
## Timestamp
- Walkthrough clock: (from the SRT cue)
## Steps
1.
2.
## Expected
## Actual
## Notes
- Quote from my spoken notes, checked against the page:
The first week I used this, I filed four issues from a single checkout walkthrough, and two of them were things I would have written as “confusing form” and then never been able to reproduce. One was a heading level that I had felt, vaguely, and then could point to at 03:41. The other was an error message that was visible but never spoken. I had heard myself say “I submitted, and nothing was announced,” which is a better ticket than “error??” with a screenshot of a red box.
What I will not do with this
I will not attach the transcript to a public issue tracker. I will not record a customer. I will not treat this as a substitute for testing by people who use a screen reader every day. This is a way for me, as an engineer, to keep my place and to write a ticket that another engineer can follow. It is not a complete accessibility practice, and I do not want it read as one.
If you already do a spoken walkthrough and you already lose your notes, you can transcribe the walkthrough and file from the cues instead of from the mess on your second monitor. Try it on one route, one day, and compare the tickets to the last set you wrote from one-handed typing. Mine were shorter, and they were easier to reopen a month later.
I still keep the checklist. The recorder does not know the route. I do, and I still forget a step when I am annoyed at a dropdown. The difference is that when I say “end of walkthrough” and something is missing, I can see the gap in the text and go back, instead of discovering the gap in front of a reviewer.
If you try audio to text for this, start with your own voice, one route, and a template that already has a timestamp field. The file is a means to a ticket. The ticket is the thing that should last.
Disclosure: I'm involved with AudioToText, the tool linked in this post. The walkthrough route, the template, and the checkout examples are from my own reviews. I have not included product UI, customer data, or a real internal URL.
Top comments (0)