GitHub
The GitHub App connects your workspace to the repositories that hold your site’s code. Once it is installed:
- Pull requests link to issues. Mention an issue key in a pull request and the issue’s status follows it: in progress when it opens, fixed, pending verification when it merges.
- Draft pull requests carry the fix context. Open one from an issue, or from a group of issues that share a component, and it arrives on its own branch with the rule, the failing markup and the affected pages.
- Likely source files, when a search of the repository finds the failing markup.
- A coding agent can take an issue. GitHub Copilot’s coding agent can be started from the issue, on your own Copilot seat.
- A merge is verified by a scan. Ten minutes after a linked pull request merges, a scan of the issue’s affected pages marks it verified or reopens it.
The app never writes the fix itself. A draft pull request holds one context file; a person or a coding agent writes the change, and a person reviews and merges it.
GitHub is on every plan.
1. Install the app
Section titled “1. Install the app”Only owners and admins can manage the integration.
- Open Settings → Connections → GitHub and choose Install GitHub App.
- On GitHub, pick the account or organisation, then choose the repositories the app may use. Choosing only the repositories that hold your sites’ code keeps the list short.
- GitHub sends you back to Settings, which shows Connected to your account or organisation and the repositories.
If someone installed the app directly on GitHub rather than from this page, use Already installed on GitHub? on the same card: connect your own GitHub account, then Claim installation. Claiming checks through your GitHub account that you can reach that installation, so nobody can attach an installation they do not have access to.
Repositories belong to the workspace, not to a site. Every issue can use any of them, and you pick the repository each time you open a pull request. To add or remove repositories, change the app’s repository access on GitHub; the dashboard follows the change on its own.
We never store your code: only the installation, the repository names, the pull requests linked to issues, and the paths of any likely source files. The app works with GitHub tokens that expire within the hour.
2. Link pull requests to issues
Section titled “2. Link pull requests to issues”Every issue has a key, such as ACME-123, at the top of its page.
Mention it in a pull request’s title, description or branch name in a
repository the app can see. Case does not matter, so a branch called
tac/acme-123-fix-nav links too.
| On GitHub | In The Accessibility Company |
|---|---|
| Pull request opened or reopened | The issue links to it, moves to in progress, and records the pull request as its fix. |
| Pull request edited, or closed without merging | The link’s title and state are updated. |
| Pull request merged | The issue moves to fixed, pending verification and its verification starts: see When a pull request merges. |
- Linked pull requests show in the GitHub card on the issue’s page, with their state.
- A pull request links at most 10 issue keys. Keys that do not belong to your workspace are ignored.
- Status changes are recorded as the person who connected the app. If an issue cannot move that way (it is already verified, say), only the link is added.
3. Open a draft pull request
Section titled “3. Open a draft pull request”Members and above can open one. On an issue’s page, the GitHub card in the sidebar offers Open draft PR; choose the Repository first if the app can see more than one. The draft opens on GitHub in a new tab.
It creates three things, from your default branch:
- a branch,
tac/<issue key>; - one commit adding a context file,
.tac/<issue key>.md; - a draft pull request titled
fix(a11y): <issue title> (<issue key>).
The context file holds the rule, its impact, the selector and the number of affected pages; the failing element’s HTML and what is wrong with it; the AI-drafted fix suggestion when the issue has one, marked for review before anyone applies it; any likely source files; up to ten affected pages; and a definition of done that ends with deleting the context file before the pull request is marked ready.
The app does not change your code. A scan sees the HTML your site serves, not where that HTML comes from in your source, so it cannot write a patch it can stand behind. Someone on your team, or a coding agent, makes the change on the branch.
Opening a draft again for the same issue reuses the branch and returns the pull request already open. Each person can open five draft pull requests in any five minutes.
One pull request for a shared component
Section titled “One pull request for a shared component”Issues → Suggested components groups issues that seem to come from the same component, by their shared selectors. On a group, Open draft PR opens one draft covering every issue in it: the context file lists each issue with its rule and impact, shows the failing element of the highest-priority one, and includes AI fix suggestions for up to three. The pull request names every issue key, so merging it moves them all (up to 10) to fixed, pending verification.
The grouping is a suggestion, so the dashboard asks you to check the issues in it before it opens anything.
4. Likely source files
Section titled “4. Likely source files”When GitHub is connected, an issue’s page searches the selected repository’s default branch for distinctive parts of the failing markup: class names, data attributes and visible text. Files that match well enough appear under Likely source in the GitHub card, up to three, each with a confidence percentage, and they go into the draft pull request’s context file too.
Expect them on some issues, not most. Only confident matches are
shown, because a wrong file is worse than none. Hashed class names
(CSS Modules, CSS-in-JS) and generic ones like button or card give
nothing to search for, so those issues show no hint. Results are kept
for seven days.
5. Hand an issue to a coding agent
Section titled “5. Hand an issue to a coding agent”GitHub Copilot’s coding agent can take an issue and open a pull request for it. It runs on your own Copilot seat and GitHub account, so it needs your personal GitHub authorisation as well as the app.
- On an issue’s GitHub card, choose Connect GitHub to use the coding agent and authorise on GitHub. This links your GitHub account to you, not to the workspace, and the token is stored encrypted.
- The Fix with a coding agent button then appears, but only when GitHub confirms your account can start the coding agent in the selected repository. Your Copilot plan has to include the coding agent, and it has to be turned on for that repository.
- Press it. The coding agent receives the same fix context as a draft pull request, with an instruction to put the issue key in its pull request’s title. The issue moves to in progress, noting who started it and in which repository.
Its pull request links back by the key like any other, so merging it moves the issue to fixed, pending verification. Its usage counts against your Copilot plan, not The Accessibility Company’s. Members and above can start it, from an issue or from a suggested component group, five times in any five minutes.
To remove your personal authorisation, open Settings → Profile and choose Disconnect on the GitHub account card: the token we hold for you is deleted. To revoke the authorisation on GitHub as well, remove the app under Settings → Applications → Authorized GitHub Apps on GitHub. Other coding agents (Claude Code, Cursor, Codex and any MCP client) work from the same issues through the MCP server.
6. When a pull request merges
Section titled “6. When a pull request merges”- Each linked issue moves to fixed, pending verification, and the merge is recorded as its fix, with the pull request and the merge commit.
- If the workspace has an active plan, the issue’s verification starts: the same one Verify now starts, a scan of the issue’s affected pages. Its pages wait 10 minutes before they are scanned, so your deploy has time to reach the site. Up to five issues per merge are verified, in one scan per site.
- When the scan finishes, the issue is reopened if the problem is still there. If it is gone from those pages, the pages are scanned once more straight away, because a finding can be missing from one scan of an unchanged page; the issue is marked verified if that scan does not find it either. If a page could not be scanned, the issue stays fixed, pending verification.
The request and the result are on the issue’s activity, recorded as the person who connected the app, and a linked Jira or Linear ticket gets a comment when the issue is verified. While the verification waits and runs, it is listed with the site’s scans as in progress: a full-site Scan now says a scan is already running until it has finished, and a scheduled scan that falls due meanwhile starts after it.
If your deploy takes longer than 10 minutes, the scan can load the page before the fix is live and reopen the issue. Once the fix is live, move the issue back to fixed, pending verification and use Verify now. The next full scan, such as a scheduled scan, also marks the issue verified once the problem is gone.
Verification scans never count against your page checks.
Disconnecting
Section titled “Disconnecting”Settings → Connections → GitHub → Disconnect forgets the installation: pull requests stop linking and statuses stop following them. Existing links stay on issues. To withdraw the app’s access to your repositories, uninstall it on GitHub as well; uninstalling it on GitHub also disconnects the workspace.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause | Fix |
|---|---|---|
| A pull request didn’t link | The key isn’t in the title, description or branch, the repository isn’t one the app can see, or the key belongs to another workspace. | Add the key and edit the pull request, or give the app access to the repository on GitHub. |
| The issue linked but its status didn’t change | The issue can’t move that way: it is already verified, for example. | Change the status on the issue if it needs to move. |
| No Fix with a coding agent button | Your GitHub account isn’t connected, your Copilot plan doesn’t include the coding agent, or it is off for that repository. Viewers never see it. | Connect your account, then check the coding agent is enabled for the repository on GitHub. A viewer needs the member role, which the owner can give. |
| Open draft PR says the repository isn’t available | The repository isn’t part of the installation. | Add it to the app’s repository access on GitHub. |
| Issue stays fixed, pending verification after a merge | The verification is still waiting its 10 minutes, a page could not be scanned, or the workspace has no active plan. | Once the fix is live, use Verify now on the issue. |
| Issue reopened after a merge | The scan ran before your deploy finished, or the problem is still on a page. | Check the page. Once the fix is live, move the issue back to fixed, pending verification and use Verify now. |