this should be more than sufficient for signaling an age-bracket to a service, which may then serve an “age-appropriate experience”.

nothing should be signaled to any service. the service should signal its age limit, and the local software needs to compare the limit with the user age. that too could happen on a per content basis, I guess HTML or CSS could be extended with a new property for that.

then, if the user age is below the limit, the browser should continue loading the page as usual, but hidden from the user, to avoid introducing a new vector for fingerprinting.

A digital identity wallet should be strictly reserved for matters that already required personal identification. Using such heavy-handed measures for controlling access to adult content, or even social media, is complete and utter overkill.

or even to government services portals that did not require personal identification.