[TRACKING] reCAPTCHA and related design changes

[machikoyasuda]

This is the design ticket: #2494

Recommended order of dev tickets:

• reCAPTCHA: Remove icons from media item templates #2538
• reCAPTCHA: Eligibility - Realign form, text, button #2539
• reCAPTCHA: Eligibility Start - Realign page text and button #2542
• reCAPTCHA: Agency Card form - Realign form, text and button #2543
• reCAPTCHA: Enrollment form - Realign text, button #2546
• reCAPTCHA: Enrollment success - Widen text #2544
• reCAPTCHA: Help, Error pages - Button width #2545
• reCAPTCHA: Add reCAPTCHA text and hide button #2541
• reCAPTCHA: Text padding realignment #2540

All these tickets should be completed before a deploy.

The one open question: Whether the Ageny card form page needs the text. I'm leaning towards no, but need 100% confirmation from @indexing

[machikoyasuda]

@thekaveman @angela-tran @lalver1

I ended up making tickets for the realignment of each page, as it requires changing every individual template for every flow (rather than say, being able to easily change all of this in 1 base template file or 1 CSS change), and I wanted to make smaller PRs that are focused and easier to QA. Aside from the last ticket (text realignment 24px/72px), all the tickets can be done synchronously by the whole team - since there aren't depenencies and they're on different files. I imagine most of these PRs will involve deleting CSS and making a small CSS class change (like from col-lg-8 to col-lg-6).

If finishing all of these tickets then reveals to us that greater refactors can be made to template files or CSS (which I do anticipate!), I think that should be a new ticket for the future, and should be discussed when the whole reCAPTCHA removal project is complete. The focus of these tickets is to get the app in a clean deployable state.

[indexing]

@machikoyasuda Response to your question in the description here: #2494.

TL;DR Let's add the informational copy everywhere we use reCaptcha.