Most organizations can work on multiple accessibility projects at the same time, but the right number depends on three factors: project complexity, team capacity, and how well you track progress. Trying to do too much at once causes every project to lose freshness. Doing too little leaves compliance deadlines at risk.
The answer for most teams falls between two and five concurrent projects. That range accounts for the reality that accessibility work, whether audits, remediation, or VPAT/ACR documentation, requires focused attention from people with specialized knowledge.
What Counts as a Separate Accessibility Project?
A project is any distinct digital asset going through its own accessibility lifecycle. A corporate website being evaluated against WCAG 2.1 AA is one project. A mobile app getting remediated is another. An ACR being produced for a SaaS product is a third.
Each project has its own scope, timeline, and team members involved. Even when the same auditor or developer touches multiple projects, the tracking, reporting, and priorities differ enough that each one needs its own management lane.
| Factor | How It Affects Capacity |
|---|---|
| Project complexity | A 10-page informational website takes far less effort than a web app with hundreds of interactive components. Complex projects consume more capacity. |
| Team size and skill | A team of three experienced developers and a dedicated project manager can carry more concurrent work than a single coordinator wearing multiple hats. |
| Phase of each project | Projects in the audit phase need auditor availability. Projects in remediation need developer hours. Staggering phases lets teams carry more projects. |
| Tracking and visibility | Without a centralized way to monitor progress, even two projects can feel unmanageable. A platform like Accessibility Tracker keeps every project visible. |
Why Two to Five Is the Realistic Range
Organizations with a small internal team or a single accessibility coordinator typically top out at two to three projects running in parallel. That might look like one website audit wrapping up while remediation starts on a second asset and an ACR is being drafted for a third.
Larger teams with dedicated project management capacity can carry four or five. Beyond five, quality tends to suffer unless you have a mature process and the tooling to support it.
Accessible.org works with clients managing anywhere from a single website to a portfolio of digital assets. The pattern is consistent: organizations that stagger project phases and use structured tracking move faster with fewer errors than those running everything at the same pace.
Does Staggering Project Phases Help?
Yes. This is the most effective way to increase capacity without increasing headcount.
An accessibility project moves through distinct phases: inventory, audit, remediation, validation, and documentation. Not every project needs every resource at the same time. If Project A is in remediation and Project B is still being evaluated, your auditor and your developers are working in parallel without competing for the same hours.
Staggering also reduces decision fatigue for project managers. When three projects are all in remediation at once, the volume of issues to prioritize becomes overwhelming. When only one is in active remediation while others are in earlier or later phases, each gets the attention it needs.
What Happens When You Take On Too Many?
Every project starts to lose freshness. Audit reports sit unreviewed. Remediation queues grow. Developers context-switch between codebases so often that fix quality drops.
The cost of overcommitting is real. A WCAG 2.2 AA conformance project that drags on for months costs more than the same project completed in weeks, both in direct labor and in continued compliance risk. ADA compliance deadlines and procurement requirements from enterprise buyers do not wait for teams to catch up.
If your team is stretched thin across six or seven projects and none are progressing, cutting back to three with clear priorities will get you to conformance faster than spreading effort across everything.
How Tracking Tools Change the Math
The single biggest factor in how many projects a team can carry is visibility. When every issue, every status change, and every milestone lives in one place, project managers spend less time chasing updates and more time moving work forward.
The Accessibility Tracker Platform was built for exactly this. It gives teams a centralized view of all active projects, with issue-level tracking, prioritization formulas, and AI-generated progress reports. Organizations using the platform consistently report that they can carry more concurrent projects because the overhead of managing each one drops significantly.
Spreadsheets work for one or two projects. Beyond that, the coordination cost grows faster than the project count.
What About Organizations with Dozens of Digital Assets?
Government agencies, universities, healthcare systems, and large enterprises often have 20, 50, or more digital assets that need to conform to WCAG 2.1 AA or WCAG 2.2 AA. ADA Title II requirements for state and local government web content make this especially pressing.
These organizations do not run all projects at once. They prioritize by risk and public impact, batch assets into phases, and work through them over a planned timeline. A typical approach: evaluate the highest-traffic or highest-risk assets first, begin remediation on those, then move to the next batch as capacity opens.
Taking inventory of every digital asset is the first step. From there, grouping assets by complexity and setting a realistic timeline keeps the work manageable without ignoring lower-priority properties.
Can a solo accessibility coordinator manage multiple projects?
Yes, but two to three is the practical ceiling. A solo coordinator’s time splits between vendor coordination, internal communication, issue tracking, and documentation. Each additional project adds overhead to every one of those tasks. Using a dedicated tracking platform offloads much of the administrative burden and makes three projects viable where two might otherwise be the limit.
Should you finish one project before starting the next?
Not necessarily. Sequential work is predictable, but it is slow. If you have team members whose skills map to different project phases, running projects in parallel with staggered timelines produces better throughput. The key is that each project has a clear owner and a visible status at all times.
How do you know when you have taken on too much?
Three signs: audit reports are not being reviewed within a week of delivery, remediation queues are growing instead of shrinking, and project managers cannot answer where each project stands without digging through email. If any of those are true, capacity is exceeded.
The right number of concurrent accessibility projects is the number your team can move forward every week. For most organizations, that is two to five. The constraint is rarely budget or ambition. It is attention, tracking, and the discipline to stagger work so nothing stalls.
Contact Accessible.org to discuss how to plan and prioritize your accessibility projects.
