Well as a software developer this seldom affects me, but surely compliance is just an extra set of constraints. There are some constraints that affect any device, but cost and compliance requirements vary with time, if only slowly, so it is trickier to include them in a course.
However I think the approach I would make if I were teaching would be something like.
"It works, but that is only the start, now you have to meet constraints like cost and availability of components, safety, legal standards etc"
And in the second year when they can presumably build a circuit give them the same things to build they built in year one with a bunch of made up but plausible constraints, perhaps modelled on old compliance requirements.
This would hopefully get students to realise that they are basically getting paid to handle the constraints.