These seems to be a small bug in the described by reference and target. I had this error prior to GF 2.5 and it is still there on a new form built in the new version.
It may be a mistake in the way the Wave accessibility checker reports it but looking at the source I think it is probably a bug.