Project Planning

A successful approach to accessibility starts with embedding it into the project plan by defining requirements early, allocating time for accessibility and including people with disabilities in your user testing and feedback. 

On this Page

Planning for Accessibility 

By integrating accessibility into the planning stages of websites and apps, teams can ensure that inclusive and user-friendly requirements are embedded into every phase of the project lifecycle from the beginning.

Related Content: 

Key Takeaways:

  • Cost Efficiency: Addressing accessibility early reduces expensive rework later.
  • Improved User Experience: Inclusive designs benefit everyone, not just users with disabilities.
  • Compliance and Risk Mitigation: Help to meet Yale University’s legal and regulatory requirements.  
  • Innovation: Accessibility challenges often inspire creative, universally beneficial solutions.

Incorporating Accessibility into Project Planning

A successful approach to accessibility starts with embedding it into the project plan. Here’s how to integrate accessibility in a structured and sustainable way:

Define Accessibility Goals Early

  • Establish clear accessibility objectives at the outset of the project. For example:
    • Compliance with WCAG 2.2 AA.
    • Plan for testing and fixing accessibility barriers. 
  • Assign a dedicated accessibility advocate or champion to keep the team focused on these goals.

Allocate Time in Each Sprint for Accessibility

  • Planning Phase: Include accessibility criteria in user stories, acceptance criteria, and definition of done.
  • Development Phase: Build accessibility into code from the beginning by using semantic HTML, ARIA roles, and proper keyboard navigation.
  • Testing Phase: Dedicate time in every sprint to:
    • Run automated accessibility tests using aXe.
    • Conduct manual tests, such as keyboard navigation and screen reader compatibility.
  • Treat accessibility issues as high-priority defects to be resolved within the sprint.

Conduct User Testing with People with Disabilities

  • Recruit diverse participants with disabilities to provide real-world feedback during usability testing.
  • Perform user testing at multiple stages, such as:
    • Prototype review.
    • Pre-launch usability testing.
    • Post-launch testing for continuous improvement.

Invest in Team Training and Resources

  • Provide ongoing accessibility training for all team members, including developers, designers, QA testers, and product managers.
    • Topics might include WCAG guidelines, inclusive design principles, and testing tools.
  • Share resources like checklists, style guides, and templates to make accessibility easier to implement.

Use Accessible Tools and Frameworks

  • Choose design and development tools that support accessibility by default, such as:
    • Design tools with color contrast checkers.
    • Code libraries with prebuilt, accessible components.
  • Automate where possible to reduce the burden on the team (e.g., accessibility linters, browser plugins).

Monitor and Adapt

  • Measure progress against accessibility goals throughout the project using KPIs, such as:
    • Percentage of pages passing automated tests.
    • User feedback from accessibility testing.
  • Conduct regular audits to identify and address any emerging issues.

Conclusion:

Shifting accessibility left is not just about compliance; it’s about creating digital products that work for everyone. By embedding accessibility into the DNA of your project plan, you’ll deliver higher-quality, more inclusive solutions while building a culture of accessibility that will benefit your organization for years to come.