-
Notifications
You must be signed in to change notification settings - Fork 4
appendix u resources
Listen to Episode 38: Resources and Links - a conversational audio overview of this chapter. Listen before reading to preview the concepts, or after to reinforce what you learned.
This is your permanent reference. Every link, tool, guide, and community resource from the two-day workshop in one place. Bookmark this page in your fork so it travels with you.
- The Central Project - Accessibility Agents
- GitHub Accessibility Guides
- GitHub Skills Learning Modules
- Screen Reader Downloads and Documentation
- VS Code Resources
- GitHub Copilot Resources
- GitHub Agentic Workflows
- Spec-Driven Development - Spec Kit
- GitHub CLI, Desktop, and Copilot CLI
- GitHub Mobile Apps
- GitHub Best Practices and Power Features
- Finding More Contributions
- Accessibility Standards and References
- GitHub Keyboard Shortcuts
- Community and Support
- Your Workshop Documentation - Offline Reference
The project you forked, contributed to, and carry home.
| Resource | URL | Notes |
|---|---|---|
| Accessibility Agents - Main Repo | github.com/community-access/accessibility-agents | The upstream - your contributions go here |
| Getting Started Guide | accessibility-agents/Documentation/GETTING-STARTED.md | Your first hour with the agents |
| Full Reference Guide | accessibility-agents/Documentation/GUIDE.md | Complete agent and command reference |
| Setup Guide | accessibility-agents/SETUP.md | Configuration and preferences |
| Contributing Guide | accessibility-agents/CONTRIBUTING.md | How to submit improvements |
| Security Policy | accessibility-agents/SECURITY.md | Responsible disclosure instructions |
| MIT License | accessibility-agents/LICENSE | Fork it, use it, make it yours |
After the workshop, your fork lives at:
https://github.com/[your-username]/accessibility-agents
- Clone your fork:
git clone https://github.com/[your-username]/accessibility-agents.git - Open in VS Code:
cd accessibility-agents && code . - Open Copilot Chat:
Ctrl+Shift+I - Type:
@daily-briefing morning briefing
- Copy
preferences.example.mdtopreferences.mdin.github/agents/ - Add your GitHub username, your most-used repositories, and your preferred output format
- Commit the file - now the agents know who you are and what you work on
Official guides from the GitHub Accessibility team. These were the primary research sources for this workshop's documentation.
| Guide | URL | When to Use |
|---|---|---|
| GitHub Repos - Screen Reader Guide | accessibility.github.com/documentation/guide/repos | Navigating repositories, file trees, branches |
| GitHub Issues - Screen Reader Guide | accessibility.github.com/documentation/guide/issues | Filing, reading, commenting on issues |
| GitHub Pull Requests - Screen Reader Guide | accessibility.github.com/documentation/guide/pull-requests | Reading diffs, reviewing, merging |
| GitHub Copilot in VS Code - Screen Reader Guide | accessibility.github.com/documentation/guide/github-copilot-vsc | Using Copilot with NVDA, JAWS, VoiceOver |
| Custom Instructions - Screen Reader Guide | accessibility.github.com/documentation/guide/custom-instructions | Configuring Copilot's behavior for your workflow |
| Getting Started with Custom Agents for Accessibility | accessibility.github.com/documentation/guide/getting-started-with-agents | What agents are, custom agents vs custom instructions, informational vs task-oriented agents, step-by-step walkthroughs for building both types |
| Accessibility Settings Overview | docs.github.com/en/get-started/accessibility | Hovercard settings, motion reduction, color modes |
GitHub Skills is GitHub's free, self-paced interactive learning platform. Every course runs entirely inside GitHub - no external site, no separate login, no video to watch. Each course uses the template-copy pattern: you copy the course repository to your account, and Mona (GitHub's official education bot) activates and teaches you entirely through issues and pull requests.
Unlike a conventional course where you watch videos or read slides, GitHub Skills teaches through doing:
- Copy the course: Select "Start course" → "Use this template" → "Create a new repository." This copies the course scaffold to your own account.
- Mona activates: A GitHub Actions workflow automatically runs - within 20 seconds, Mona opens your first lesson as an Issue in your new repository.
- Read and act: The issue contains step-by-step instructions. You do the task (commit a file, open a PR, resolve a conflict) in the same repository.
- Mona validates: Another GitHub Actions workflow detects what you did, checks if it's correct, and either advances you to the next step or gives you feedback to try again.
- Repeat until done: All feedback arrives as issue comments and new issues. The course is complete when Mona closes the final issue with a success message.
Since everything happens in GitHub, the accessibility skills from this workshop apply directly:
Starting a course:
Navigate to the module URL
B → "Start course" button → Enter
B → "Use this template" → Enter
B → "Create a new repository" → Enter
Fill in repo name → Tab → "Create repository" → Enter
Following lessons:
Navigate to your new repo's Issues tab (G then I)
H or 3 → find "Step 1:" issue heading → Enter to open it
Read instructions with ↓ in Browse Mode
Complete the task described → commit / PR / edit as instructed
Wait ~20 seconds → Mona posts a follow-up comment or opens the next issue
9 (NVDA/JAWS) → navigate to comments to read Mona's feedback
GitHub Skills courses are available 24/7 and are completely free. Recommended order after this workshop:
| Module | URL | Duration | Prerequisite | What You Learn |
|---|---|---|---|---|
| Introduction to GitHub | github.com/skills/introduction-to-github | < 1 hour | None | Branches, commits, pull requests, merge |
| Communicate Using Markdown | github.com/skills/communicate-using-markdown | < 1 hour | Introduction to GitHub | Headings, emphasis, images, code blocks, task lists, tables |
| Review Pull Requests | github.com/skills/review-pull-requests | < 30 min | Introduction to GitHub | Assign reviewers, leave comments, suggest changes, apply suggestions, approve, merge |
| Resolve Merge Conflicts | github.com/skills/resolve-merge-conflicts | < 30 min | Introduction to GitHub | Why conflicts happen, reading conflict markers, resolving in the web editor |
| Hello GitHub Actions | github.com/skills/hello-github-actions | < 30 min | Introduction to GitHub | Workflow files, triggers, jobs, run steps, merge |
| Write JavaScript Actions | github.com/skills/write-javascript-actions | < 1 hour | Hello GitHub Actions | Custom action metadata (action.yml), writing steps, composing workflows |
Relationship to this workshop: The introduction and PR courses reinforce everything you practiced here. The GitHub Actions course is the foundation for understanding the CI/CD workflows that run inside accessibility-agents.
| Resource | URL |
|---|---|
| Download NVDA (free) | NVDA download page |
| NVDA User Guide | NVDA User Guide |
| NVDA Add-ons | NVDA Add-on Store |
| NVDA Community | NVDA Community site |
- Toggle browse/focus mode:
NVDA+Space - Elements list:
NVDA+F7 - Next heading:
H| Next link:K| Next button:B| Next form field:F
| Resource | URL |
|---|---|
| Download JAWS (trial available) | freedomscientific.com/products/software/jaws |
| JAWS Getting Started | freedomscientific.com/training/jaws/getting-started |
| JAWS Keyboard Reference | freedomscientific.com/training/jaws/keyboard-shortcuts |
- Virtual PC Cursor on/off:
Insert+Z - Elements list:
Insert+F3 - Next heading:
H| Next link:TaborU| Next button:B
| Resource | URL |
|---|---|
| VoiceOver User Guide (macOS) | support.apple.com/guide/voiceover/welcome/mac |
| VoiceOver Getting Started (macOS) | apple.com/accessibility/mac/vision |
| Enable VoiceOver |
Cmd+F5 (macOS) or Settings → Accessibility → VoiceOver (iOS) |
- Start/stop VoiceOver:
Cmd+F5 - VO modifier:
Caps LockorCtrl+Option - Rotor:
VO+U - Next heading:
VO+Cmd+H
| Screen Reader | Platform | URL |
|---|---|---|
| Narrator | Windows (built in) |
Win+Ctrl+Enter to launch - no download required |
| Orca | Linux (GNOME) | wiki.gnome.org/Projects/Orca |
| TalkBack | Android (built in) | Settings → Accessibility → TalkBack |
| Resource | URL | Notes |
|---|---|---|
| Download VS Code | code.visualstudio.com | Free - Windows, macOS, Linux |
| VS Code Accessibility Docs | code.visualstudio.com/docs/editor/accessibility | Screen reader mode, audio cues, accessible view |
| VS Code Keyboard Shortcuts (Windows) | aka.ms/vscode-keyboard-windows | Full reference PDF |
| VS Code Keyboard Shortcuts (macOS) | aka.ms/vscode-keyboard-mac | Full reference PDF |
| GitHub Pull Requests Extension | marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github | Review and manage PRs from VS Code |
| GitLens | marketplace.visualstudio.com/items?itemName=eamodio.gitlens | Enhanced git history, blame, and branch visualization |
| YAML Support | marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml | YAML validation - useful for issue templates |
- Open VS Code Extensions (
Ctrl+Shift+X) - Search:
GitHub Pull Requests - Install: publisher is "GitHub"
| Resource | URL | Notes |
|---|---|---|
| GitHub Copilot (Free tier) | github.com/features/copilot | Free for individuals - no credit card required |
| Copilot Documentation | docs.github.com/copilot | Full reference |
| Copilot in VS Code | docs.github.com/en/copilot/using-github-copilot/getting-started-with-github-copilot | Setup guide |
| Copilot Extensions Marketplace | github.com/marketplace?type=apps&copilot_app=true | Extensions that add capabilities to Copilot Chat |
| Custom Instructions for Copilot | docs.github.com/en/copilot/customizing-copilot/adding-custom-instructions-for-github-copilot | Teach Copilot your preferences and project context |
| Copilot Coding Agent - Customize Environment | docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment | Switch coding agent to Windows dev environment |
| Copilot in VS Code - A11y Guide | accessibility.github.com/documentation/guide/github-copilot-vsc | Screen reader-optimized usage |
GitHub Agentic Workflows are in technical preview as of February 2026. Access, feedback channels, and setup information:
| Resource | URL | Notes |
|---|---|---|
| Agentic Workflows Blog Post | github.blog/ai-and-ml/automate-repository-tasks-with-github-agentic-workflows | The announcement - explains the full model |
gh-aw CLI Extension |
gh extension install github/gh-aw |
Install via GitHub CLI |
| Technical Preview Feedback | gh.io/aw-tp-community-feedback | Community discussion for the preview |
| GitHub Next Discord | gh.io/next-discord | Real-time discussion with the GitHub Next team |
During the workshop, you learned:
- Standard GitHub Actions (YAML workflows - triggers, jobs, steps)
- Accessibility Agents agents (
.agent.mdfiles - plain English instructions, Copilot Chat executor) - GitHub Agentic Workflows (
.mdfiles in.github/workflows/- plain English instructions, cloud-based coding agent executor)
All three live in .github/. All three are plain text. The only difference is where they run and how sophisticated their executor is.
| Resource | URL | Notes |
|---|---|---|
| Spec Kit - GitHub Repo | github.com/github/spec-kit | Open source, MIT license |
| Spec Kit Blog Post | github.blog/ai-and-ml/generative-ai/spec-driven-development-with-ai-get-started-with-a-new-open-source-toolkit | Full explanation of the methodology |
The core idea: Write the intent of a feature before anyone builds it. The specification is a living document - AI uses it to plan tasks, contributors use it to stay aligned, the community uses it to evaluate whether the outcome matched the intention.
uvx --from git+https://github.com/github/spec-kit.git specify init YOUR_PROJECT_NAME-
/specify- open a new specification session -
/plan- convert a spec into a development plan -
/tasks- break the plan into trackable tasks
Works with GitHub Copilot, Claude Code, and Gemini CLI.
| Resource | URL |
|---|---|
| Download | cli.github.com |
| Documentation | cli.github.com/manual |
| Authentication guide | docs.github.com/en/github-cli/github-cli/quickstart |
# Install
winget install GitHub.cli # Windows
brew install gh # macOS
# Most useful commands for contributors
gh issue list # List issues in current repo
gh issue view 42 # Read issue #42
gh pr list # List open PRs
gh pr view 14 # Read PR #14
gh pr create # Create a PR interactively
gh pr merge 14 # Merge PR #14
gh repo fork # Fork the current repo
gh repo clone owner/repo # Clone a repository# Install the extension
gh extension install github/gh-copilot
# Ask Copilot to explain a command
gh copilot explain "git rebase -i HEAD~3"
# Ask Copilot to suggest a command
gh copilot suggest "undo my last commit but keep the changes staged"| Resource | URL |
|---|---|
| Download | desktop.github.com |
| Keyboard shortcuts | docs.github.com/en/desktop/installing-and-authenticating-to-github-desktop/keyboard-shortcuts-in-github-desktop |
GitHub's official mobile apps bring the full GitHub experience to your phone or tablet. Perfect for reviewing PRs, triaging issues, and staying connected when away from your computer.
| Platform | Download | Screen Reader Support |
|---|---|---|
| iOS | apps.apple.com/app/github/id1477376905 | VoiceOver supported |
| Android | play.google.com/store/apps/details?id=com.github.android | TalkBack supported |
- Browse repositories - navigate code, read files, view commits
- Manage issues - create, edit, comment, close, and label issues
- Review pull requests - read diffs, leave comments, request changes, approve, merge
- Manage notifications - triage your inbox on the go
- Interact with GitHub Copilot - chat with Copilot Chat on mobile (as of Feb 2026)
- View GitHub Actions - monitor workflows and check build status
- Manage Discussions - participate in community conversations
Both apps support:
- Native screen reader gestures (VoiceOver on iOS, TalkBack on Android)
- Dynamic text sizing
- Dark mode / high contrast
- Keyboard navigation (when using external keyboard with tablet)
Pro tip: Enable push notifications for mentions and reviews so you can respond quickly when your input is needed.
Essential tips and lesser-known features that make you a more effective contributor.
Saved replies let you create reusable text templates for common responses. Perfect for:
- Thanking first-time contributors
- Requesting more information with a friendly tone
- Explaining common setup issues
- Closing duplicate issues
- Go to github.com/settings/replies
- Click "Add a saved reply"
- Give it a short label (e.g., "welcome-first-time")
- Write your template text (can include Markdown)
- Save
- When writing any comment, press
Ctrl+.(period) to open the saved replies menu - Select your saved reply
- Edit as needed before posting
Pin important issues to the top of your repository's Issues tab. Perfect for:
- FAQs and getting started guides
- Known issues and workarounds
- Roadmap and project status updates
- Community guidelines
- Open the issue you want to pin
- In the right sidebar, click the three-dot menu (⋯)
- Select "Pin issue"
- It now appears at the top of the Issues list
You can pin up to 3 issues per repository. Pinned issues are visible to everyone, even those who haven't starred or watched your repo.
You can now pin a single comment within an issue thread to keep important information visible. Perfect for:
- Workarounds or temporary solutions
- Decisions made during discussion
- Links to related issues or PRs
- Status updates from maintainers
- Find the comment you want to pin
- Click the three-dot menu (⋯) on the comment
- Select "Pin comment"
Only repository collaborators can pin comments. There can be only one pinned comment per issue.
Share precise references to code by including line numbers in GitHub URLs.
- Single line:
github.com/owner/repo/blob/main/file.js#L42 - Line range:
github.com/owner/repo/blob/main/file.js#L42-L58
- Navigate to a file on GitHub
- Click the line number (in screen readers: navigate to the line and activate the number link)
- Hold
Shiftand click another line number to select a range - Copy the URL from your browser - the line numbers are automatically included
Screen reader tip: Line numbers are links announced as "Line 42 link" (or similar). They're in the left margin of the code view.
When you link to code on GitHub using a branch name (main, develop), that link can break if the code changes or the file moves. Permalinks use the commit SHA instead of the branch name, creating a permanent snapshot link.
Why this matters: When you file a bug report or reference code in a discussion, you want the link to show exactly what you were looking at - not what the code looks like weeks later after someone refactored it.
- View any file on GitHub
- Press
Ywhile viewing the file - the URL changes from/blob/main/file.jsto/blob/a1b2c3d4.../file.js - Copy the new URL - it now points to that specific commit
Shortcut: Y = "Yank permalink" (borrows from Vim terminology)
Not every issue is a bug or feature request. Some are questions, proposals, or open-ended conversations. GitHub Discussions provide a better home for these.
- Questions that don't require a code change ("How do I configure X?")
- Proposals that need community feedback before becoming actionable
- General discussion about the project's direction
- Show-and-tell or community showcases
- Open the issue
- In the right sidebar, click "Convert to discussion"
- Select which discussion category it belongs in
- Confirm
All comments and history are preserved. The issue is closed and replaced with a link to the new discussion.
In organizations, you can mention entire teams instead of individuals: @org-name/team-name
Example: @github/accessibility notifies everyone on GitHub's accessibility team.
- You don't need to know who's on a team - just mention the team
- Teams can subscribe to notifications as a group
- CODEOWNERS files use team mentions for automatic reviewer assignment
Permission: You can only mention teams you have visibility to. Public teams in public orgs can be mentioned by anyone.
Keep long issue descriptions or PR descriptions scannable by hiding details in collapsible sections.
<details>
<summary>Click to expand: Full error stack trace</summary>
(Your detailed content here - code blocks, lists, anything)
</details>- Long error messages or logs
- Optional context that most readers don't need
- Large screenshots or code samples
- Step-by-step troubleshooting instructions
Accessibility note: Collapsible sections are announced as "disclosure triangles" or "expandable" regions by most screen readers. The summary text is always visible.
Credit multiple people for a single commit using the Co-authored-by trailer in your commit message.
Fix keyboard navigation in modal dialog
This addresses the issue where focus was lost when the modal closed.
Co-authored-by: Alex Chen <alex@example.com>
Co-authored-by: Jordan Smith <jordan@example.com>
- Pair programming - both people get credit in the Git history
- Crediting someone who provided the solution but didn't write the code
- GitHub recognizes these trailers and shows all co-authors on the commit
Screen reader tip: When viewing a commit with co-authors on GitHub, screen readers announce "Co-authored-by" in the commit details.
Three ways to interact with a repository - each means something different:
| Action | What It Does | When to Use |
|---|---|---|
| Watch | Subscribe to notifications for activity | You want to stay updated on issues, PRs, and releases |
| Star | Bookmark a repo | You want to save it for later or show appreciation |
| Fork | Create your own copy of the repo | You want to contribute changes or use it as a starting point |
- All activity - every issue, PR, and discussion
- Participating (default) - only threads you comment on or are @mentioned in
- Releases only - just new releases
- Ignore - unsubscribe completely
Pro tip: Star repos for discovery; Watch repos you actively contribute to.
The CODEOWNERS file automatically requests reviews from specific people or teams when files in their area are changed.
Location: .github/CODEOWNERS in your repository
# Documentation team reviews all docs changes
/docs/ @org-name/docs-team
# Accessibility specialist reviews UI changes
/src/components/ @username
# Security team reviews authentication code
/src/auth/ @org-name/security-team
# Default owner for everything else
* @project-lead
- Someone opens a PR that changes files in
/docs/ - GitHub automatically requests a review from
@org-name/docs-team - The PR can't be merged until the required review is approved (if branch protection requires it)
- Ensuring domain experts review specialized code
- Distributing review responsibilities
- Preventing changes from being merged without appropriate oversight
Support open source maintainers financially through GitHub Sponsors. If a project you use has a "Sponsor" button, consider supporting them.
- Maintainers set up a Sponsors profile
- You can sponsor with a monthly recurring amount or one-time payment
- GitHub doesn't take a fee (as of 2026)
- Open source maintainers often work for free in their spare time
- Your sponsorship helps them dedicate more time to the project
- Many maintainers offer perks to sponsors (early access, prioritized issues, etc.)
- Visit a repository with a "Sponsor" button
- Click the button
- Choose a sponsorship tier
- Complete payment through GitHub Sponsors
GitHub supports several powerful Markdown features beyond the basics:
- [x] Completed task
- [ ] Pending task
- [ ] Another pending task| Left-aligned | Center-aligned | Right-aligned |
|:-------------|:--------------:|--------------:|
| Text | Text | Text |```mermaid
graph TD
A[User opens issue] --> B{Is it a bug?}
B -->|Yes| C[Label: bug]
B -->|No| D[Label: enhancement]
```textInline math: $E = mc^2$
Block math:
$$
\sum_{i=1}^{n} i = \frac{n(n+1)}{2}
$$Here is a statement that needs citation[^1].
[^1]: Source: Documentation link> [!NOTE]
> Useful information that users should know
> [!WARNING]
> Critical content requiring immediate attention
> [!TIP]
> Helpful advice for better outcomesAfter the workshop, use these resources to find your next open source contribution.
| Resource | URL | What It Does |
|---|---|---|
| Good First Issue | Good First Issue | Curated list of beginner-friendly issues across popular open source projects |
| Up For Grabs | Up For Grabs | Projects that explicitly welcome new contributors |
| GitHub Explore | GitHub Explore | Discover trending repos, topics, and collections |
| Accessibility on GitHub | Search: topic:accessibility is:public
|
Public repositories tagged with the accessibility topic |
| AT on GitHub | Search: topic:assistive-technology is:public
|
Public repositories tagged with assistive-technology |
| Filter by label | In any repo: Issues → Label → good first issue
|
Works on every public repository |
is:open is:issue label:good-first-issue topic:accessibility
is:open is:issue label:help-wanted topic:screen-reader
is:open is:issue label:accessibility no:assignee
| Resource | URL | Notes |
|---|---|---|
| WCAG 2.2 (Full Standard) | WCAG 2.2 specification | The complete Web Content Accessibility Guidelines |
| WCAG Quick Reference | WCAG 2.2 Quick Reference | Filtered, searchable version - much more practical |
| ARIA Authoring Practices Guide | ARIA Authoring Practices Guide | When and how to use ARIA roles and attributes |
| WebAIM Screen Reader Survey | WebAIM Screen Reader Survey | Real-world data on how screen reader users work |
| The A11y Project | The A11y Project | Community-driven accessibility checklist and resources |
| Deque University (free content) | Deque University | Free accessibility rules reference |
| MDN Accessibility Guide | MDN Accessibility Guide | Web accessibility fundamentals |
| Tool | URL | Notes |
|---|---|---|
| WebAIM Contrast Checker | WebAIM Contrast Checker | Check text/background color contrast against WCAG AA/AAA |
| WAVE Browser Extension | WAVE Browser Extension | Highlights accessibility issues on any webpage - Chrome, Firefox, Edge |
| Axe DevTools | Axe DevTools | Finds WCAG violations with severity levels |
| Lighthouse | In Chrome DevTools (F12 → Lighthouse tab) | Built-in auditing for accessibility, performance, and SEO |
| Resource | URL | Notes |
|---|---|---|
| Learn Git Branching | Learn Git Branching | Gamified, step-by-step challenges - branching, merging, rebasing |
| Visualizing Git | Visualizing Git | Interactive visual playground for branches and commits |
| Pro Git Book (free) | Pro Git Book | Complete reference - free online |
| Git Cheat Sheet | GitHub Git Cheat Sheet (PDF) | Quick command reference PDF |
| Resource | URL | Notes |
|---|---|---|
| Full Keyboard Shortcuts Reference | GitHub Keyboard Shortcuts documentation | Every shortcut on every page |
Press ? on any GitHub page |
- | Opens the keyboard shortcuts overlay for that specific page |
| Shortcut | What It Does |
|---|---|
? |
Open keyboard shortcuts help for current page |
G I (press G then I) |
Go to Issues tab |
G P |
Go to Pull Requests tab |
G A |
Go to Actions tab |
G C |
Go to Code tab |
/ |
Focus the search bar |
C |
Create a new issue (on Issues list page) |
E |
Archive notification (on Notifications page) |
Shift+I |
Mark notification as read |
M |
Mute thread (on Notifications page) |
Not sure where to start after the workshop? Use these suggested paths.
| Role | Start Here | Then |
|---|---|---|
| New contributor | 00-pre-workshop-setup.md |
Issues → Pull Requests → Merge Conflicts |
| Maintainer | 08-labels-milestones-projects.md |
Issue templates → Branch protection → Notifications |
| Accessibility advocate | 14-accessible-code-review.md |
Screen reader cheat sheet → Appendix C (Standards) |
| Facilitator | FACILITATOR.md |
Day 1 and Day 2 agendas → FAQ |
| Time | Suggested Path |
|---|---|
| 30 min | Pre-workshop setup → Understanding GitHub's web structure |
| 1 hour | Add: Working with Issues |
| 2 hours | Add: Pull Requests + Navigating Repositories |
| 4+ hours | All core chapters → pick one advanced appendix topic |
| Resource | URL |
|---|---|
| GitHub Accessibility Community Discussions | GitHub Community Accessibility Discussions |
| GitHub Accessibility Feedback | GitHub Accessibility Feedback Discussions |
| GitHub Accessibility Team (public presence) | GitHub Accessibility site |
| Resource | URL |
|---|---|
| Accessibility Agents Issues (bug reports, ideas) | Accessibility Agents Issues |
| Accessibility Agents Discussions | Accessibility Agents Discussions |
| Security concerns | jeff@jeffbishop.com (do not open public issues for vulnerabilities) |
| Resource | URL |
|---|---|
| A11y Slack | A11y Slack community (invite: A11y Slack invite page) |
| A11y Weekly Newsletter | A11y Weekly Newsletter |
| Inclusive Design Research Centre | Inclusive Design Research Centre |
Every guide from this workshop lives in your fork. Clone your fork once and the complete documentation works offline - no internet required.
git clone https://github.com/[your-username]/accessibility-agents.gitThe documentation set is in the docs/ folder of this learning repository (separate from the accessibility-agents fork). If your workshop facilitator shared a repository link for the learning materials, clone that too.
Back: Issue Templates Start over: README ← Reference: Screen Reader Cheat Sheet
Getting Started
Core Chapters
- 1. GitHub Web Structure
- 2. Navigating Repositories
- 3. The Learning Room
- 4. Working with Issues
- 5. Working with Pull Requests
- 6. Merge Conflicts
- 7. Culture and Etiquette
- 8. Labels, Milestones, Projects
- 9. Notifications
VS Code and Git
AI and Accessibility
Appendices
- A. Glossary
- B. Screen Reader Cheat Sheet
- C. Accessibility Standards
- D. Git Authentication
- E. Markdown
- F. Gists
- G. Discussions
- H. Releases, Tags, Insights
- I. GitHub Projects
- J. Advanced Search
- K. Branch Protection
- L. Security Features
- M. VS Code Accessibility
- N. Codespaces
- O. GitHub Mobile
- P. GitHub Pages
- Q. Actions and Workflows
- R. Profile, Sponsors, Wikis
- S. Orgs and Templates
- T. Open Source
- U. Resources
- V. Accessibility Agents Ref
- W. Copilot Reference
- X. Copilot AI Models
- Y. Workshop Materials
- Z. GitHub Skills Catalog