Appendix X: 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.
Reference companion to: All chapters | Master resource index for the entire curriculum
Everything You Need - Before, During, and After the Workshop
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.
Learning Cards: Navigating This Resource Guide
Screen reader users
- This appendix is organized as 16 numbered sections with heading levels -- press
H or 2 to jump between major sections in browse mode
- Most sections contain tables of links -- navigate tables with
T to jump to the next table, then use arrow keys to read rows and columns
- Each resource link opens in the same tab by default -- use
Ctrl+Enter (Windows) to open in a new tab and keep this reference page available
Low vision users
- Tables in this appendix have a Resource/URL/Notes column structure -- widen your browser or zoom out slightly if columns overlap at high magnification
- Link text is descriptive (resource names, not raw URLs) making it easier to scan the page visually
- Bookmark this page in your browser for quick access -- it is the single-page reference for everything from the workshop
Sighted users
- Use the Table of Contents at the top to jump directly to any of the 16 resource categories
- Each section uses a consistent table layout: Resource name (left), URL (middle), Notes (right)
- The GitHub keyboard shortcuts section (14) is worth bookmarking separately -- press
? on any GitHub page for a shortcuts overlay
Table of Contents
- 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
1. The Central Project - Accessibility Agents
The project you forked, contributed to, and carry home.
Your Personal Fork
After the workshop, your fork lives at:
https://github.com/[your-username]/accessibility-agents
Quick access from VS Code
- 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+Alt+I, or run Chat: Open Chat from the Command Palette if your keymap differs
- Type:
@daily-briefing morning briefing
Personalizing Your Fork
- Copy
preferences.example.md to preferences.md in .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
2. GitHub Accessibility Guides
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 |
3. GitHub Skills Learning Modules
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.
How GitHub Skills Works
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.
Screen Reader Navigation of a GitHub Skills Course
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
After This Workshop - Your Learning Path
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.
4. Screen Reader Downloads and Documentation
Learning Cards: Screen Reader Downloads and Setup
Screen reader users
- NVDA (free, Windows): download from nvaccess.org -- after installing, toggle browse/focus mode with
NVDA+Space and open the elements list with NVDA+F7
- JAWS (Windows): download a trial from freedomscientific.com -- Virtual PC Cursor toggle is
Insert+Z, elements list is Insert+F3
- VoiceOver (macOS/iOS): built in, no download needed -- start with
Cmd+F5 on Mac, or Settings then Accessibility then VoiceOver on iOS
Low vision users
- NVDA and JAWS both support speech and braille output simultaneously if you use a refreshable braille display
- VoiceOver on macOS integrates with Zoom (screen magnifier) -- enable both in System Settings then Accessibility for combined magnification and speech
- Narrator on Windows is built in and requires no download -- launch with
Win+Ctrl+Enter for a quick, lightweight screen reader experience
Sighted users
- NVDA is free and the most common screen reader for testing on Windows -- install it to verify your content is accessible
- VoiceOver is built into every Mac and iPhone -- toggle it with
Cmd+F5 (Mac) to quickly test how your pages sound
- The key commands listed in this section (H for headings, B for buttons, K for links) work in all major screen readers and are essential for understanding how AT users navigate
NVDA (Windows)
Key commands (quick reference)
- Toggle browse/focus mode:
NVDA+Space
- Elements list:
NVDA+F7
- Next heading:
H | Next link: K | Next button: B | Next form field: F
JAWS (Windows)
Key commands (quick reference)
- Virtual PC Cursor on/off:
Insert+Z
- Elements list:
Insert+F3
- Next heading:
H | Next link: Tab or U | Next button: B
VoiceOver (macOS / iOS - built in)
Key commands (quick reference)
- Start/stop VoiceOver:
Cmd+F5
- VO modifier:
Caps Lock or Ctrl+Option
- Rotor:
VO+U
- Next heading:
VO+Cmd+H
Other Screen Readers (Reference)
| 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 |
5. VS Code Resources
Install the GitHub PR extension quickly
- Open VS Code Extensions (
Ctrl+Shift+X)
- Search:
GitHub Pull Requests
- Install: publisher is "GitHub"
6. GitHub Copilot Resources
7. GitHub Agentic Workflows
GitHub Agentic Workflows are in technical preview as of February 2026. Access, feedback channels, and setup information:
How Agentic Workflows connect to what you learned
During the workshop, you learned:
- Standard GitHub Actions (YAML workflows - triggers, jobs, steps)
- Accessibility Agents agents (
.agent.md files - plain English instructions, Copilot Chat executor)
- GitHub Agentic Workflows (
.md files 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.
8. Spec-Driven Development - Spec Kit
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.
Quick start
uvx --from git+https://github.com/github/spec-kit.git specify init YOUR_PROJECT_NAME
Slash commands
/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.
9. GitHub CLI, Desktop, and Copilot CLI
GitHub CLI (gh)
winget install GitHub.cli
brew install gh
gh issue list
gh issue view 42
gh pr list
gh pr view 14
gh pr create
gh pr merge 14
gh repo fork
gh repo clone owner/repo
Copilot in the CLI (gh copilot)
gh extension install github/gh-copilot
gh copilot explain "git rebase -i HEAD~3"
gh copilot suggest "undo my last commit but keep the changes staged"
GitHub Desktop
10. GitHub Mobile Apps
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.
What You Can Do in GitHub Mobile
- 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
Accessibility Features
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.
11. GitHub Best Practices and Power Features
Essential tips and lesser-known features that make you a more effective contributor.
Saved Replies
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
How to set up
- 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
How to use
- When writing any comment, press
Ctrl+. (period) to open the saved replies menu
- Select your saved reply
- Edit as needed before posting
Pinned Issues
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
How to pin an issue
- 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.
Linking to Specific Lines of Code
Share precise references to code by including line numbers in GitHub URLs.
Syntax
- Single line:
github.com/owner/repo/blob/main/file.js#L42
- Line range:
github.com/owner/repo/blob/main/file.js#L42-L58
How to create these links
- Navigate to a file on GitHub
- Click the line number (in screen readers: navigate to the line and activate the number link)
- Hold
Shift and 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.
Permalinks - Stable Links That Never Break
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.
How to create a permalink
- View any file on GitHub
- Press
Y while viewing the file - the URL changes from /blob/main/file.js to /blob/a1b2c3d4.../file.js
- Copy the new URL - it now points to that specific commit
Shortcut: Y = "Yank permalink" (borrows from Vim terminology)
Converting Issues to Discussions
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.
When to convert
- 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
How to convert an issue to a discussion
- 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.
Team Mentions - Notify a Whole Group
In organizations, you can mention entire teams instead of individuals: @org-name/team-name
Example: @github/accessibility notifies everyone on GitHub's accessibility team.
Why this matters
- 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.
Collapsible Sections in Markdown
Keep long issue descriptions or PR descriptions scannable by hiding details in collapsible sections.
Syntax
<details>
<summary>Click to expand: Full error stack trace</summary>
(Your detailed content here - code blocks, lists, anything)
</details>
Use for
- 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.
Co-Authored Commits
Credit multiple people for a single commit using the Co-authored-by trailer in your commit message.
Syntax
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>
Why this matters
- 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.
Understanding Watch, Star, and Fork
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 |
Watch settings
- 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.
CODEOWNERS - Automatic Reviewer Assignment
The CODEOWNERS file automatically requests reviews from specific people or teams when files in their area are changed.
Location: .github/CODEOWNERS in your repository
Syntax
# 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
How it works
- 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)
Use for
- 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.
How it works
- 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
Advanced Markdown Features
GitHub supports several powerful Markdown features beyond the basics:
Task Lists
- [x] Completed task
- [ ] Pending task
- [ ] Another pending task
Tables with alignment
| Left-aligned | Center-aligned | Right-aligned |
|:-------------|:--------------:|--------------:|
| Text | Text | Text |
Mermaid Diagrams
```mermaid
graph TD
A[User opens issue] --> B{Is it a bug?}
B -->|Yes| C[Label: bug]
B -->|No| D[Label: enhancement]
```text
Math Expressions (LaTeX)
Inline 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
Alerts (Callout blocks)
> [!NOTE]
> Useful information that users should know
> [!WARNING]
> Critical content requiring immediate attention
> [!TIP]
> Helpful advice for better outcomes
12. Finding More Contributions
After 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 |
GitHub search queries to bookmark
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
13. Accessibility Standards and References
| 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 |
Interactive Git Learning
14. GitHub Keyboard Shortcuts
| 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 |
The most important shortcuts to memorize
| 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) |
14b. Learning Pathways
Not sure where to start after the workshop? Use these suggested paths.
By Role
| Role |
Start Here |
Then |
| New contributor |
00-pre-workshop-setup.md |
Issues → Pull Requests → Merge Conflicts |
| Maintainer |
09-labels-milestones-projects.md |
Issue templates → Branch protection → Notifications |
| Accessibility advocate |
15-code-review.md |
Screen reader cheat sheet → Appendix C (Standards) |
| Facilitator |
FACILITATOR.md |
Day 1 and Day 2 agendas → FAQ |
By Time Available
| 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 |
15. Community and Support
GitHub Accessibility
16. Your Workshop Documentation - Offline Reference
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.git
The 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.
Quick Navigation
Next: Appendix Y: Workshop Materials
Back: Appendix W: GitHub Pages
Teaching chapter: All chapters
Authoritative Sources
Use these official references when you need the current source of truth for facts in this chapter.
Section-Level Source Map
Use this map to verify facts for each major section in this file.
- Everything You Need - Before, During, and After the Workshop: GitHub Docs, home, GitHub Changelog
- 1. The Central Project - Accessibility Agents: GitHub Docs, home, GitHub Changelog, GitHub Copilot docs, Custom instructions support matrix, About custom agents
- 2. GitHub Accessibility Guides: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- 3. GitHub Skills Learning Modules: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- 4. Screen Reader Downloads and Documentation: GitHub Docs, home, GitHub Changelog, W3C Web Content Accessibility Guidelines (WCAG) 2 overview, WAI tutorials for accessible design patterns, WAI-ARIA Authoring Practices Guide
- 5. VS Code Resources: GitHub Docs, home, GitHub Changelog
- 6. GitHub Copilot Resources: GitHub Docs, home, GitHub Changelog, GitHub Copilot docs, Custom instructions support matrix, About custom agents
- 7. GitHub Agentic Workflows: GitHub Docs, home, GitHub Changelog, GitHub Copilot docs, Custom instructions support matrix, About custom agents
- 8. Spec-Driven Development - Spec Kit: GitHub Docs, home, GitHub Changelog
- 9. GitHub CLI, Desktop, and Copilot CLI: GitHub Docs, home, GitHub Changelog, GitHub Copilot docs, Custom instructions support matrix, About custom agents
- 10. GitHub Mobile Apps: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- 11. GitHub Best Practices and Power Features: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- How it works: GitHub Docs, home, GitHub Changelog
- Use for: GitHub Docs, home, GitHub Changelog
- 12. Finding More Contributions: GitHub Docs, home, GitHub Changelog
- 13. Accessibility Standards and References: GitHub Docs, home, GitHub Changelog, W3C Web Content Accessibility Guidelines (WCAG) 2 overview, WAI tutorials for accessible design patterns, WAI-ARIA Authoring Practices Guide