I am working with a lot of teams and there are different phases of testing. We have devised a standardized process for accessibility testing across many different teams. This process is to be done for all new software applications, upgrades or enhancements. The problem is deciding how to estimate accessibility testing and incorporating it into a standard accessibility testing process for team leaders.
The problem is deciding how to estimate accessibility testing and incorporate it into this standard accessibility testing process for team leaders.
Accessibility testing is just testing. From a project management point of view, it's just another task, milestone, or gating activity that must be performed to complete a unit of work.
You estimate accessibility testing the same way you estimate the rest of your work packages: you use historical norms, or you ask subject-matter experts and/or assigned task-performers to provide an educated guess about how long they expect each task to take.
If this type of testing is new to your project, then your estimates are likely to be less accurate than you might like. If that's the case, you simply apply a fudge factor that represents your project's level of uncertainty about the tasks, and then re-estimate or adjust your schedule as the team's experience grows and your estimation practices improve.