Live review panel
Some checks the scan cannot decide: can you reach every control with the keyboard, does the screen reader say what a button does, does the page still work at 400% zoom. A person has to try them on the live page. The live review panel sits beside that page, in Chrome’s side panel or Firefox’s sidebar, and shows only those checks, one card at a time. Your answer is saved exactly as it would be in the site’s Review.
The panel is not a scanner. It runs no checks of its own and finds nothing itself, so it can never disagree with your next scan.
What it shows
Section titled “What it shows”For the page you have open, the panel lists the checks that are open and that a person tests on the live page, grouped by the kind of testing (keyboard first, then forms, then the rest), in the same words as Review.
It leaves out:
- Checks the scan passed. They are not tasks.
- Scan findings to confirm. Confirming a finding is a desk task: the evidence is already in Review. A line under the list says how many are waiting there.
- Journey checks. A journey state cannot be found from a URL, so these stay in Review too.
If the page is in the review but nothing is left to test, the panel says so. If the page is not in the review, or the site is not in your workspace, it says that instead.
Answering
Section titled “Answering”Open a check to see what to try and what you should see, then answer:
- Looks good records a pass.
- Problem asks for what is wrong in one line and what you saw, and takes an optional screenshot. It becomes an issue you can assign and track, titled with your one line.
- Couldn’t check asks what stopped you.
- Doesn’t apply appears on checks whose subject may not be on the page.
Once a check is answered it leaves the list. Review shows the same answer when you refresh it.
Retesting
Section titled “Retesting”When someone marks a problem you logged as fixed, its check comes back: first on its page in the panel (“2 to retest, 4 to test on this page”), and under To retest in Review’s Today, each saying which problem it is about.
- Looks good verifies the fix. The issue is closed as verified, with a note that a retest passed and on which page.
- Problem reopens the issue, and what you saw is added to it as a comment, for whoever marked it fixed.
Nothing else needs a retest: a scan finding that is marked fixed is checked by the next scan.
Logging something else
Section titled “Logging something else”You will find problems no open check asks about: a keyboard trap while you check reflow, say. Use Log a problem on this page, choose the WCAG criterion it fails, and describe it. If the page has an open check for that criterion, the panel takes you to that check with what you wrote, so it is one issue, not two.
What you are testing with
Section titled “What you are testing with”Before your first answer in a sitting, the panel asks what you are testing with: browser, assistive technology and platform. The browser and platform start from what your browser reports; type your screen reader and its version, or leave it empty if you are not using one. It is sent with every answer and problem, and the readiness reports cite it (“Firefox 131, NVDA 2025.1, Windows 11”). You can skip it; the reports then say “Environment not recorded.” Change it any time from the line at the top of the panel; answers already saved keep what they were tested with.
The element a problem is about
Section titled “The element a problem is about”A problem can carry the element it is about, so whoever fixes it can find it in the code: the issue shows its selector and HTML, and coding assistants reading the issue over MCP get them as the problem’s location.
- The focused element. If you reached the element with the keyboard or your screen reader, press Alt+Shift+E on the page, or Use the focused element in the problem form. Focus inside shadow DOM and same-page frames is followed. Alt+Shift+E also attaches a screenshot of the page around the element, with the element outlined, unless the problem already has one.
- Pick an element. With a mouse, choose Pick an element, then click the element on the page; the one under the pointer is outlined. Escape cancels. The page does not act on that click.
Before anything is sent, the panel takes out what the page held: form values, hidden and password fields, and the text of scripts, styles and text areas. The form shows exactly what will be sent, and Remove drops it.
A screen reader’s browse mode moves its own cursor, not the page’s focus, so the focused element can be the last control you tabbed to rather than the text you are reading. For text, pick it with the mouse, or describe it in What you saw.
The panel reaches into a page only when you capture an element, and only on a site you allowed it on.
Screenshots
Section titled “Screenshots”A browser lets an extension capture a tab only when you point it at that tab from the page itself, not from a button in the panel. While you are writing a problem:
- right-click the page, open The Accessibility Company and choose Attach a screenshot of this page (from the keyboard, Shift+F10 opens the same menu on Windows and Linux), or press Alt+Shift+S while the page is in front;
- right-click, open The Accessibility Company and choose Attach a screenshot of an area, then drag across the part that matters. Escape cancels, and the page does not act on the drag. Only what is on screen can be chosen;
- press Alt+Shift+E on the element you tabbed to, for a screenshot of the page around it with the element outlined (see above). This is the keyboard’s way to a picture of one part of the page; or
- choose a file you captured yourself.
The screenshot lands in the problem you are writing. The right-click items show only while a problem form is open: open a check and choose its fail answer, or Log a problem on this page, first.
You can change the shortcuts in your browser’s extension shortcuts
settings (chrome://extensions/shortcuts in Chrome); the panel’s hints
show the keys you set. None uses the NVDA, JAWS or VoiceOver modifier
keys. The area has no key of its own, since dragging needs a pointer,
but you can set one there.
Setting it up
Section titled “Setting it up”- Install the panel. Until it is listed in the Chrome Web Store
and Firefox Add-ons, your team gives you the build to load: in
Chrome, open
chrome://extensions, turn on Developer mode and choose Load unpacked; in Firefox, openabout:debugging, choose This Firefox, then Load Temporary Add-on. - Connect it. In the dashboard, open a site’s Review and press Test these on the live site on any page, or go to the panel’s Connect page, and press Connect. There is no token to copy. Members and above can connect; viewers cannot answer checks.
- Allow it on your sites. The panel asks to see the pages of the sites in your workspace, and only those. It cannot see any other site you visit, and sends nothing from them.
- Pin it to your toolbar.
After that, Test these on the live site in a site’s Review opens the page with the panel beside it. In Firefox, which does not let a page open the sidebar, open it from the toolbar once the page has opened.
Disconnecting
Section titled “Disconnecting”Disconnect, at the bottom of the panel, revokes the panel’s access at once. Owners and admins can also revoke it from Settings → Connections, where it is listed as a review panel token. It also stops working if you leave the workspace, and after 90 days, when you connect again with one press.
What it can see and send
Section titled “What it can see and send”- It reads the address of your current tab only on your workspace’s sites, to find the page’s checks.
- It sends your answers, the problems you log (with the page address and any screenshot you add) and your testing environment to The Accessibility Company.
- It never reads or sends anything from other sites, and never changes the pages you test.