3984 labels descriptions

[mbgower]

Closes #3984 by incorporating the idea of accuracy into 2.4.6 Headings and Labels, and reinforcing the relationship between 2.4.6 and 3.3.2 Labels or Instructions.

Also took the opportunity to use em dashes instead of dashes, where appropriate.

[netlify]

✅ Deploy Preview for wcag2 ready!

Name	Link
🔨 Latest commit	4bb1c38
🔍 Latest deploy log	https://app.netlify.com/sites/wcag2/deploys/67cb36f3efbdd70008c2464d
😎 Deploy Preview	https://deploy-preview-4212--wcag2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[TestPartners]

A semi-colon would be a more appropriate separator than a dash or hyphen.

[StackOverflowIsBetterThanAnyAI]

I see no improvement changing xxx - xxx to xxx-xxx.

[patrickhlauke]

I see no improvement changing xxx - xxx to xxx-xxx.

for context, the change here uses an actual – dash character rather than a - minus sign. and in traditional typography, there's no spaces around dashes (or rather, generally you'd want a hairline space)

[patrickhlauke]

x-ref #4096

[patrickhlauke]

discussed in backlog meeting - opted to reintroduce the spaces around the – dashes (even though it does break the "proper" typographic rules, but improves readability)

[patrickhlauke]

I refreshed my mind on the original issue this tries to address, #3984 - i'd say this SC covers the concern now in a fairly clear way (it still doesn't "reintroduce" the need for accuracy to 3.3.2, but reinforces it - or at least name-checks it - in 2.4.6 now). in short, LGTM

[patrickhlauke]

Would suggest more gracefully embedding the cross-reference to 3.3.2, rather than in an parenthetical

[bruce-usab]

Discussed on backlog call 3/7. Kept in Drafted.