↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

How we stopped making excuses and started improving Basecamp’s accessibility

In 2017, Basecamp made web accessibility a priority after years of delay. The author describes how personal motivation, a new challenge, and a direct experience with assistive technology led to sustained work on Basecamp 3.

Reading notes
#

  • Accessibility became a priority at Basecamp in 2017, after being delayed for years.
  • The author took on improving Basecamp 3 accessibility as a personal mission over the past year.
  • A search for meaningful work and recent experiences with vision loss helped make the project feel urgent.
  • The author’s grandmother’s macular degeneration showed how assistive tools can preserve independence and connection.
  • Basecamp’s QA process is exploratory and usually happens after a feature is built.
  • During a quiet period in early 2017, the author used VoiceOver and keyboard navigation to test Basecamp.
  • Screen reader output revealed confusing page descriptions.
  • The author began filing accessibility issues as bugs in the Basecamp 3: Bugs project.
  • Research into WCAG was needed to understand how elements should look and behave for accessibility.
  • The author made code changes locally and tested them, which made the work feel rewarding.
  • Accessibility feedback was folded into the existing QA process.
  • New features were treated like any other bug when accessibility concerns appeared.
  • Over time, this work helped designers and developers build with accessibility in mind from the start.
  • Earlier attempts to address accessibility had produced discussion and some tweaks, but no sustained process.
  • In the past year, all new features shipped by Basecamp were designed and tested to be accessible.
  • The author began making screen reader walkthroughs to show colleagues existing accessibility issues.
  • Basecamp is still not fully accessible, but the company agrees the work matters.
  • The author says Basecamp’s autonomy and support made this learning and growth possible.
  • Future posts will cover specific accessibility fixes and techniques.