Automated A11y non-issues and SC Parsing 4.1.1

Hi all,

I have a client which uses multiple IDs in their UI widgets - these IDs 
are 'active' at different times for different reasons depending where 
the user is within a 'flow'. It hasn't demonstrated any a11y problems, 
but is technically a fail of SC 4.1.1.

My client is doing really good work in terms of their a11y approach, and 
I really don't want to fail them on this. But these 'errors' are called 
out by automated tools, and will be visible to anyone else testing the 
site. I just can't say they have resulted in a problem at all.

What would you guys/gals do? Do this also represent a 'false negative' 
that we should address in 2.1 or Silver?

Thoughts?

Josh