When you get an accessibility audit and you don't know how to work with it, the worst thing you can do is start top to bottom and implement whatever you think works. If you don't know how to read it, how to test your fixes, how to document what you've done and why you've done it, the best thing you can do is to get back in touch with the person who did the audit and ask them.
When you hand in an accessibility audit, the worst thing you can do is assume the persons getting it will know how to work with it. If you don't know the level of accessibility knowledge they have, the best thing you can do is to get in touch with them and ask them. Walk through the audit with them. Was the terminology too technical? Were the reproduction steps for issues detailed enough? Did they understand the priority levels?
You should check in periodically if you what to prevent that thing where developers spend a week implementing something, only to find out they completely misunderstood what they had to do.
I like to think of it like a conversation rather than a one-time document dead drop. The audit is just the opening line of that conversation.
An accessibility audit is a roadmap, not the solution.