Testing the home page with VoiceOver
A first pass at testing this site’s home page with VoiceOver, the screen reader built into the Mac, before testing it with people with disabilities. The goal was to find barriers early and fix them. Each step is a short video, and each problem found is fixed and tested again in the same video.
In brief
The home page works with a keyboard and a screen reader for most of what was tested. It has a skip link, a clear outline of headings, named regions, and controls that say what they are and what state they are in. Focus is always visible, and Escape always puts it back where you were.
The test found six problems on the page. Five are fixed and live, one of them by working around a bug in Safari, and one, a small one, is still open. One more thing heard was VoiceOver and Safari, not the page.
Fixed A hidden menu held VoiceOver for four presses
WCAG 4.1.2 Name, Role, Value
Just after the Set for you button, VoiceOver said “menu” four times and didn’t move. There was no menu on screen: the closed settings panel still held its four dropdowns, and Safari passed them to VoiceOver. Someone listening would think the page had stopped.
Fixed: the panel is now left empty while it is closed. Live since October 16, 2026.
Fixed Changing a setting wasn’t announced
WCAG 4.1.3 Status Messages
Turning the drawings off worked, but nothing said so. The note confirming it was only on screen, so someone listening had to go and look for it.
Fixed: a status line now says what each change did. VoiceOver says “Drawings are off and their captions go with them.” Live since October 17, 2026.
Fixed Describe this page read only its name when it opened
Not a WCAG failure on its own; it stops the feature doing its job
When the dialog opened, VoiceOver read its name and heading, but not the description under them, the picture of the page, until you went looking. (An earlier draft of this report said the dialog opened in silence; that came from the test runner, not the page.)
Fixed: the heading now carries the description, so VoiceOver reads it the moment the dialog opens. Re-tested on mpaiva.com. Live since October 17, 2026.
Fixed Essay links in the drawing strip read their title twice
WCAG 2.4.4 Link Purpose is met; a listening cost
In the band of drawings, each link read its essay’s title twice, then the whole summary. The links made sense, but a list of them was slow to get through.
Fixed: each link now says its title once, then the summary. Live since October 16, 2026.
Open The strip’s preview is read again after its links
No WCAG failure; a listening cost
Reading the page item by item, the preview card for the drawing in the middle of the strip is read after the strip’s links, so one essay’s title and summary are heard a third time.
Open: hiding the preview from screen readers would stop it, while its summary still reaches the link. Not done yet.
Fixed Old focus rings stayed on screen as VoiceOver moved
WCAG 2.4.7 Focus Visible
As VoiceOver jumped from link to link, Safari left focus rings behind on links it had already passed, and kept the skip links showing after focus left them. Someone watching couldn’t tell which link had focus. The page’s styles were right: this is a bug in Safari, and a real Tab press doesn’t show it.
Fixed: a small script now makes Safari redraw whatever just lost focus. Tested with VoiceOver over the same ten links: ten rings before, one after. Live since October 17, 2026.
Not the page Choosing from a dropdown reads the old value first
VoiceOver in Safari
When you pick a new value in a dropdown, VoiceOver first reads the value it had before. This happens with Safari’s standard dropdown, not because of the page; the status line now follows it with the right answer.
About these videos
Two voices. The tester (af_heart) drives VoiceOver and the keyboard and says what she hears. The reviewer (am_puck) names the guideline a problem falls under, explains why it matters, and says what changed in the code. Both are synthetic voices; the captions label them Tester and Reviewer.
What these videos are. VoiceOver in Safari, on macOS 27, driven by a script so each test can be run again the same way. What you hear from VoiceOver is what it said. The narrator is a synthetic voice, describing what a tester listens for.
What they are not. An audit, or a claim that the site conforms to WCAG. It is one specialist, one screen reader and one browser, on one page. Nobody who uses a screen reader every day took part: that comes next, in the recommendations.
Captions. Every video has captions for both voices on screen. They are also in each video as a captions track, and as a file you can download, with a transcript under each video.
Where they were filmed. On copies of this site built from just before and just after each fix, served from my own Mac. The last check of Describe this page was filmed on the live site.
Overview
The tester and the reviewer introduce themselves and how they split the work, then the goal of the test, why it is a first pass, the six steps, and how each video goes: find, fix, test again.
Read the transcript
- Tester: Hello. This is the home page of Marcelo Paiva's site, in Safari, with VoiceOver on. I'm the tester. I'll drive VoiceOver and the keyboard, and tell you what I hear.
- Reviewer: And I'm the reviewer. When something sounds wrong, I'll name the guideline it falls under, and explain why it matters to the person it stops. When it's fixed, I'll say what changed in the code.
- VoiceOver: Marcelo Paiva — Design Engineer web content is in the VoiceOver cursor
- Tester: The goal is simple. Can someone using VoiceOver understand this page, find what they need, and use its controls, without seeing it?
- Reviewer: This is a first pass, before testing with people with disabilities. It finds problems early, so they can be fixed, and so the time with people goes on what only they can tell us.
- Tester: I test in six steps. First, I inspect the page structure in the code. Second, the keyboard on its own. Third, a reading pass with the screen reader, top to bottom. Fourth, jumping by headings, landmarks and links. Fifth, the controls themselves. And sixth, real tasks, start to finish.
- Reviewer: Each step gets its own short video. When we find a problem, we fix it, and test again in the same video. At the end, we list what still needs testing with people.
The six steps
Step 1: the structure, before the screen reader
The goal: understand the intended structure and find obvious semantic problems.
Safari’s Web Inspector, before any screen reader: what the page tells assistive technology. The Set for you button says it is collapsed and which panel it controls. That panel is hidden, but its four dropdowns are still inside it, in the page.
Read the transcript
- Tester: Step one, before any screen reader: the structure in the code. I'm opening Safari's Web Inspector, and making it larger, to see what this page tells assistive technology.
- Keyboard: Command-Option-I: the Web Inspector
- Keyboard: Command-Plus: makes the Inspector larger
- Keyboard: Command-Plus: larger again
- Keyboard: Command-Option-C: the Console
- Keyboard: Command-K: clears the Console
- Keyboard: Typed inspect(document.querySelector('button[aria-expanded]'))
- Tester: This is the Set for you button. Its attributes say aria-expanded, false, and aria-controls points at the panel it opens.
- Reviewer: That's what a screen reader needs. Expanded, false, is announced as collapsed, so the person knows there's more behind it.
- Keyboard: Command-Option-C: back to the Console
- Keyboard: Command-K: clears the Console
- Keyboard: Typed panel = document.getElementById(document.querySelector('button[aria-expanded]').getAttribute('aria-controls'))
- Keyboard: Typed [panel.hidden, panel.querySelectorAll('select').length]
- Tester: That panel is marked hidden, and the four dropdowns are still inside it, in the page.
- Reviewer: Hidden content should stay out of a screen reader's way. Nothing's wrong yet… but it's the first thing to listen for, in the reading pass.
- Keyboard: Command-0: the Inspector back to normal size
- Keyboard: Command-Option-I: closes the Web Inspector
What it found: Something to listen for, not yet a problem: hidden content should stay out of a screen reader’s way. The reading pass in step 3 hears that it doesn’t.
Step 2: the keyboard on its own
The goal: the page works without a mouse, before the screen reader comes in.
No screen reader and no mouse: real key presses, with the focus ring showing where each one lands. The skip link skips the header, and Shift-Tab retraces it in screen order. Set for you opens with Return; typing “n” in the Drawings dropdown chooses “not at all”, and the drawings go. Escape puts focus back on the button, and Space presses Pause motion.
Read the transcript
- Tester: Step two, the keyboard on its own. No screen reader and no mouse, just the keys a keyboard user presses, and the focus ring that shows where I am.
- Keyboard: Tab → link, Skip to content
- Tester: The first stop is a skip link. I'll press Return, then Tab, to see whether it really skips the header.
- Keyboard: Return → main
- Keyboard: Tab → link, Read the writing
- Tester: I'm on Read the writing, past the whole header. The skip link works.
- Reviewer: That's WCAG 2.4.1, Bypass Blocks. Without it, a keyboard user tabs through every link in the header, on every page.
- Tester: Now back up, with Shift-Tab.
- Keyboard: Shift-Tab → button, Pause motion
- Keyboard: Shift-Tab → button, Set for you, collapsed
- Tester: Pause motion, then Set for you: the same order as on screen, and the focus ring follows every time.
- Reviewer: That's 2.4.7, Focus Visible. If you can't see where focus is, using a keyboard is guesswork.
- Tester: I'll open it with Return.
- Keyboard: Return → button, Set for you, expanded
- Keyboard: Tab → pop-up button, Drawings, in calm color
- Tester: It opens, and Tab takes me to the first setting, the drawings. With a dropdown focused, I can type the first letter of a choice. N, for not at all.
- Keyboard: Typed n
- Keyboard: Focus is on → pop-up button, Drawings, not at all
- Tester: The dropdown says not at all, and the drawings are gone. Now Escape.
- Keyboard: Escape → button, Set for you, collapsed
- Tester: Escape closes the panel, and puts focus back on the button. Next, Pause motion.
- Keyboard: Tab → button, Pause motion
- Keyboard: Space → button, Pause motion, pressed
- Tester: Space presses it, and the button now says pressed.
- Reviewer: Tab, Shift-Tab, Return, Escape, Space, and typing to choose. Every control works without a mouse, and focus is never trapped or lost. For what was tested, the goal of step two is met. WCAG 2.1.1, Keyboard, holds here.
What it found: For everything tested here, the page works without a mouse. WCAG 2.1.1 Keyboard and 2.4.7 Focus Visible hold.
Step 3: the reading pass, then the fix
The goal: the experience of discovering and understanding the page.
VoiceOver reads the home page from the top, one item at a time. Just after the Set for you button it says “menu”, four times, and doesn’t move. There is no menu on screen. Then the same steps on the fixed page.
Read the transcript
- Tester: Step three, the reading pass. The home page from the top, in Safari with VoiceOver, the way someone who can't see the screen would meet it.
- VoiceOver: Skip to content visited link is in the VoiceOver cursor
- Tester: The first thing it reaches is a skip link, which is a good start. Now I'll read the header one item at a time.
- VoiceOver: Describe this page dialog pop up button
- VoiceOver: banner
- VoiceOver: visited link Marcelo Paiva
- VoiceOver: Main navigation
- VoiceOver: list 5 items
- VoiceOver: link Writing 1 of 5
- VoiceOver: link Work 2 of 5
- VoiceOver: link Signal 3 of 5
- VoiceOver: link Tools 4 of 5
- VoiceOver: link Resume 5 of 5
- VoiceOver: end of list
- VoiceOver: end of Main navigation
- VoiceOver: Set for you collapsed button
- Tester: Set for you… a button, and it tells me it's collapsed. That's what I want to hear. Next item.
- Reviewer: A name, a role, and a state. That's what WCAG 4.1.2 asks for.
- VoiceOver: menu
- VoiceOver: menu
- VoiceOver: menu
- VoiceOver: menu
- Tester: It says menu… and again… and again. Four presses, and it hasn't moved past it.
- Reviewer: There's no menu on screen. The settings panel is closed, but its four dropdowns are still reaching VoiceOver. That's a problem under WCAG 4.1.2, Name, Role, Value. If you're listening, it sounds like the page has stopped, right at the control that sets the site up for you.
- Reviewer: The fix: the panel is now left empty while it's closed. Here's the same page after that change.
- Tester: I'll go straight to Set for you.
- VoiceOver: Set for you collapsed button
- Tester: Collapsed, the same as before. Next item.
- VoiceOver: Pause motion toggle button
- Tester: That's Pause motion, the next button on the screen. The silence is gone.
- Reviewer: 4.1.2 holds here.
What it found: A problem under WCAG 4.1.2 Name, Role, Value, fixed: the panel is now empty while it is closed, and VoiceOver goes from Set for you straight to the next button. WCAG 4.1.2 holds.
Step 4: structural navigation, then the fix
The goal: finding information without reading the whole page.
Jumping by headings, landmarks and links instead of reading everything. The heading outline holds and every landmark has a name. In the drawing strip, each link reads its essay’s title twice, then the whole summary, and Safari leaves focus rings behind on links already passed. Then the same links on the fixed page.
Read the transcript
- Tester: Step four, structural navigation. Someone using a screen reader rarely reads every item. They jump, by headings, by landmarks, and by links. First, headings.
- VoiceOver: heading level 1 I design experiences and ship accessible code that runs them.
- VoiceOver: heading level 2 LATEST WRITING
- VoiceOver: Last heading heading level 2 LATEST WRITING
- VoiceOver: heading level 3 link Designers don't need Figma anymore
- Tester: One level one, a level two for the latest writing, and the essays under it at level three. The outline holds, all the way down.
- Reviewer: That's WCAG 1.3.1, Info and Relationships. Headings are how someone using a screen reader skims a page.
- Tester: Now landmarks.
- VoiceOver: banner visited link Marcelo Paiva
- VoiceOver: Last landmark banner
- VoiceOver: Main navigation
- VoiceOver: main MARCELO PAIVA group
- VoiceOver: More essays, by their drawings region
- VoiceOver: LATEST WRITING region
- Tester: Each region is announced with a name, so I can tell them apart and jump straight to the one I want.
- Tester: And links. In a list of links, each one has to make sense on its own.
- VoiceOver: Marcelo Paiva visited link
- VoiceOver: Writing link
- VoiceOver: Work link
- VoiceOver: Signal link
- VoiceOver: Tools link
- VoiceOver: Resume link
- VoiceOver: Read the writing link
- VoiceOver: See the work link
- VoiceOver: How do you keep something powerful approachable? link
- VoiceOver: How do we learn a spec nobody reads? How do we learn a spec nobody reads? Nobody learns a language by reading its dictionary, and I think that explains most of what is wrong with how we teach accessibility. link
- VoiceOver: Last link How do we learn a spec nobody reads? How do we learn a spec nobody reads? Nobody learns a language by reading its dictionary, and I think that explains most of what is wrong with how we teach accessibility. link
- Tester: The essays in the drawing strip read their title twice, and then the whole summary.
- Reviewer: Each link still makes sense, so WCAG 2.4.4 is met. But a list of links is how people scan a page, and this one takes several seconds per link. It's worth fixing.
- Tester: Something else, on screen. As I moved through the links, rings stayed behind on links I'd already left. Even now, See the work still has one, though I'm in the drawing strip.
- Reviewer: That's WCAG 2.4.7, Focus Visible. Someone who sees the screen while using VoiceOver, or a person sitting beside them, needs to find focus at a glance. The page's styles are right: this is a bug in Safari. But people still see it, so the page works around it.
- Reviewer: Two fixes. Each link is now described by its summary alone, and a small script makes Safari redraw whatever just lost focus. Here's the same list after both changes.
- VoiceOver: Last link Skip to content link
- VoiceOver: Marcelo Paiva visited link
- VoiceOver: Writing link
- VoiceOver: Work link
- VoiceOver: Last link Work link
- VoiceOver: Signal link
- VoiceOver: Tools link
- VoiceOver: Resume link
- VoiceOver: Read the writing link
- VoiceOver: See the work link
- VoiceOver: How do you keep something powerful approachable? link
- VoiceOver: How do we learn a spec nobody reads? Nobody learns a language by reading its dictionary, and I think that explains most of what is wrong with how we teach accessibility. link
- VoiceOver: Should a design system have a file written for machines? Writing rules for a reader who cannot ask a follow-up question turned out to be the clearest thinking I have done about my own design system. link
- Tester: Now each essay says its title once, then its summary, and only the link I'm on has a ring.
What it found: Headings: WCAG 1.3.1 holds. Links: WCAG 2.4.4 is met, but the doubled titles made the list slow to get through. Focus: stale rings fail WCAG 2.4.7 on screen; the cause is a Safari bug. Fixed: each link now says its title once, then its summary, and only the current link has a ring.
Step 5: the Set for you control
The goal: controls are understandable and usable, not merely discoverable.
The settings button, closely: its name, role and state, what happens when it opens, each setting inside it, and where Escape leaves you.
Read the transcript
- Tester: Step five, the controls. Finding Set for you isn't enough. It has to say what it is, what state it's in, and work from the keyboard.
- VoiceOver: Set for you collapsed button
- Tester: Set for you, a button, collapsed.
- Reviewer: Name, role and state, all three. That's WCAG 4.1.2.
- VoiceOver: Set for you expanded button
- Tester: When I press it, the state changes to expanded, and VoiceOver says so. Now the panel, one item at a time.
- VoiceOver: THIS SITE, SET FOR YOU group
- VoiceOver: THIS SITE, SET FOR YOU
- VoiceOver: Show the drawings
- VoiceOver: in calm color Drawings Drawings collapsed pop up button, group
- VoiceOver: , with the theme
- VoiceOver: following my device Theme collapsed pop up button, group
- VoiceOver: , and motion
- VoiceOver: allowed Motion collapsed pop up button, group
- VoiceOver: . The home page as
- VoiceOver: a list of essays Home page collapsed pop up button, group
- Tester: The settings read as a sentence, and each dropdown has its own name… Drawings, Theme, Motion, Home page… with its current value first.
- VoiceOver: Set for you collapsed button banner
- Tester: And Escape closes it, and puts me back on the button, collapsed again.
- Reviewer: Focus isn't lost. Where focus goes when a panel or a dialog closes is one of the most common keyboard problems, and here it's right.
What it found: WCAG 4.1.2 holds: the button says collapsed and expanded, every dropdown has a name and says its value, and Escape puts focus back on the button.
Step 6: a real task, then the fix
The goal: people can complete what they came to do.
Turning the drawings off with VoiceOver, start to finish. It works: the drawings go, for VoiceOver too. But nothing says so: the note that confirms it is only on screen. Then the same task on the fixed version, where the change is announced.
Read the transcript
- Tester: Step six, a real task. I'll turn the drawings off, start to finish, with VoiceOver… and find out whether it tells me it worked.
- VoiceOver: Set for you collapsed button
- VoiceOver: Set for you expanded button
- VoiceOver: THIS SITE, SET FOR YOU group
- VoiceOver: THIS SITE, SET FOR YOU
- VoiceOver: Show the drawings
- VoiceOver: in calm color Drawings collapsed pop up button, group
- Tester: There's the Drawings dropdown, set to calm color. I'll open it, and choose not at all.
- VoiceOver: menu 3 items ✓ in calm color
- VoiceOver: in full color
- VoiceOver: not at all
- VoiceOver: in calm color Drawings Drawings collapsed pop up button, group
- Tester: When I choose it, VoiceOver reads the old value… calm color.
- Reviewer: That seems to be VoiceOver in Safari, with a standard dropdown. It isn't the page.
- Tester: I'll ask again to hear what's set.
- VoiceOver: not at all Drawings collapsed pop up button, group is in the VoiceOver cursor
- Tester: Not at all. It worked… but nothing told me. The panel has a note about it, so I'll go and find it.
- VoiceOver: , with the theme
- VoiceOver: following my device Theme collapsed pop up button, group
- VoiceOver: , and motion
- VoiceOver: allowed Motion collapsed pop up button, group
- VoiceOver: . The home page as
- VoiceOver: a list of essays Home page collapsed pop up button, group
- VoiceOver: .
- VoiceOver: end of THIS SITE, SET FOR YOU group
- VoiceOver: Your device is set to dark, so this site is too. Drawings are off, and their captions go with them. Nothing else on a page depends on them.
- Tester: There it is. Drawings are off, and their captions go with them.
- Reviewer: That's a status message, and it's only on screen: it should be announced, without going to look. That's a problem under WCAG 4.1.3, Status Messages. Someone listening can't tell whether their choice worked.
- VoiceOver: Set for you collapsed button
- VoiceOver: link See the work
- VoiceOver: LATEST WRITING region
- Tester: And after See the work, VoiceOver goes straight to Latest writing. The drawings are gone for a listener too.
- Reviewer: The fix: a status line that says what each change did. Here's the same task on the fixed version, the one that's live now.
- VoiceOver: Set for you collapsed button
- VoiceOver: Set for you expanded button
- VoiceOver: THIS SITE, SET FOR YOU group
- VoiceOver: THIS SITE, SET FOR YOU
- VoiceOver: Show the drawings
- VoiceOver: in calm color Drawings collapsed pop up button
- VoiceOver: menu 3 items ✓ in calm color
- VoiceOver: in full color
- VoiceOver: not at all
- VoiceOver: in calm color Drawings Drawings collapsed pop up button, Drawings are off and their captions go with them.
- Tester: There it is: drawings are off, and their captions go with them, said straight after the choice.
- Reviewer: 4.1.3 holds here.
What it found: A problem under WCAG 4.1.3 Status Messages, fixed: VoiceOver now says “Drawings are off and their captions go with them.” straight after the choice. WCAG 4.1.3 holds.
Extra: Describe this page, then the fix
A screen reader reads a page in a line, one item at a time; it doesn’t say what the page looks like. Describe this page puts the layout into words, so someone who is blind gets a map: what is on the page before reading all of it, and where things are when a sighted colleague points to “the column on the right”.
Read the transcript
- Reviewer: One more feature to test: Describe this page. A screen reader reads a page one item at a time, in a line. It doesn't say that the essays fill most of the page, or that a narrow column sits beside them.
- Reviewer: For someone who's blind, a picture of the layout is a map. It says what's on the page before reading all of it, and where things are when a sighted colleague says it's in the column on the right.
- VoiceOver: system has new window
- VoiceOver: Describe this page dialog pop up button
- Tester: It's the second thing on the page, right after the skip link. I'll press it.
- VoiceOver: The home page web dialog with 9 items heading level 2 The home page
- Tester: It says the dialog's name, The home page, and its heading… and stops there. The picture of the page isn't read until I go looking.
- VoiceOver: Close button
- VoiceOver: This is the front page of a magazine. The newest essays take most of the page, and a narrower column beside them lists everything else.
- VoiceOver: heading level 3 From top to bottom
- VoiceOver: list 7 items
- VoiceOver: 1
- VoiceOver: At the top, the site header: my name, which goes home, then links to Writing, Work, Signal, Tools and Resume, then Set for you, where you choose the drawings, theme and motion. Beside it is a button that pauses everything that moves.
- Tester: It starts with a picture: the front page of a magazine, the newest essays taking most of the page, and a narrower column beside them. Then it walks the layout from top to bottom.
- Reviewer: What it says is useful. But on opening it only says its name, so someone has to explore to find out what the page is like. That's not a guideline failure, but it holds back the whole point of the feature.
- VoiceOver: At the top, the site header: my name, which goes home, then links to Writing, Work, Signal, Tools and Resume, then Set for you, where you choose the drawings, theme and motion. Beside it is a button that pauses everything that moves.
- Reviewer: The fix, now live: the heading carries the description, so it's read the moment the dialog opens. Same steps, on the live site.
- VoiceOver: link Skip to content
- VoiceOver: Describe this page dialog pop up button
- VoiceOver: The home page web dialog with 9 items heading level 2 The home page This is the front page of a magazine. The newest essays take most of the page, and a narrower column beside them lists everything else.
- Tester: This time it reads the picture straight away: the front page of a magazine, the newest essays taking most of the page.
- Reviewer: Now the feature does its job from the first second. Whether the description helps is for blind people to tell us.
- VoiceOver: Describe this page dialog pop up button
What it found: The description works, but on opening VoiceOver read only its name and heading. Fixed: on the live site, it reads the picture of the page straight away.
What needs testing with people with disabilities
A screen reader run by script shows whether things work. It cannot show whether they are good to use. These are the areas where only the people they are for can say.
Describe this page. Whether a written description of the layout actually helps someone build a picture of the page, whether it says too much or too little, and whether people find the button where it is. A screen reader can show the dialog works; only the people it is for can say it helps.
Who to test with: blind people who use a screen reader every day, on VoiceOver and on JAWS or NVDA.
Other screen readers and devices. This pass used VoiceOver in Safari only, and its biggest finding came from how Safari passes hidden content to VoiceOver. JAWS and NVDA on Windows, VoiceOver on iPhone and TalkBack on Android behave differently.
Who to test with: people who use each of them daily, on their own devices and settings.
Set for you, as a sentence of settings. The panel reads its settings as a sentence, with a dropdown in each part. Whether that reads naturally, and whether the new announcements are enough to know what changed, is a question of experience, not of code.
Who to test with: screen-reader users, and people with cognitive or learning disabilities.
Motion. The band of drawings drifts and the background moves. The pause button and reduced-motion setting were checked to work, not whether they are found in time or whether the motion is comfortable before they are.
Who to test with: people with vestibular disorders, and people for whom motion makes reading harder, such as some people with ADHD.
Zoom and magnification. The header stays at the top of the screen, and some text sits over moving color that the site measures but doesn’t yet grade. How that feels at high zoom or under a screen magnifier wasn’t part of this pass.
Who to test with: people with low vision who use browser zoom or a screen magnifier.
Voice control and switch access. Controls were checked for names a screen reader announces, not for names people would say aloud, and the home page has more than fifty stops from top to bottom for someone moving one step at a time.
Who to test with: people who use Voice Control or switch access, and others with motor disabilities.
The collage layout. Set for you can swap the home page’s list of essays for a collage of drawings. This pass tested the list only.
Who to test with: screen-reader and keyboard users.
The recommendations, on screen
Each area that needs testing with people with disabilities, shown on the page as it is named: the Describe this page dialog, the Set for you sentence, the moving drawings, the page zoomed in, and the Home page setting that switches to the collage.
Read the transcript
- Reviewer: Last, what this first pass can't tell us. A screen reader shows whether things work as built, not whether they help the people they're for. These need people with disabilities, on their own devices and settings. I'll show each one on the page as we name it.
- Tester: First, Describe this page. I'll press Tab twice, to its button in the skip links, then Return to open it.
- Keyboard: Tab → link, Skip to content
- Keyboard: Tab → button, Describe this page
- Keyboard: Return → heading, The home page
- Tester: A dialog sits over the dimmed page, titled The home page: one sentence comparing it to the front page of a magazine, then a numbered list of its parts, top to bottom, and a Close button at the top. Does a description like this help someone picture the page? Is it too long, or too short? Blind people who use a screen reader every day should tell us, on VoiceOver and on JAWS or NVDA.
- Tester: I'll press Escape to close it.
- Keyboard: Escape → button, Describe this page
- Reviewer: Second, other screen readers and devices. We're back on the home page. This pass used VoiceOver in Safari only, and its biggest finding came from how Safari passes hidden content to VoiceOver. JAWS, NVDA, VoiceOver on iPhone and TalkBack all behave differently.
- Tester: Third, Set for you. I'll Tab across the header: my name, Writing, Work, Signal, Tools and Resume, then Set for you, and press Return to open it.
- Keyboard: Tab → link, Marcelo Paiva
- Keyboard: Tab → link, Writing
- Keyboard: Tab → link, Work
- Keyboard: Tab → link, Signal
- Keyboard: Tab → link, Tools
- Keyboard: Tab → link, Resume
- Keyboard: Tab → button, Set for you, collapsed
- Keyboard: Return → button, Set for you, expanded
- Tester: A small panel drops down with one sentence: show the drawings in calm color, with the theme following my device, and motion allowed. The home page as a list of essays. Each of those choices is a dropdown. Whether a sentence like that feels natural, and whether the announcements are enough, is for screen reader users, and people with cognitive or learning disabilities, to say.
- Tester: Escape closes the panel.
- Keyboard: Escape → button, Set for you, collapsed
- Reviewer: Fourth, motion. Under the introduction, a band of drawings drifts slowly sideways, and thin lines and points move across the dark background behind the heading. A pause button sits beside Set for you. It works… but is it found in time, and is the motion comfortable before it is? People with vestibular disorders can tell us.
- Tester: Fifth, zoom and magnification. I'll zoom in, pressing Command-Plus three times.
- Keyboard: Command-Plus: zooms the page
- Keyboard: Command-Plus: zooms the page
- Keyboard: Command-Plus: zooms the page
- Tester: The heading now fills most of the width, the header stays across the top, and the text sits over the moving background. People with low vision who use zoom or a screen magnifier should try it.
- Tester: Command-Zero puts the page back to its normal size.
- Keyboard: Command-0: back to actual size
- Reviewer: Sixth, voice control and switch access. Names were checked for what a screen reader says, not for what people say aloud, and the home page has more than fifty stops for someone moving one step at a time.
- Tester: And last, the collage. I'll press Return to open Set for you again, then Tab past Drawings, Theme and Motion, to its last dropdown.
- Keyboard: Return → button, Set for you, expanded
- Keyboard: Tab → pop-up button, Drawings, in calm color
- Keyboard: Tab → pop-up button, Theme, following my device
- Keyboard: Tab → pop-up button, Motion, allowed
- Keyboard: Tab → pop-up button, Home page, a list of essays
- Keyboard: Focus is on → pop-up button, Home page, a list of essays
- Tester: The Home page dropdown reads a list of essays. Choosing a collage of drawings there turns the home page into a field of pictures. This pass tested the list only.
- Tester: Escape closes it.
- Keyboard: Escape → button, Set for you, collapsed
- Tester: That's the end of the first pass. Six problems found on the page: five fixed and live, and one still open.
- Reviewer: The next test is with people.