Skip to content

README.md

Latest commit

 

History

History
94 lines (61 loc) · 4.68 KB

README.md

File metadata and controls

94 lines (61 loc) · 4.68 KB
Raw

Test Super Access in Chrome

This guide is for product managers and other testers who do not write code. You will load a test version of Super Access into Chrome, try a prepared set of examples, and record what happens.

You do not need to understand the source code or fix anything you find.

What to set aside

  • A Mac with a current version of Google Chrome
  • VoiceOver, if you are completing the screen-reader checks
  • About 45 minutes
  • The unzipped Super Access human test folder
  • For one final 10-minute check, a colleague who has worked on a website but has not worked on Super Access

Before you begin

  1. Unzip the test package.
  2. Keep the entire unzipped folder together. Do not move individual files out of it.
  3. Follow Add Super Access to Chrome below before starting the test page.

The package contains no Mac application or executable installer. Super Access is a Chrome extension and does not require Apple signing or notarization. Chrome loads it directly from the supplied extension folder.

Add Super Access to Chrome

This is a private test build, so Chrome needs you to add it once:

  1. In Chrome, enter chrome://extensions in the address bar and press Return.
  2. Turn on Developer mode in the upper-right corner.
  3. Choose Load unpacked.
  4. In the file window, open the unzipped test folder and select the folder named extension.
  5. If Chrome asks you to confirm, choose Select or Open.
  6. Open Chrome’s Extensions menu—the puzzle-piece icon near the address bar.
  7. Find Super Access and choose its pin icon so it stays visible.

You should now see the Super Access icon near Chrome’s address bar.

Start the supplied test page

The test page needs a small local web server. These are the only Terminal steps:

  1. Install the current LTS version of Node.js if it is not already installed.
  2. In Finder, Control-click the unzipped super-access-human-test folder.
  3. Choose Services, then New Terminal at Folder.
  4. Copy the following line, paste it into Terminal, and press Return:
npm install && npm run dev:fixtures
  1. Leave Terminal open. When it displays a local address, open http://127.0.0.1:5173 in Chrome.

If New Terminal at Folder is unavailable, open Terminal from Applications → Utilities, type cd including the space, drag the unzipped folder from Finder into Terminal, press Return, and then paste the command above.

Open the extension

  1. Return to the Chrome tab titled Super Access verifier fixtures. If it did not open, go to http://127.0.0.1:5173.
  2. Choose the Super Access icon near the address bar. The side panel should open.
  3. Chrome may display a message that Super Access “started debugging this browser.” That is expected: the extension needs this connection to test real keyboard behavior.

If the side panel does not open, enter chrome://extensions/shortcuts in the address bar. Find Super Access, assign a shortcut to Open the Super Access side panel, return to the test page, and use that shortcut.

Complete the checklist

Open HUMAN-TEST-RESULTS.md from the extension folder in any text editor. Follow it from top to bottom.

For each check, mark one result:

  • Pass: what happened matched the expected result.
  • Fail: you completed the check, but the result was wrong or confusing.
  • Blocked: you could not complete the check at all.

Please write what happened in ordinary language. A short note such as “focus moved to the top of the panel” is more useful than trying to diagnose the cause.

If something stops working

  1. Mark the current check Blocked or Fail and note the last thing that worked.
  2. If the panel offers Retry connection, choose it once.
  3. Otherwise, close and reopen the side panel.
  4. If that does not help, return to chrome://extensions, find Super Access, choose its reload button, and reopen the panel.
  5. If it still fails, continue with any checks that remain possible. Do not troubleshoot further.

What to send back

Send the Super Access team:

  1. Your completed HUMAN-TEST-RESULTS.md file.
  2. Screenshots only for failures that are difficult to explain in words.
  3. Your Chrome and macOS version, recorded at the top of the checklist.

When finished, close the Terminal window. To remove the test extension, return to chrome://extensions and choose Remove under Super Access.

Privacy note

Use only the supplied test page. The extension reads the currently inspected page while its panel is connected. Test evidence stays on your computer unless you copy and send it. Do not test confidential or customer pages with this build.