Skip to content

docs: framework at 20 of 24 (respond to reports) - #278

Merged
accesswatch merged 1 commit into
mainfrom
docs/framework-respond-action
Oct 29, 2026
Merged

accesswatch merged 1 commit into
mainfrom
docs/framework-respond-action

Conversation

@accesswatch

Copy link
Copy Markdown
Collaborator

The Open Source Accessibility Framework action "Respond constructively to accessibility reports" (respond-constructively-to-accessibility-reports, community action 2) is now checked on this project's public tracking issue, which shows 20 of 24. This updates the repository's records to match.

Why the action is done:

  • "How we respond" in ACCESSIBILITY.md gives the guidance.
  • Since 2026-10-29 the accessibility-reports workflow (.github/workflows/accessibility-reports.yml) acknowledges every report, reminds the owner after 5 business days without a reply, reopens a report closed without a documented outcome (a merged fix or an Outcome: line), and invites the reporter to confirm a fix.
  • The owner, Jeff Bishop, decided that past reports are not reopened.

No other framework action changed.

Files changed: ACCESSIBILITY.md and html/ACCESSIBILITY.html (the count was already 20 of 24; this adds the evidence for community action 2)


Generated by Claude Code

The Open Source Accessibility Framework action "Respond constructively to
accessibility reports" (community action 2) is now checked on the project's
public tracking issue. How we respond is in ACCESSIBILITY.md; since
2026-10-29 the accessibility-reports workflow acknowledges every report,
reminds the owner after 5 business days without a reply, reopens a report
closed without a documented outcome, and invites the reporter to confirm a
fix. Past reports are not reopened.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PmRBrUTuhzYnQBFxUCN6Vr
@github-actions

Copy link
Copy Markdown
Contributor

Peer Review Assigned

Hi @accesswatch! Your PR has been automatically paired with @taylorarndt for peer review.

For @taylorarndt:

This is a great opportunity to practice code review skills! Here's what to look for:

Content Quality:

  • Does the change accomplish what the issue describes?
  • Is the writing clear and helpful?
  • Are there any typos or grammar issues?

Accessibility:

  • Proper heading hierarchy (H1 → H2 → H3, no skips)?
  • Descriptive link text (not "click here")?
  • Alt text on images?
  • [TODO] markers removed?

Documentation:

  • Code blocks are properly formatted?
  • Tables have headers?
  • References/links work correctly?

Review Guidelines:

  • Be kind and constructive
  • Suggest improvements, don't just point out problems
  • Ask questions if something is unclear
  • Approve when ready or request changes with explanation

Resources:


Pairing by Learning Room Grouping Engine

@accesswatch
accesswatch merged commit 76b14cd into main Oct 29, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants