[docs] Tooltip guidelines

[atomiks]

Before the API reference, it's a good idea to list guidelines to ensure users are using the right component. This is currently a plain section/paragraph, but we can add callouts or styling/colors.

Part of #559

Preview

[netlify]

✅ Deploy Preview for base-ui ready!

Name	Link
🔨 Latest commit	1f8c54e
🔍 Latest deploy log	https://app.netlify.com/sites/base-ui/deploys/67a0a439792ef7000871904f
😎 Deploy Preview	https://deploy-preview-1356--base-ui.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.

[colmtuite]

@atomiks Perhaps "Accessibility" or "Accessibility Guidelines" is a better heading? Also, this should come after the API Reference. The first thing you see for any component should be the demo and the anatomy.

[atomiks]

Hmm yeah, "Accessibility guidelines" is likely better. Other guidelines like "Design guidelines" can be separate from accessibility guidelines, if we decide to add them at some point.

Also, this should come after the API Reference.

I somewhat disagree here (even though I think it looks cleaner). The user may not reach the end of the API reference before deciding to start using the component since they didn't see the guidelines - it's important that they understand they're using the right component up front/as soon as possible before diving in.