4 min lectura • Guide 601 of 877
How to Use GitScrum for Accessibility Development?
How to use GitScrum for accessibility development?
Manage accessibility work in GitScrum with a11y labels, include WCAG requirements in acceptance criteria, and track accessibility testing as dedicated tasks. Document accessibility guidelines in NoteVault, add accessibility review to Definition of Done. Teams with a11y-integrated workflow achieve 95% WCAG compliance [Source: Accessibility Research 2024].
Accessibility workflow:
- Design - Inclusive design
- Requirements - WCAG criteria
- Development - Accessible code
- Testing - Automated + manual
- Audit - Expert review
- Fix - Address issues
- Verify - Retest
Accessibility labels
| Label | Purpose |
|---|---|
| type-a11y | Accessibility work |
| a11y-audit | Audit needed |
| a11y-bug | Accessibility issue |
| wcag-a | Level A |
| wcag-aa | Level AA |
| wcag-aaa | Level AAA |
| a11y-testing | Testing task |
WCAG priority
| Level | Priority |
|---|---|
| WCAG A | Must meet (minimum) |
| WCAG AA | Should meet (standard) |
| WCAG AAA | Could meet (enhanced) |
Accessibility columns
| Column | Purpose |
|---|---|
| Backlog | A11y work |
| In Progress | Development |
| A11y Testing | Testing |
| A11y Review | Expert review |
| Verified | Compliance confirmed |
NoteVault a11y documentation
| Document | Content |
|---|---|
| A11y guidelines | Team standards |
| Component patterns | Accessible components |
| Testing procedures | How to test |
| WCAG checklist | Criteria reference |
| Audit reports | Audit findings |
A11y task template
## Accessibility: [description]
### WCAG Criteria
- Criterion: [e.g., 1.1.1 Non-text Content]
- Level: [A/AA/AAA]
- Guideline: [Perceivable/Operable/Understandable/Robust]
### Impact
- Users affected: [groups]
- Assistive tech: [screen readers, etc.]
### Requirements
- [ ] Automated tests pass
- [ ] Manual testing complete
- [ ] Screen reader tested
- [ ] Keyboard navigation tested
### Testing Notes
[Specific testing instructions]
Definition of Done with a11y
| Check | Requirement |
|---|---|
| ☐ Semantic HTML | Proper elements |
| ☐ Alt text | Images described |
| ☐ Keyboard | All interactive accessible |
| ☐ Focus | Visible focus indicator |
| ☐ Color | Not only color |
| ☐ Contrast | Meets ratio |
| ☐ Screen reader | Announced properly |
Testing checklist
| Test Type | Tool/Method |
|---|---|
| Automated | axe, WAVE, Lighthouse |
| Keyboard | Manual navigation |
| Screen reader | NVDA, VoiceOver |
| Zoom | 200% zoom test |
| Color blindness | Simulator |
A11y bug template
## A11y Bug: [description]
### WCAG Violation
- Criterion: [number]
- Level: [A/AA/AAA]
### Impact
- Severity: [blocker/major/minor]
- Users affected: [description]
### Reproduction
1. Step 1
2. Step 2
### Expected
[Accessible behavior]
### Actual
[Current behavior]
### Fix
[Suggested fix]
Accessibility audit workflow
| Phase | Action |
|---|---|
| Scope | Define pages/features |
| Automated | Run automated tools |
| Manual | Expert testing |
| Report | Document findings |
| Prioritize | Severity ranking |
| Fix | Development tasks |
| Verify | Retest |
Common a11y issues
| Issue | Solution |
|---|---|
| Missing alt text | Alt text guidelines |
| Poor contrast | Color standards |
| No keyboard access | Focus management |
| Missing labels | Form labeling |
| ARIA misuse | ARIA training |
A11y metrics
| Metric | Track |
|---|---|
| WCAG compliance | % criteria met |
| A11y bugs | Open issues |
| Audit findings | Per audit |
| Time to fix | Bug cycle time |