@@ -209,7 +209,7 @@ The accessibility owner keeps these current. Report a problem with any of them t
 
 ## Open Source Accessibility Framework
 
-We follow the [Open Source Accessibility Framework](https://open-source-accessibility.github.io/Open-Source-Accessibility-Framework/) in its four phases and record our progress, action by action, in a public tracking issue in the framework's repository. Progress is self-reported. As of October 2026:
+We follow the [Open Source Accessibility Framework](https://open-source-accessibility.github.io/Open-Source-Accessibility-Framework/) in its four phases and record our progress, action by action, in our public tracking issue, [GIT Going with GitHub, issue 55](https://github.com/open-source-accessibility/Open-Source-Accessibility-Framework/issues/55), in the framework's repository. Progress is self-reported, and an action is checked there only when its definition of done is fully met: 17 of 24 as of October 2026. Three workflow actions described below are in place but stay unchecked for now: docs accessible by default (findings remain in issue 267), accessible interfaces (the site has not yet been checked in a browser) and dependencies (the two known blockers have no upstream report yet). As of October 2026:
 
 - **Foundational:** this document; the `accessibility` label, applied to accessibility reports and work.
 - **Workflow:** priorities, contributor expectations and interface requirements above, linked from [CONTRIBUTING.md](CONTRIBUTING.md); the accessibility bug report form with an email alternative; severity and response; the pull request checklist; `good first issue` and `help wanted` accessibility issues with acceptance criteria; an owner; documentation checked by the automated check; dependencies and upstream blockers recorded.
 
@@ -317,7 +317,9 @@ And by the end of Day 2, you will not just be a learner. You will be a product m
 
 ## Accessibility of This Project
 
-How we work on the workshop's own accessibility, how to report a barrier (on GitHub or by email), how we respond, what the workshop supports and what we know is not yet good enough are all in [ACCESSIBILITY.md](ACCESSIBILITY.md). We follow GitHub's [Open Source Accessibility Framework](https://open-source-accessibility.github.io/Open-Source-Accessibility-Framework/), an improvement framework rather than a certification, and publish our progress in ACCESSIBILITY.md.
+How we work on the workshop's own accessibility, how to report a barrier (on GitHub or by email), how we respond, what the workshop supports and what we know is not yet good enough are all in [ACCESSIBILITY.md](ACCESSIBILITY.md). We follow GitHub's [Open Source Accessibility Framework](https://open-source-accessibility.github.io/Open-Source-Accessibility-Framework/), an improvement framework rather than a certification, and publish our progress in ACCESSIBILITY.md and in our public tracking issue, [GIT Going with GitHub, issue 55](https://github.com/open-source-accessibility/Open-Source-Accessibility-Framework/issues/55).
+
+[![Open Source Accessibility Framework progress for GIT Going with GitHub](https://img.shields.io/badge/Accessibility%20Framework-GIT%20Going%20with%20GitHub-F143AB?logo=github&logoColor=000000)](https://github.com/open-source-accessibility/Open-Source-Accessibility-Framework/issues/55)
 
 To report a barrier, use the [accessibility bug report form](https://github.com/Community-Access/git-going-with-github/issues/new?template=accessibility-bug.yml) or email [support@community-access.org](mailto:support@community-access.org). To help, look for issues labeled [`accessibility`](https://github.com/Community-Access/git-going-with-github/issues?q=is%3Aopen+label%3Aaccessibility).
 
 
@@ -414,7 +414,7 @@ <h2 id="reusing-our-accessibility-materials">Reusing our accessibility materials
 </ul>
 <p>The accessibility owner keeps these current. Report a problem with any of them the same way as any other barrier.</p>
 <h2 id="open-source-accessibility-framework">Open Source Accessibility Framework</h2>
-<p>We follow the <a href="https://open-source-accessibility.github.io/Open-Source-Accessibility-Framework/">Open Source Accessibility Framework</a> in its four phases and record our progress, action by action, in a public tracking issue in the framework&#39;s repository. Progress is self-reported. As of October 2026:</p>
+<p>We follow the <a href="https://open-source-accessibility.github.io/Open-Source-Accessibility-Framework/">Open Source Accessibility Framework</a> in its four phases and record our progress, action by action, in our public tracking issue, <a href="https://github.com/open-source-accessibility/Open-Source-Accessibility-Framework/issues/55">GIT Going with GitHub, issue 55</a>, in the framework&#39;s repository. Progress is self-reported, and an action is checked there only when its definition of done is fully met: 17 of 24 as of October 2026. Three workflow actions described below are in place but stay unchecked for now: docs accessible by default (findings remain in issue 267), accessible interfaces (the site has not yet been checked in a browser) and dependencies (the two known blockers have no upstream report yet). As of October 2026:</p>
 <ul>
 <li><strong>Foundational:</strong> this document; the <code>accessibility</code> label, applied to accessibility reports and work.</li>
 <li><strong>Workflow:</strong> priorities, contributor expectations and interface requirements above, linked from <a href="CONTRIBUTING.html">CONTRIBUTING.md</a>; the accessibility bug report form with an email alternative; severity and response; the pull request checklist; <code>good first issue</code> and <code>help wanted</code> accessibility issues with acceptance criteria; an owner; documentation checked by the automated check; dependencies and upstream blockers recorded.</li>
 
@@ -818,7 +818,8 @@ <h2 id="questions-before-the-event">Questions Before the Event?</h2>
 <li><strong>Community:</strong> <a href="https://github.com/orgs/community/discussions/categories/accessibility">GitHub Accessibility Discussions</a></li>
 </ul>
 <h2 id="accessibility-of-this-project">Accessibility of This Project</h2>
-<p>How we work on the workshop&#39;s own accessibility, how to report a barrier (on GitHub or by email), how we respond, what the workshop supports and what we know is not yet good enough are all in <a href="ACCESSIBILITY.html">ACCESSIBILITY.md</a>. We follow GitHub&#39;s <a href="https://open-source-accessibility.github.io/Open-Source-Accessibility-Framework/">Open Source Accessibility Framework</a>, an improvement framework rather than a certification, and publish our progress in ACCESSIBILITY.md.</p>
+<p>How we work on the workshop&#39;s own accessibility, how to report a barrier (on GitHub or by email), how we respond, what the workshop supports and what we know is not yet good enough are all in <a href="ACCESSIBILITY.html">ACCESSIBILITY.md</a>. We follow GitHub&#39;s <a href="https://open-source-accessibility.github.io/Open-Source-Accessibility-Framework/">Open Source Accessibility Framework</a>, an improvement framework rather than a certification, and publish our progress in ACCESSIBILITY.md and in our public tracking issue, <a href="https://github.com/open-source-accessibility/Open-Source-Accessibility-Framework/issues/55">GIT Going with GitHub, issue 55</a>.</p>
+<p><a href="https://github.com/open-source-accessibility/Open-Source-Accessibility-Framework/issues/55"><img src="https://img.shields.io/badge/Accessibility%20Framework-GIT%20Going%20with%20GitHub-F143AB?logo=github&logoColor=000000" alt="Open Source Accessibility Framework progress for GIT Going with GitHub"></a></p>
 <p>To report a barrier, use the <a href="https://github.com/Community-Access/git-going-with-github/issues/new?template=accessibility-bug.yml">accessibility bug report form</a> or email <a href="mailto:support@community-access.org">support@community-access.org</a>. To help, look for issues labeled <a href="https://github.com/Community-Access/git-going-with-github/issues?q=is%3Aopen+label%3Aaccessibility"><code>accessibility</code></a>.</p>
 <h2 id="license">License</h2>
 <p>All workshop documentation is licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a> - you are free to share and adapt with attribution.</p>