From b0f9d72c61a36e0cf317e28d96f2c9735356c526 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 28 Oct 2026 15:32:57 -0700 Subject: [PATCH] docs: link the framework tracking issue and badge GIT Going with GitHub is registered with the Open Source Accessibility Framework as issue 55, with 17 of 24 actions checked. ACCESSIBILITY.md links it and says which three workflow actions stay unchecked and why; the README links it and carries the framework badge. HTML rebuilt. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01PmRBrUTuhzYnQBFxUCN6Vr --- ACCESSIBILITY.md | 2 +- README.md | 4 +++- html/ACCESSIBILITY.html | 2 +- html/README.html | 3 ++- 4 files changed, 7 insertions(+), 4 deletions(-) diff --git a/ACCESSIBILITY.md b/ACCESSIBILITY.md index 668782dc..0c86c94c 100644 --- a/ACCESSIBILITY.md +++ b/ACCESSIBILITY.md @@ -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. diff --git a/README.md b/README.md index 4a579dbb..35aff1de 100644 --- a/README.md +++ b/README.md @@ -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). diff --git a/html/ACCESSIBILITY.html b/html/ACCESSIBILITY.html index 0216e12a..806a8139 100644 --- a/html/ACCESSIBILITY.html +++ b/html/ACCESSIBILITY.html @@ -414,7 +414,7 @@

Reusing our accessibility materials

The accessibility owner keeps these current. Report a problem with any of them the same way as any other barrier.

Open Source Accessibility Framework

-

We follow the 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 in its four phases and record our progress, action by action, in our public tracking issue, GIT Going with GitHub, issue 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:

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. We follow GitHub's 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. We follow GitHub's 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.

+

Open Source Accessibility Framework progress for GIT Going with GitHub

To report a barrier, use the accessibility bug report form or email support@community-access.org. To help, look for issues labeled accessibility.

License

All workshop documentation is licensed under CC BY 4.0 - you are free to share and adapt with attribution.