Accessibility review record

Updated July 25, 2026

This page documents the assistive-technology review behind Rung's accessibility statement: what is verified, how it was verified, what the screen reader announced, and what remains open. Each section carries the date it was verified.

Screen-reader review: TalkBack (Android)

Verified July 24, 2026. TalkBack walked the live product the way a person using it would: the landing page, the situation chooser, the interview's first questions, the occupation search, the finished resume, the export step, and the Spanish interface. Navigation used TalkBack's own gestures, and every announcement TalkBack composed was recorded verbatim from its speech output.

What TalkBack announced, as recorded

The interview's first question, with its structure spoken:

"main. First, a few questions. heading 1. * marks a question you need to answer before moving on. What's your work situation? heading 2. So I can ask the right questions."

The occupation search, while typing "cashier":

"Edit box. Job title. A few letters to see matching jobs." … then, as results arrived: "8 suggestions, use up and down arrows to choose."

The export step:

"Ready to go with you. dialog." … the file's real name … the acknowledgment sentence in full, announced as a checkbox with its checked state, and, while unticked, the save control's own explanation: "Tick the box first, then save your file."

The Spanish interface, switched through the language menu:

"main. El trabajo que ya hiciste es suficiente. heading 1. Nueve situaciones cambian lo que se pregunta." … "¿Qué trabajo buscas? status. Gratis. Sin cuenta. Tu currículum se queda en tu teléfono."

The animated product demo on the landing page stayed silent throughout: it is marked decorative, and none of its imitation controls took focus or spoke.

What the review found, and what changed

• Decorative separators spoke. The dots between the footer's legal links were each announced as a stop. Fixed the same day: they are now hidden from assistive technology, so the footer reads as its five links.
• Two invisible controls could take keyboard focus. On the returning-visitor landing, the Tab key could land on a faded-out header control that was not visible on screen. Fixed the same day, and a regression test now walks that page with real Tab presses and fails if any focused element is invisible.
• Three earlier automated flags were checked by hand and are not defects: the theme and language buttons are fully visible when focused, and controls inside the swipeable preview scroll into view when reached by keyboard.

Screen-reader review: VoiceOver (macOS)

Verified July 25, 2026. VoiceOver walked the same journey on Apple's screen reader: the landing page in both its fresh and answered states, the interview's first questions, the occupation search, the polished draft, the finished resume, the export step through a real save, the style step, and the Spanish interface. Navigation used VoiceOver's own cursor and activation commands, and every phrase VoiceOver spoke was recorded verbatim: 467 announcements.

What VoiceOver announced, as recorded

The landing's situation chooser, chosen with VoiceOver's own activation:

"Recently lost a job Laid off, let go, or the work ended toggle button" … and the answered sentence read back: "I am, recently lost a job, and I want work as, any job."

The occupation search, as results arrived:

"8 suggestions, use up and down arrows to choose"

The export step, driven end to end by VoiceOver:

"Ready to go with you. heading level 2" … the file's real name … the acknowledgment sentence in full as an "unchecked checkbox", VoiceOver's own activation turning it "checked", and the save control running the real save.

The Spanish interface:

"Nombra el trabajo. Sus tareas ya se conocen." … "Perdí un trabajo hace poco. Recorte, despido, o el trabajo terminó."

What the VoiceOver review found, and what changed

• Two lone periods spoke. The landing's fill-in sentence and the footer each close with a period that VoiceOver announced as its own stop, in both languages. Fixed the same day: both are now hidden from assistive technology, the visible sentence unchanged, with a regression test that fails on any bare punctuation left audible there.
• One control explained itself twice. The floating "Talk with Rung" control carries a spoken explanation; VoiceOver read it with the control and then again as a separate stop at the end of every screen. Fixed the same day, and re-verified under live VoiceOver: the control now announces once, with its explanation.
• Three other observations were checked by hand and are not defects: a typing field that read empty once carries its spoken name; the separate read-aloud button the harness looked for does not exist when the talk-through mode replaces it; and a settings panel announced as one long group on entry reads control by control on its own screen.

Manual WCAG 2.2 checks

The criteria an automated scanner cannot judge were checked by hand on every core screen: focus is never fully obscured (one failure found and fixed, above); no interaction requires dragging (the phone's swipe panes have buttons as alternatives); help sits in the same place on every page; nothing asks for the same information twice; the access password field accepts paste and password managers; and the layout holds at 320 pixels with no horizontal scrolling. The automated rules (axe-core, WCAG 2.0/2.1 A and AA plus the 2.2 AA rules) run on every change and block release on a violation.

Cognitive accessibility

The product was reviewed against the W3C's "Making Content Usable for People with Cognitive and Learning Disabilities": plain-language questions asked one at a time, choices offered instead of required writing, every question available read aloud with a spoken answer path, explicit errors, no time limits, no flashing, answers that stay visible and editable, and a person behind the contact address.

What remains open

• On-device passes. VoiceOver on a physical iPhone and TalkBack on a physical Android handset, walking the same scenes.

Documentation

The complete announcement logs and the conformance report (an ACR on the VPAT 2.5 template, dated July 25, 2026, with the on-device passes named as scope limits) are available on request at hello@rung.guru.