GitScrum / Docs
Todas as Boas Práticas

Desenvolvimento de Acessibilidade a11y | GitScrum

Gerencie desenvolvimento de acessibilidade a11y usando GitScrum. Rastreie compliance WCAG, coordene testes de acessibilidade e melhore inclusividade.

4 min de leitura

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

    LabelPurpose
    type-a11yAccessibility work
    a11y-auditAudit needed
    a11y-bugAccessibility issue
    wcag-aLevel A
    wcag-aaLevel AA
    wcag-aaaLevel AAA
    a11y-testingTesting task

    WCAG priority

    LevelPriority
    WCAG AMust meet (minimum)
    WCAG AAShould meet (standard)
    WCAG AAACould meet (enhanced)

    Accessibility columns

    ColumnPurpose
    BacklogA11y work
    In ProgressDevelopment
    A11y TestingTesting
    A11y ReviewExpert review
    VerifiedCompliance confirmed

    NoteVault a11y documentation

    DocumentContent
    A11y guidelinesTeam standards
    Component patternsAccessible components
    Testing proceduresHow to test
    WCAG checklistCriteria reference
    Audit reportsAudit 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

    CheckRequirement
    ☐ Semantic HTMLProper elements
    ☐ Alt textImages described
    ☐ KeyboardAll interactive accessible
    ☐ FocusVisible focus indicator
    ☐ ColorNot only color
    ☐ ContrastMeets ratio
    ☐ Screen readerAnnounced properly

    Testing checklist

    Test TypeTool/Method
    Automatedaxe, WAVE, Lighthouse
    KeyboardManual navigation
    Screen readerNVDA, VoiceOver
    Zoom200% zoom test
    Color blindnessSimulator

    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

    PhaseAction
    ScopeDefine pages/features
    AutomatedRun automated tools
    ManualExpert testing
    ReportDocument findings
    PrioritizeSeverity ranking
    FixDevelopment tasks
    VerifyRetest

    Common a11y issues

    IssueSolution
    Missing alt textAlt text guidelines
    Poor contrastColor standards
    No keyboard accessFocus management
    Missing labelsForm labeling
    ARIA misuseARIA training

    A11y metrics

    MetricTrack
    WCAG compliance% criteria met
    A11y bugsOpen issues
    Audit findingsPer audit
    Time to fixBug cycle time

    Related articles