2026 Equalify 6-Month Roadmap

[azdak]

Goals

• Develop a free, top-in-class automated accessibility scanning and reporting platform that's easy to use, simple for businesses and organizations to adopt, and less expensive to maintain than existing commercial solutions
• Bring these tools to the widest possible audience by attracting users, developers, and contributors in a vibrant open-source ecosystem

Quarterly Project Reporting

• Metrics:
  • Stakeholder survey results
  • Bugs fixed
  • Features added
  • git stars
  • Forks
  • Contributors
  • Feature comparison to existing commercial solutions
  • Cost comparison to existing commercial solutions
• Review and Revise Roadmap

Meeting Schedules

Meeting	Cadence
Equalify Engineering Standups	2/week - Tues/Thurs @ 12CST
Roadmap/Stakeholder Meeting	1/mo - Third Wednesday @ 3CST
Engineering + Service Team	1/mo - First Thursday @ 11CST
Open-Source Call	1/mo - 3rd Weds @ 11CST (pending)
Monthly Metrics Report	1/mo
Quarterly Metrics Report	1/mo
Feature/Project calls	as needed

Roadmap

Now (validated, in-production tasks)

• Meet or exceed feature set of existing commercial platforms

  • Complete Equalify V2 Roadmap Validate Product, Catch Issues
    • Design & Maintenance Sprint
    • Onboarding Features Sprint
  • Bug fixes (as-needed)
  • Feedback & New Features
    • Collect and review submitted feature requests in git
    • User/stakeholder consultation for big-picture feedback
      • Regular, scheduled call with Services Team (and/or written product survey)
  • Implement in-app feedback (?)

• Encourage Open-Source Adoption

  • FOSS (open-source) Sprint

• Hard Launch (with announcement) on completion of roadmap sprints

Next (tasks pending further discovery)

• Meet or exceed feature set of existing commercial platforms

  • Identify and compare existing feature set
    • Identify "essential" features
  • Replicate (or improve on) all identified essential features
  • Create cost comparison vs existing platforms
    • Optimize scan and server usage to minimize user costs

• Encourage Open-Source Adoption

  • Documentation for everything
    • Simple installation guide
    • User documentation
    • Contributor documentation
    • Create and maintain project FAQ
  • Marketing
    • Establish messaging priorities/USPs
    • Website & marketing assets (update and improve)
    • Leverage UIC connection
    • Recruit established a11y community members to test and offer feedback
    • Invite a11y online communities to test
    • Email list and regular project emails

Later (long-term priorities)

• Meet or exceed feature set of existing commercial platforms

  • Manual Testing (Project Raga)

• Encourage Open-Source Adoption

  • Training Materials
  • Formalize leadership/governance structure (eg https://medium.com/the-node-js-collection/healthy-open-source-967fa8be7951)
  • Ports to additional platforms (Google Cloud Platform, Azure, etc)

[bbertucc]

The "now" work needs due dates.

Also the Open Source items need to be added:

• Deployment in 30 minutes or less
• Handles 100 pages/minute without breaking a sweat
• Costs less than $1000/month for typical usage
• No critical bugs
• Documentation that doesn't suck

Could we do that by CSUN (March 9)? I preset equalify then.

[bbertucc]

A few more comments:

• shouldn't "Feature/Project calls" be "Feature/Project Development Calls"?
• "Roadmap/Stakeholder Meeting" needs to be "Roadmap + Feature Review Meeting". We won't have additional stakeholders until after this 6 mo. sprint and we need some time to review feature requests before you build, so you're not building stuff we're not aligned on.
• I scheduled "Roadmap + Feature Review Meeting" to the third monday of every month.

[bbertucc]

Aiming to finalize this by our next third monday meeting.

[bbertucc]

We approved this on today's call.