Google isn't in control of the hardware Chrome is running on. Many of those devices do support Av1 decode at a hardware level so it is efficient. Apple has complete control over all their hardware, and they don't support av1 decode. They're absolutely holding progress back.
Anyhow, I will also point out that there is plenty of non Apple hardware in use that also doesn’t have dedicated AV1 decoders. I realize that’s changing, but it’s still got to be a low % of devices at the moment with dedicated AV1 support. I think a more user friendly posture from Google would be to only report AV1 capability in WebRTC negotiation or video tag source selection where it can be done energy efficiently. Happy to be shown to be wrong on that, but my understanding is they don’t do that today.