Prefill

Accessibility Statement

Last reviewed 13 August 2026 · describes Prefill 1.1

The keyboard and contrast work described below is in Prefill 1.1, currently with the Chrome Web Store for review. In 1.0, the tab strip and the dropdown menus are mouse-only and some hint text sits at 3.3:1 rather than the 4.5:1 minimum. If that blocks you today, email us and we will help you directly while the update clears review.

Prefill exists to remove a barrier: filling the same forty fields into every job application. That job matters most to the people for whom typing, reading small text, or using a mouse is expensive. So accessibility is not a compliance box here, it is the point of the product.

What works today

Each of these has been checked in the current build:

• Everything is reachable from the keyboard. The tab strip is a real tab list with arrow-key, Home and End navigation; the profile and status menus open with Enter or the down arrow, move with arrow keys, choose with Enter, and close with Escape, returning focus where you left it.
• Focus is always visible, including inside the panel Prefill draws on other people's pages, where we force our own focus ring because many sites switch theirs off.
• Text contrast meets the 4.5:1 AA minimum across the whole palette, on all three surface shades. That was measured, not eyeballed.
• Status messages are announced. Save confirmations, import and erase results, and the on-page message after a fill are live regions, so a screen reader hears the outcome instead of the fill being silent.
• Motion respects your system setting. Everything that animates stops when "reduce motion" is on.
• No time limits, no flashing, no CAPTCHA, no audio, and nothing that requires a mouse gesture, a drag, or a hover to complete.
• Drag and drop is never the only way. The Files tab accepts a drop, and every drop zone also has a normal file button.
• Nothing is auto-submitted. Prefill fills; you review and send. Nothing moves under you while you read.

What does not work well yet

Stating these plainly is more useful than a conformance badge:

• The toolbar popup does not scale to 200%. Chrome caps how large a popup window can be, so at large text sizes it scrolls rather than reflows. The side panel and the full Settings page do scale, and both hold the same controls. If text size matters to you, work in one of those; the side panel opens from the icon in the panel header.
• No independent audit or VPAT. Our testing is keyboard, zoom, contrast measurement and screen-reader spot checks by one person, not a formal review.
• The application forms themselves are not ours. Prefill draws a small panel on employer and job-board pages, and those pages have their own barriers that we cannot fix. Prefill filling a field for you is often the workaround, but it cannot repair the page underneath.
• Screen-reader testing is not systematic yet. The structure is there (labels, roles, live regions) and it is written to be read, but we have not walked every form end to end with VoiceOver, NVDA or JAWS. If something reads badly, tell us which screen and it goes to the front of the queue.

How to reach a person

Email getprefill@gmail.com with the word "access" in the subject. Tell us what you were trying to do, what got in the way, and the assistive technology and browser you use if you know them. We will reply within 5 business days, and if a fix will take longer than that, we will tell you what we are doing and offer another way to get the same result in the meantime, including doing it with you by email.

Prefill is made by one person, so there is no ticket queue and no phone tree: your message reaches the developer.

How we test

• Keyboard-only walkthrough of the popup, the side panel and the Settings page.
• Contrast ratios computed against every surface colour whenever a colour changes.
• Browser zoom and OS text scaling.
• Automated checks in the build, so the things that regress silently fail loudly instead.
• Reports from people who use Prefill. Those outrank our own checklist: if you tell us something is unusable, that is the finding.

Standard and scope

Target: WCAG 2.1 Level AA. Scope: the Prefill Chrome extension (popup, side panel, Settings, and the panel it draws on pages) and the pages on getprefill.netlify.app. It does not extend to third-party sites we appear on, or to Stripe's checkout and billing pages, which are governed by Stripe's own practices.

Changes to this statement

We review this page whenever the interface changes materially, and at least twice a year. The date at the top is when it was last checked against the shipped build, not just when the wording was edited.