Polish: remove em/en-dashes, fix http to https, remove sign language placeholder, remove practice repo link, fix registration URLs, remove emojis from workflow

Author: accesswatch

.github/ISSUE_TEMPLATE/accessibility-bug.yml

@@ -15,15 +15,15 @@ body:
       label: Type of Accessibility Issue
       description: Which category best describes what you encountered?
       options:
-        - Keyboard navigation — cannot reach or operate a control with keyboard only
-        - Screen reader — missing, incorrect, or confusing announcements
-        - Focus management — focus jumps unexpectedly or is lost
-        - Heading structure — headings skipped, missing, or in wrong order
-        - Link / button labels — unlabeled, ambiguous, or "click here"
-        - Color / contrast — text or controls are hard to distinguish
-        - Images — missing or inadequate alternative text
-        - Forms — fields not labeled or error messages not announced
-        - Time limits — content changes or disappears before I can act
+        - Keyboard navigation - cannot reach or operate a control with keyboard only
+        - Screen reader - missing, incorrect, or confusing announcements
+        - Focus management - focus jumps unexpectedly or is lost
+        - Heading structure - headings skipped, missing, or in wrong order
+        - Link / button labels - unlabeled, ambiguous, or "click here"
+        - Color / contrast - text or controls are hard to distinguish
+        - Images - missing or inadequate alternative text
+        - Forms - fields not labeled or error messages not announced
+        - Time limits - content changes or disappears before I can act
         - Other (describe below)
     validations:
       required: true
@@ -89,7 +89,7 @@ body:
     id: os
     attributes:
       label: Operating System and Version
-      description: For example — Windows 11, macOS Sonoma 14.3, iOS 17.2
+      description: For example - Windows 11, macOS Sonoma 14.3, iOS 17.2
       placeholder: Windows 11
     validations:
       required: true
@@ -98,7 +98,7 @@ body:
     id: wcag
     attributes:
       label: Relevant WCAG Success Criterion (if known)
-      description: If you know which WCAG criterion applies, select it. Leave blank if unsure — the team will assess.
+      description: If you know which WCAG criterion applies, select it. Leave blank if unsure - the team will assess.
       options:
         - "1.1.1 Non-text Content (alt text)"
         - "1.3.1 Info and Relationships (semantic structure)"
@@ -135,6 +135,6 @@ body:
     id: additional
     attributes:
       label: Additional Context
-      description: Anything else that might help — screenshots with alt text, screen reader log excerpts, or links to related issues.
+      description: Anything else that might help - screenshots with alt text, screen reader log excerpts, or links to related issues.
     validations:
       required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1,20 +1,20 @@
 blank_issues_enabled: false
 contact_links:
-  - name: "Register for GIT Going with GitHub (March 6–7, 2026)"
-    url: https://github.com/BITS-ACB/git-going-with-github/issues/new?template=workshop-registration.yml&title=%5BREGISTER%5D+
+  - name: "Register for GIT Going with GitHub (March 6-7, 2026)"
+    url: https://github.com/BITS-ACB/git-going-with-github/issues/new?template=workshop-registration.yml&title=%5BREGISTER%5D+GIT+Going+with+GitHub+-+March+2026
     about: Sign up for the two-day accessible open source workshop by BITS. Free, online, 75 seats.
-  - name: GitHub Skills — Introduction to GitHub
+  - name: GitHub Skills - Introduction to GitHub
     url: https://github.com/skills/introduction-to-github
-    about: Interactive module — branches, commits, pull requests, and merge. Mona guides you step by step.
-  - name: GitHub Skills — Communicate Using Markdown
+    about: Interactive module - branches, commits, pull requests, and merge. Mona guides you step by step.
+  - name: GitHub Skills - Communicate Using Markdown
     url: https://github.com/skills/communicate-using-markdown
-    about: Interactive module — headings, emphasis, links, code blocks, task lists, and tables.
-  - name: GitHub Skills — Review Pull Requests
+    about: Interactive module - headings, emphasis, links, code blocks, task lists, and tables.
+  - name: GitHub Skills - Review Pull Requests
     url: https://github.com/skills/review-pull-requests
-    about: Interactive module — Mona creates a real PR in your account for you to review.
+    about: Interactive module - Mona creates a real PR in your account for you to review.
   - name: Workshop Documentation
     url: https://bits-acb.github.io/git-going-with-github/
-    about: Full workshop guide — start here if you are new to this repository.
-  - name: Discussion Forum — Questions, Introductions, Ideas
+    about: Full workshop guide - start here if you are new to this repository.
+  - name: Discussion Forum - Questions, Introductions, Ideas
     url: https://github.com/BITS-ACB/git-going-with-github/discussions
     about: Ask questions, connect with other participants, and share ideas before, during, and after the workshop.

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -45,7 +45,7 @@ body:
     id: contribution
     attributes:
       label: Are you able to help implement this?
-      description: No commitment required — just helps with planning.
+      description: No commitment required - just helps with planning.
       options:
         - label: Yes, I can open a pull request with the change
         - label: I can provide research, examples, or feedback but cannot write the change

.github/ISSUE_TEMPLATE/workshop-registration.yml

@@ -1,6 +1,6 @@
-name: "Workshop Registration — GIT Going with GitHub"
-description: "Register for the GIT Going with GitHub workshop (March 6–7, 2026)"
-title: "[REGISTER] GIT Going with GitHub — March 2026"
+name: "Workshop Registration - GIT Going with GitHub"
+description: "Register for the GIT Going with GitHub workshop (March 6-7, 2026)"
+title: "[REGISTER] GIT Going with GitHub - March 2026"
 labels: ["registration"]
 assignees: []
 body:
@@ -10,11 +10,11 @@ body:
         ## Welcome! You are registering for GIT Going with GitHub.
 
         **Dates:** Friday, March 6 and Saturday, March 7, 2026
-        **Time:** 12:00 PM — 8:00 PM Eastern (both days)
+        **Time:** 12:00 PM - 8:00 PM Eastern (both days)
         **Cost:** Free
         **Capacity:** 75 participants
 
-        Filling out this form is your first GitHub interaction — and it counts. You are already learning. All fields below are accessible with NVDA, JAWS, and VoiceOver.
+        Filling out this form is your first GitHub interaction - and it counts. You are already learning. All fields below are accessible with NVDA, JAWS, and VoiceOver.
 
   - type: input
     id: first-name
@@ -56,12 +56,12 @@ body:
     id: proficiency
     attributes:
       label: GitHub Proficiency Level
-      description: How would you describe your current experience with GitHub? There is no wrong answer — this helps us prepare the right level of support for you.
+      description: How would you describe your current experience with GitHub? There is no wrong answer - this helps us prepare the right level of support for you.
       options:
-        - "Brand new — I have never used GitHub before"
-        - "Beginner — I have a GitHub account but have not done much with it"
-        - "Intermediate — I have created repositories, filed issues, or opened pull requests"
-        - "Experienced — I use GitHub regularly for projects or work"
+        - "Brand new - I have never used GitHub before"
+        - "Beginner - I have a GitHub account but have not done much with it"
+        - "Intermediate - I have created repositories, filed issues, or opened pull requests"
+        - "Experienced - I use GitHub regularly for projects or work"
     validations:
       required: true
 
@@ -85,9 +85,8 @@ body:
       label: Questions or Accommodations
       description: Any questions about the workshop, or accommodations we should arrange? Leave blank if none.
       placeholder: |
-        I need a sign language interpreter.
         Can I attend only Day 1?
-        I use a refreshable braille display — will that work?
+        I use a refreshable braille display - will that work?
     validations:
       required: false
 

.github/README.md

@@ -160,10 +160,10 @@ Adjust PR thresholds and challenge lists as needed.
 ### Validation Rules (`.github/scripts/validate-pr.js`)
 
 Customize checks:
-- `checkIssueReference()` — Require issue link patterns
-- `checkDescription()` — Minimum character count (default: 50)
-- `checkFileLocation()` — Allowed directories (default: learning-room/)
-- `validateMarkdownAccessibility()` — A11y rules (headings, links, alt text)
+- `checkIssueReference()` - Require issue link patterns
+- `checkDescription()` - Minimum character count (default: 50)
+- `checkFileLocation()` - Allowed directories (default: learning-room/)
+- `validateMarkdownAccessibility()` - A11y rules (headings, links, alt text)
 
 Add new validation functions to `required` or `suggestions` arrays.
 
@@ -371,16 +371,16 @@ Edit `.github/data/challenge-progression.json`:
 ## Documentation Map
 
 **For Students:**
-- [Automation Guide](../learning-room/AUTOMATION.md) — How bot works, interpreting feedback
-- [Learning Paths](docs/LEARNING_PATHS.md) — Skill progression, challenge details
-- [Challenges List](../learning-room/docs/CHALLENGES.md) — Available challenges
-- [Group Challenges](../learning-room/docs/GROUP_CHALLENGES.md) — Collaborative exercises
+- [Automation Guide](../learning-room/AUTOMATION.md) - How bot works, interpreting feedback
+- [Learning Paths](docs/LEARNING_PATHS.md) - Skill progression, challenge details
+- [Challenges List](../learning-room/docs/CHALLENGES.md) - Available challenges
+- [Group Challenges](../learning-room/docs/GROUP_CHALLENGES.md) - Collaborative exercises
 
 **For Facilitators:**
-- [Implementation Guide](docs/IMPLEMENTATION_GUIDE.md) — Setup instructions
-- [Facilitator Guide](../FACILITATOR.md) — Workshop facilitation (includes automation section)
-- [Workflow Files](workflows/) — Automation source code
-- [Data Files](data/) — Configuration (roster, progression)
+- [Implementation Guide](docs/IMPLEMENTATION_GUIDE.md) - Setup instructions
+- [Facilitator Guide](../FACILITATOR.md) - Workshop facilitation (includes automation section)
+- [Workflow Files](workflows/) - Automation source code
+- [Data Files](data/) - Configuration (roster, progression)
 
 ---
 
@@ -424,11 +424,11 @@ Found a bug? Have a suggestion?
 
 This automation system was designed with these principles:
 
-**Accessibility First** — Fully screen reader accessible  
-**Educational Focus** — Teaches, doesn't just check  
-**Human-Centered** — Augments, not replaces, human review  
-**Professional Experience** — Mirrors real CI/CD workflows  
-**Community Building** — Encourages collaboration and support  
+**Accessibility First** - Fully screen reader accessible  
+**Educational Focus** - Teaches, doesn't just check  
+**Human-Centered** - Augments, not replaces, human review  
+**Professional Experience** - Mirrors real CI/CD workflows  
+**Community Building** - Encourages collaboration and support  
 
 Built for the Open Source Assistive Technology Hackathon workshop.
 

.github/agents/analytics.agent.md

@@ -6,7 +6,7 @@ tools:
   - fetch
 ---
 
-You are a team analytics agent for open source maintainers and contributors. You surface patterns in contribution data that are difficult to see by manually reading GitHub Insights — and you present them in a format navigable by screen reader.
+You are a team analytics agent for open source maintainers and contributors. You surface patterns in contribution data that are difficult to see by manually reading GitHub Insights - and you present them in a format navigable by screen reader.
 
 ## Behavior
 
@@ -29,7 +29,7 @@ When asked about review times:
 When asked about frequently changed files:
 - Identify files changed in more than 30% of recent commits
 - Note: high-churn files may indicate instability, unclear ownership, or areas needing refactoring
-- Do not make judgments — report what the data shows
+- Do not make judgments - report what the data shows
 
 ### Contributor Distribution
 
@@ -46,10 +46,10 @@ When asked to summarize contribution during a workshop or event:
 ## Output Format
 
 ```
-## Analytics Report — [repository] — [time window]
+## Analytics Report - [repository] - [time window]
 
 ### Summary
-[2–3 sentences characterizing the period]
+[2-3 sentences characterizing the period]
 
 ### Contribution Volume
 - Commits: [N]
@@ -63,7 +63,7 @@ When asked to summarize contribution during a workshop or event:
 - Unique PR authors: [N]
 - Unique reviewers: [N]
 Top contributors:
-1. [username] — [N] commits, [N] PRs
+1. [username] - [N] commits, [N] PRs
 2. ...
 
 ### Review Health
@@ -72,7 +72,7 @@ Top contributors:
 - PRs waiting > 7 days: [N] ([list titles if ≤ 5])
 
 ### Frequently Changed Files
-1. [filename] — changed in [N]% of commits
+1. [filename] - changed in [N]% of commits
 2. ...
 
 ### Notes
@@ -81,6 +81,6 @@ Top contributors:
 
 ## Accessibility Requirements
 
-- Never use tables in the output — screen reader navigation through data tables is slower than labeled lists
-- Label every number — never output a bare number without context
+- Never use tables in the output - screen reader navigation through data tables is slower than labeled lists
+- Label every number - never output a bare number without context
 - Use heading level 2 for the report title, level 3 for each section

.github/agents/daily-briefing.agent.md

@@ -1,6 +1,6 @@
 ---
 name: daily-briefing
-description: Morning situation report — sweeps your repositories and surfaces what needs your attention today
+description: Morning situation report - sweeps your repositories and surfaces what needs your attention today
 tools:
   - githubRepo
   - fetch
@@ -25,10 +25,10 @@ When a user asks for a morning briefing, a daily summary, or asks "what needs my
 
 ## Output Format
 
-Use this structure every time. Screen reader users navigate by heading — maintain this hierarchy precisely.
+Use this structure every time. Screen reader users navigate by heading - maintain this hierarchy precisely.
 
 ```
-## Morning Briefing — [Date]
+## Morning Briefing - [Date]
 
 ### Needs Your Action
 
@@ -47,7 +47,7 @@ Use this structure every time. Screen reader users navigate by heading — maint
 [List each issue: title, number, repository, labels]
 
 #### Your PRs With New Activity
-[List each PR: title, number, repository, what changed — new comment, review submitted, etc.]
+[List each PR: title, number, repository, what changed - new comment, review submitted, etc.]
 
 #### Security and Dependabot Alerts
 [List any alerts: repository, type, severity]
@@ -59,9 +59,9 @@ Use this structure every time. Screen reader users navigate by heading — maint
 ## Accessibility Requirements
 
 - Use heading level 2 for "Morning Briefing", level 3 for sections, level 4 for subsections
-- Never use bare URLs — always use descriptive link text followed by the URL in parentheses
-- If a list is empty, say explicitly "None" — do not omit the section
-- Do not use tables for the briefing output — lists are more predictable to navigate
+- Never use bare URLs - always use descriptive link text followed by the URL in parentheses
+- If a list is empty, say explicitly "None" - do not omit the section
+- Do not use tables for the briefing output - lists are more predictable to navigate
 
 ## Tone