Data consent follow-ups: redirect on decline, fixed checkbox label color

[gumaerc]

What are the relevant tickets?

Follow-up to #4006 for https://github.com/mitodl/hq/issues/13575

Description (What does it do?)

Changes to the B2B data consent dialog before the b2b-data-consent flag is turned on in production.

• Declining now sends the learner to dashboard home. The contract's cards stay disabled until consent is true, so hiding the dialog in the browser console still doesn't make them usable.
• The consent checkbox label stays dark gray all the time. It no longer changes color on hover. The box keeps its hover state.

How can this be tested?

1. Enable b2b-data-consent in PostHog, with an up-to-date mitxonline (the consent field landed in Return the user's data sharing consent on their B2B contracts mitxonline#4039).
2. As a learner attached to a B2B contract with no recorded consent, open the contract dashboard.
3. Hover over the checkbox. The box shows its hover state, and the label text keeps the same dark color.
4. Click Decline. You land on /dashboard. Open the contract again, and the dialog is back.

[github-actions]

OpenAPI Changes

No changes detected

View full changelog

Unexpected changes? Ensure your branch is up-to-date with main (consider rebasing).

[Copilot]

Copilot review overview

🟢 Approval recommended

The focused changes match the stated behavior and include appropriate regression coverage.

Review effort: Balanced
Findings: None

What changed in this PR

Updates B2B consent behavior and styling before production rollout.

Changes:

• Redirects declined learners to dashboard home while locking dialog actions.
• Keeps the consent checkbox label dark on hover.
• Updates redirect and disabled-state tests.

File	Description
DataConsentDialog.tsx	Fixes checkbox label color.
ContractContent.tsx	Redirects after successful decline.
ContractContent.test.tsx	Tests redirect and locked actions.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[gumaerc]

@steven-hatch Ferdi brought up an interesting point while I was testing this. He posited the question "why are we showing the popup once you've reached the contract page, rather than before?" He thought it made more sense if you're on dashboard home for example and you click one of the sidebar buttons or the org card button to show the popup right there before you even navigate to the page. What do you think?

[steven-hatch]

I think that’s a reasonable alternative, and I’m good with either approach.

• Existing users: showing the consent modal on Dashboard Home when they click the org/contract entry point could be cleaner because it resolves consent before navigation.
• SSO / enrollment code users: they may land directly on the contract page, so the consent modal would still need to work there.
• UX-wise: I’d treat this as the same consent step in two entry contexts, not two different experiences.
• Main thing to preserve: consent should still be tied to the specific contract, and declining should not block the rest of MIT Learn.

So I’d be comfortable with: show it before navigation when we can, and fall back to showing it on the contract page when that’s where the learner enters.

@gumaerc we should still default to dashboard home on decline for both instances. Thank you.