` elements - NVDA announces "article" as you navigate with H #### JAWS note - `A` key navigates `

` elements - useful for jumping between replies - Use Forms Mode for the reply editor #### VoiceOver note - VO+Right to read through content - VO+Command+L to list all links (useful for navigating many replies quickly) - VO+Space on the reply field to enter interaction mode ## 9. Organization-Level Discussions Some organizations enable Discussions at the organization level, separate from any repository. These work identically to repository discussions but span the whole organization. Common uses: - Org-wide announcements - Community introductions ("Introduce yourself" pinned thread) - Cross-repo feature brainstorming - Community spotlights and events Find them at `github.com/ORGANIZATION/discussions`. ## 10. Accessibility Agents: What's Different Here Accessibility Agents prompts currently operate on **issues, PRs, and code** - not directly on Discussions. If you want to respond to a discussion using Accessibility Agents: 1. Copy the discussion URL or content 2. Use `/issue-reply` with the content pasted in: the agent will draft a thoughtful, accessible response 3. Paste the result back into the discussion reply editor This works well for first-response drafts on Q&A threads or community questions in your area of expertise. *Return to: [Resources](appendix-x-resources.md) | [Glossary](appendix-a-glossary.md)* --- ## GitHub Gists > > **Listen to Episode 23:** [GitHub Gists](https://lp.csedesigns.com/ggg/PODCASTS.html) - a conversational audio overview of this chapter. Listen before reading to preview the concepts, or after to reinforce what you learned. ## Shareable Code Snippets and Notes > Gists are a simple way to share code snippets, notes, or small files without creating a full repository. Think of them as lightweight, version-controlled pastebins. ### Learning Cards: GitHub Gists

Screen reader users

- On the Gist creation page at gist.github.com, press `D` to jump to the main landmark, then `F` to navigate form fields: Description, Filename, Content, and Visibility buttons - Your Gists page lists each gist as an `H2` heading with its description -- press `2` or `H` to jump between gists - Gists are full Git repositories -- you can clone them with `git clone` and edit locally using your usual screen reader workflow in VS Code

Low vision users

- Gist pages use syntax highlighting matching GitHub's current theme -- switch between light and dark mode for comfortable reading - Public and secret gists look identical on the page; the only difference is the URL visibility -- check the "Create secret gist" or "Create public gist" button label before submitting - The revision history link appears at the top of any gist -- click "Revisions" to see a diff view of every edit

Sighted users

- Gists live at gist.github.com, separate from regular repositories -- each gist shows a syntax-highlighted code block with filename tabs at the top - The visibility selector is a split button at the bottom of the editor -- the dropdown arrow reveals "Create secret gist" vs "Create public gist" - You can add multiple files to one gist using the "Add file" button below the first editor pane

## What Is a Gist? A Gist is a Git repository that holds a single file or a small collection of files. Every Gist: - Has its own URL (e.g., `gist.github.com/username/a1b2c3d4`) - Is version-controlled (you can see edit history) - Can be **public** (anyone can see) or **secret** (only people with the link can see) - Supports Markdown rendering - Can be embedded in web pages - Can be cloned, forked, and starred just like repos **Secret does not mean private.** Anyone with the URL can view a secret Gist. It's just not listed publicly on your profile. ## When to Use a Gist vs a Repository | Use a Gist When... | Use a Repository When... | | -------------------- | -------------------------- | | Sharing a single code snippet | Building a full project | | Posting configuration examples | Collaborating with multiple people | | Quick notes or documentation | Need issues, PRs, or project management | | Sharing logs or error messages | Want CI/CD and automated checks | | Small utility scripts | Need multiple branches | ## Creating a Gist ### Via GitHub Web Interface 1. Navigate to [gist.github.com](https://gist.github.com) 2. **Gist description:** A short title (e.g., "NVDA configuration for GitHub") 3. **Filename:** Name your file with extension (e.g., `nvda-config.txt`, `script.py`, `notes.md`) 4. **Content:** Paste or type your code/text 5. **Visibility:** - Select **"Create public gist"** for openly shareable content - Select **"Create secret gist"** for link-only sharing 6. The Gist is created with a unique URL you can share #### Screen reader navigation - `D` to cycle landmarks to "Main" - `F` to navigate form fields - Tab through: Description → Filename → Content textbox → Visibility buttons ### Adding Multiple Files to a Gist You can add multiple files to a single Gist: 1. After typing the first filename and content, select **"Add file"** (button below the editor) 2. Repeat for each additional file 3. Create the Gist **Use case:** Share related config files together (e.g., `.vscode/settings.json` + `.vscode/keybindings.json`) ### Learning Cards: Creating a Gist **Screen reader users:** - On the Gist creation page at gist.github.com, press `D` to jump to the main landmark, then `F` to navigate form fields in order: Description, Filename, Content textarea, and visibility buttons - The visibility selector is a split button -- the main button creates a public gist; Tab to the dropdown arrow next to it and press Enter to reveal the "Create secret gist" option - Each filename field has a corresponding content textarea directly below it -- after filling one file, Tab to the "Add file" button to add another file to the same gist **Low-vision users:** - The Gist editor uses the same syntax highlighting as regular GitHub files -- your current theme applies; increase font size in browser zoom for comfortable editing - The split button for public vs. secret visibility is at the bottom of the form -- the two options look nearly identical; read the button label carefully ("Create public gist" vs. "Create secret gist") before clicking - The "Add file" button appears below the first file editor as a small text link -- zoom in to find it; each additional file gets its own filename field and content textarea **Sighted users:** - The Gist creation form has three main fields stacked vertically: description at the top, then filename, then a large code editor -- fill all three before choosing visibility - The visibility split button at the bottom-right has a dropdown arrow -- click the arrow to choose between public and secret; the default (larger) button creates a public gist - Add multiple files to a single gist using the "Add file" link below the editor -- multi-file gists are useful for sharing related configurations or code snippets together ## Editing a Gist 1. Navigate to your Gist's URL 2. Select **"Edit"** (button in the top-right) 3. Make your changes 4. Select **"Update public gist"** or **"Update secret gist"** Every edit creates a new revision. Click **"Revisions"** to see the full edit history. ## Embedding a Gist You can embed Gists in web pages, blog posts, or documentation: ```html ``` GitHub renders it as a formatted code block with syntax highlighting and a link back to the Gist. **Accessibility note:** Embedded Gists are `