CiaoCiao the blog about the digital lifecycle

Accessibility in project planning

Written by Karine Simard | 4-Aug-2025 8:00:00 AM

In this phase, work is done to define the needs and objectives of the project. Digital accessibility must be considered from the planning phase to avoid costly corrections and ensure an inclusive experience for all, including those with disabilities. 

In the planning phase of a project, the following actions take place: 

      • Analysis of user and market needs. 
      • Definition of functionalities and objectives. 
      • Drawing up specifications. 
      • Cost and time estimates. 

5 ways to include accessibility in project planning: 

  1. Define accessibility goals 
      1. Comply with standards and regulations: WCAG, SGQRI, RGAA, ADA, etc. 
      2. Understand the needs of people with visual, auditory, motor or cognitive limitations. 
      3. Foster a proactive inclusion approach: Make the product accessible from the start, not after the fact. 
  1. Involve stakeholders from the beginning 
      1. Product Owners: Integrate accessibility into the product vision 
      2. UX/UI Designers: Design adapted interfaces (contrast, text size, keyboard navigation, etc.). 
      3. Developers: Prevent technical errors by adopting accessible practices. 
      4. Testers and QA: Validate compliance with accessibility criteria. 
      5. End users (including those with disabilities): Participate in testing to identify areas for improvement. 
  1. Prioritizing accessibility with MoSCoW 

Example of how MoSCoW can be applied to accessibility: 

Priority 

Accessibility Support 

Must Have 

Keyboard navigation, screen reader compatibility, sufficient contrast 

Should Have 

Video subtitling, alternative to animations 

Could Have 

Dark mode for visual comfort 

Won't Have 

Advanced features that require significant resources at launch 

 

  1. Integrate accessibility into the roadmap and user stories. for example:  
    1. As a visually impaired user, I want to be able to navigate the site with a screen reader to access the information easily. Acceptance criteria: 
        1. All interactive elements must be accessible by keyboard.  
        2. Essential images must have a description (alt attribute).  
        3. Colors should not be the only way to convey information. 
5.  Provide tools and regular audits 
      1. Wave, Axe DevTools, Lighthouse: Automatic accessibility error checking.  
      2. Contrast Checker: Check colors and contrasts.  
      3. VoiceOver (Mac), NVDA (Windows), JAWS (Windows): Test with a screen reader.
      4. Schedule regular check-ins at each sprint to ensure accessibility is well integrated  

 

What’s the next step?

In our next post, we’ll talk about accessibility in the development phase. If you’re looking to get started on your accessibility training, you can download our training catalogue!

Have a project in mind? We’d love to talk to you about it!
View full post