Skip to main content
Founder / Planning Tool

Accessibility Issue Triage Workflow

A founder planning workflow for reviewing, prioritizing, and resolving accessibility issues without hiding unresolved problems.

This is not a live triage system

  • ▸This does not collect issue reports from users
  • ▸This does not store user feedback
  • ▸This does not certify accessibility
  • ▸This does not replace professional review
  • ▸This is a static planning workflow for founder/private use
This workflow is a planning tool only. No user issue reports are collected. Safety-critical warnings must never be weakened during any triage or remediation step.

Do Not Do This

Do not delete safety warnings just to shorten or simplify a page

Do not hide known issues or remove them from the issues board without full verification

Do not mark an issue Verified without actually re-testing it

Do not collect medical, disability, diagnosis, or treatment information during triage

Do not collect names or emails without a reviewed privacy process

Do not claim compliance just because a checklist item was checked

Do not treat private-preview founder notes as a completed professional audit

Triage Workflow

1

Receive or notice an issue privately (from personal testing, private review, or tester notes)

2

Confirm no emergency or safety risk is involved — if there is a safety risk, fix it immediately and do not defer it

3

Identify the route where the issue occurs

4

Identify the issue category (keyboard, labels, screen reader, mobile, safety warning, etc.)

5

Assign a severity level (Critical, High, Medium, or Low)

6

Assign a status (New, Reviewing, Needs fix, Fixed pending review, Verified, or Deferred)

7

Check whether safety warnings on that page are affected — if yes, safety clarity takes priority

8

Plan the smallest safe fix that resolves the issue without weakening warnings

9

Re-test with keyboard and on mobile after the fix is applied

10

Update the Known Accessibility Issues Board with the new status

11

Update Accessibility Release Notes or Changelog if the fix represents meaningful improvement

12

Leave deferred issues visible — do not hide or delete them from the issues board

Severity Decision Guide

Critical

Emergency or safety warning hidden or unreadable, page completely unusable, privacy warning missing from sensitive content, keyboard trap preventing exit

High

Core user task blocked (form unusable, navigation broken, Help Finder unreachable), screen reader cannot announce key content

Medium

Confusing label, unclear button, awkward mobile layout, color contrast below preference (but not safety-impacting), form tab order slightly off

Low

Polish, wording clarity, spacing, visual refinement, minor copy improvement

Issue Category Guide

  • Reading comfort (text size, contrast, spacing)
  • Keyboard navigation (tab order, focus, shortcuts)
  • Screen reader review (announcements, headings, links)
  • Focus order (logical reading sequence, skip link)
  • Forms and labels (visible labels, input instructions)
  • Error messages (plain text, next steps, not color-only)
  • ARIA and icon buttons (aria-label, role, state)
  • Mobile layout (tap targets, stacking, overflow)
  • Print and large print (disclaimer survival, readability)
  • Safety warnings (text-only, prominence, completeness)
  • Privacy warnings (placement, clarity, do-not-enter reminders)

Example Triage Decisions

Static planning examples only. Not from real user reports.

Focus ring hard to see on a button

MediumReviewing/checklists

Category: Keyboard navigation

Safe next step: Compare focus-visible CSS to contrast ratio. Increase ring size or color if needed. Re-test with keyboard after change. No safety warnings involved.

Warning box text wraps awkwardly on small mobile screen

HighNeeds fix/safety-first

Category: Safety warnings / Mobile layout

Safe next step: Fix layout without removing any warning text. Safety clarity is the priority — do not shorten the warning to fix the layout. Re-test on narrow screen after change.

Print summary of checklist missing SafetyNotice disclaimer

MediumNew/checklists

Category: Print / large print

Safe next step: Verify SafetyNotice text survives @media print CSS. If hidden, add print-visible class. Do not remove the SafetyNotice from screen view.

What this page does not claim

  • ✗No live issue triage system
  • ✗No user reports are collected or stored
  • ✗No accessibility certification
  • ✗No legal compliance
  • ✗No professional audit completion

Accessibility Issue Triage Workflow Checklist

0/14
Confirmed 'not a live triage system' warning is visible
Confirmed 12-step triage workflow is present
Confirmed step 2 says to fix safety risks immediately — do not defer
Confirmed step 12 says to leave deferred issues visible
Confirmed severity guide has Critical, High, Medium, Low
Confirmed Critical includes safety warnings and keyboard traps
Confirmed issue category guide has at least 10 categories
Confirmed Do Not Do This box is visible with at least 7 items
Confirmed 3 static example triage cards are present
Confirmed no real user reports are referenced
Confirmed safety warnings are not weakened in any example
No live triage system claim — confirmed
No certification claim — confirmed
No legal compliance claim — confirmed