GSA/accessibility-for-teams

Issues

• Security Policy violation Branch Protection

  #118 opened 9 months ago by gsa-allstar
  28

• Accessibility for Teams - Developers - Images - Confusing Text

  #112 opened a year ago by jfc3-dol
  1

• Update to USWDS 2.13.2

  #98 opened 2 years ago by mejiaj
  1

• Simplify SASS structure

  #99 opened 2 years ago by mejiaj
  1

• Update uswds from 2 to 3

  #101 opened 2 years ago by nick-mon1
  0

• UX Inclusive Design Page Broken Link

  #71 opened 3 years ago by jfc3-dol
  2

• Broken on the Visual Design Forms Page

  #76 opened 3 years ago by jfc3-dol
  1

• Humanize Accessibility Page Broken Link

  #72 opened 3 years ago by jfc3-dol
  2

• Confusing Text on the UX Images Page

  #74 opened 3 years ago by jfc3-dol
  2

• Redirected Link on the Visual Design Typography Page

  #75 opened 3 years ago by jfc3-dol
  2

• Broken Link on the UX Navigation Shortcuts Page

  #73 opened 3 years ago by jfc3-dol
  2

• Broken Link to Federalist in Footer

  #69 opened 3 years ago by brickman1444
  1

• consolidate GSA accessibility sites?

  #44 opened 5 years ago by afeld
  1

• Integrate pa11y CI to catch errors

  #66 opened 4 years ago by mgifford
  0

• Text, Links & Focused Links

  #65 opened 4 years ago by mgifford
  0

• Lead by example

  #64 opened 4 years ago by mgifford
  0

• Permanent, Temporary & Situational Disabilities

  #63 opened 4 years ago by mgifford
  0

• Mobile compatability testing/review

  #60 opened 5 years ago by iamjolly
  0

• Usability testing plan and execution

  #59 opened 5 years ago by iamjolly
  0

• Ensure the content does not duplicate content maintained by an authoritative source

  #58 opened 5 years ago by iamjolly
  0

• Follow GSA design and branding guidelines

  #57 opened 5 years ago by iamjolly
  0

• Screen reader section should mention interaction modes

  #50 opened 5 years ago by brennanyoung
  1

• WCAG 2+

  #41 opened 5 years ago by mgifford
  4

• Accessibility for Teams--adding Audio Description

  #40 opened 5 years ago
  3

• No ALT attributes on the homepage.

  #46 opened 5 years ago by c-frizzle
  2

• No Next button on the Information Architecture subset of Content Design

  #47 opened 5 years ago by kirabug
  1

• expand on data visualization guidance

  #45 opened 5 years ago by afeld
  1

• Question about headings asterisk (include only one h1 per page)

  #30 opened 6 years ago by macgyver
  5

• Missing "developer" role

  #31 opened 6 years ago by ginsterbusch
  2

• QA Testing

  #27 opened 6 years ago by michaelspellacy
  5

• Request: Closed captioning for video/multimedia content section?

  #33 opened 6 years ago by jaredcunha
  6

• Contact email inaccurate

  #35 opened 6 years ago by DanTuleta
  5

• Browser Compatibility (IE and other browsers)

  #32 opened 6 years ago by shahilmhd
  1

• What about researchers?

  #26 opened 6 years ago by cmaczo
  10

• Consider best practices vs. requirements

  #8 opened 6 years ago by maya
  0

• Pros and cons feedback from a designer

  #28 opened 6 years ago by maya
  1

• Colour contrast question

  #22 opened 6 years ago by samsadasivan
  4

• Add Traceability category organized under Product

  #4 opened 6 years ago by normanbrobinson
  2

• Launch plan

  #18 opened 6 years ago by maya
  2

• incorrect terminology in "diverse users"

  #24 opened 6 years ago by KSerra
  1

• Write a README and CONTRIBUTING doc

  #20 opened 6 years ago by maya
  1

• Move to GSA repo and update repo name

  #11 opened 6 years ago by maya
  0

• test

  #19 opened 6 years ago by maya
  1

• Various fixes

  #6 opened 7 years ago by maya
  0

• Different touch target size recommendations

  #7 opened 6 years ago by maya
  1

• Add PC screen reader

  #9 opened 7 years ago by maya
  1

• Test/improve navigation IA

  #10 opened 6 years ago by maya
  3

• Make sure expandable persona content works in IE

  #13 opened 7 years ago by maya
  1

• Condense homepage content

  #12 opened 6 years ago by maya
  1

• Add WCAG references to topics

  #5 opened 7 years ago by maya
  1