Skip to content

LG-6349 Consistently use 'Update' language on verify and update pages#6546

Merged
sheldon-b merged 13 commits intomainfrom
sbachstein/lg-6349-content-changes-to-doc-auth-flow
Jul 6, 2022
Merged

LG-6349 Consistently use 'Update' language on verify and update pages#6546
sheldon-b merged 13 commits intomainfrom
sbachstein/lg-6349-content-changes-to-doc-auth-flow

Conversation

@sheldon-b
Copy link
Contributor

@sheldon-b sheldon-b commented Jul 2, 2022

  • Updates the verify page's labels to use sentence case ("First name") instead of title case ("First Name")
  • Changes "Social Security Number" to "Social Security number" per designs
  • Changes "Zip Code" to "ZIP Code"
  • Updates the pages where users update their address, state ID information, and Social Security number to have an "Update" button instead of "Continue" button
  • Changes the HTML semantics of the verify page key/value pairs to be HTML description lists instead of just divs with text
  • Moves a bunch of content strings that were previously only used in the doc auth flow but are now also used in the in-person proofing flow. I moved them from doc auth namespaces/files into idv namespaces/files

📋 Not included

  • Back/cancel/start over buttons of any sort

📺 Demo

You can try these changes in the sbachstein sandbox.

Verify page (doc auth)

localhost_3000_verify_doc_auth_verify (5)

Change address page (doc auth)

localhost_3000_verify_address (1)

Verify page (in-person proofing)

localhost_3000_verify_in_person_verify (3)

Change address page (in-person proofing)

localhost_3000_verify_in_person_address (6)

Change state ID page

localhost_3000_verify_in_person_state_id

Change SSN page

Note: this is the doc auth page which is the same for in-person except in-person's step indicator is different.

localhost_3000_verify_doc_auth_ssn (2)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Description lists have a default bottom margin of 2 so I wanted to override it to match the div that was here previously

Comment on lines 89 to 93
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This translation got messed up in this PR -- this restores it to what it should be

@sheldon-b sheldon-b force-pushed the sbachstein/lg-6349-content-changes-to-doc-auth-flow branch from e419a71 to 86aa542 Compare July 2, 2022 07:11
@sheldon-b sheldon-b force-pushed the sbachstein/lg-6349-content-changes-to-doc-auth-flow branch from c166628 to 5a5ec17 Compare July 3, 2022 00:09
<div class="margin-bottom-4">
<%= f.input :city, label: t('idv.form.city'), required: true, maxlength: 255, wrapper: false,
input_html: { aria: { invalid: false }, class: 'usa-input', value: @pii['city'] } %>
input_html: { aria: { invalid: false }, value: @pii['city'] } %>
Copy link
Contributor Author

@sheldon-b sheldon-b Jul 4, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This styling was making the city input text smaller than the other inputs:
Screen Shot 2022-07-04 at 3 50 55 PM

pattern: '(\d{5}([\-]\d{4})?)',
wrapper: false,
input_html: { aria: { invalid: false }, class: 'usa-input', value: @pii['zipcode'] } %>
input_html: { aria: { invalid: false }, value: @pii['zipcode'] } %>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This styling was making the ZIP code input text smaller than the other inputs:
Screen Shot 2022-07-04 at 3 51 02 PM

Comment on lines +14 to +15
<%= "#{t('doc_auth.forms.first_name')}: #{pii[:first_name]}" %>
<dt class="display-inline"> <%= t('idv.form.first_name') %>: </dt>
<dd class="display-inline margin-left-05"> <%= pii[:first_name] %> </dd>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took this opportunity to implement Andrew's suggestion to improve the HTML semantics of this page by using description lists

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may not need both the margin-left-05 and the explicit " " space, since my intention with the margin-left-05 in the other component was as a substitute for the space character.

Copy link
Contributor Author

@sheldon-b sheldon-b Jul 5, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh good call, for some reason I thought I needed the left margin but the space alone is better. Set the margins to 0 in 9abec01 (there is a default margin that is way too big)

@sheldon-b sheldon-b changed the title (WIP) LG-6349 Consistently use 'Update' language on verify and update pages LG-6349 Consistently use 'Update' language on verify and update pages Jul 4, 2022
@sheldon-b sheldon-b marked this pull request as ready for review July 4, 2022 23:03
@sheldon-b sheldon-b requested review from a team, NavaTim, WheresHJ, rutvigupta-design, tomas-nava and zachmargolis and removed request for a team and rutvigupta-design July 4, 2022 23:03
@aduth
Copy link
Contributor

aduth commented Jul 5, 2022

  • Updates the pages where users update their address, state ID information, and Social Security number to have an "Update" button instead of "Continue" button

I expect these changes would need to be reflected in the partner-facing Figma designs for identity verification. Has this been / can we communicate to the UX folks?

Copy link
Contributor

@aduth aduth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to defer to another with more context here, but changes LGTM! Some great refactoring here too.

Comment on lines +14 to +15
<%= "#{t('doc_auth.forms.first_name')}: #{pii[:first_name]}" %>
<dt class="display-inline"> <%= t('idv.form.first_name') %>: </dt>
<dd class="display-inline margin-left-05"> <%= pii[:first_name] %> </dd>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may not need both the margin-left-05 and the explicit " " space, since my intention with the margin-left-05 in the other component was as a substitute for the space character.

<div class='margin-top-4 margin-bottom-2'>
<div class="grid-row grid-gap grid-gap-2 padding-bottom-1">
<div class='grid-col-fill'>
<dl class="grid-col-fill margin-bottom-0">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At some point we may want to consider creating a convenience CSS class for these sorts of term:value lists, so that we can avoid the margin utility here and the display-inline below.

Copy link
Contributor Author

@sheldon-b sheldon-b Jul 5, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. Could you link me to an existing CSS class so I can see how that's currently done in the codebase? Not planning to do it as part of this ticket but I'd like to know how for next time

Copy link
Contributor

@aduth aduth Jul 6, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. Could you link me to an existing CSS class so I can see how that's currently done in the codebase? Not planning to do it as part of this ticket but I'd like to know how for next time

That's a good question. The stylesheets are a bit scattered as far as patterns go.

I could imagine a few options:

  • Treat it like a "component" for description list, optionally of an "unstyled" variety
    • e.g. .description-list or .term-list or .description-list.description-list--unstyled in a new file _description-list.scss or _term-list.scss
    • Ideally these component stylesheets would map to a Rails component or React component, which we could do, but I don't think is strictly necessary unless you think there's some value in it.
  • Add a utility class, maybe even to one of the existing (typography?)
    • I'm not a huge fan of the utility classes since they're a hodgepodge of miscellaneous things, but this feels like it fits as a miscellaneous thing

buttons:
cancel: Cancel and return to your profile
change_address_label: Change address
change_label: Update
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were we intending to change the text here from "Change" to "Update" ?

The links on the right:

image

Edit: I see this update is proposed in the Figma attached to LG-6285. Two follow-up points:

  • Do we also need to revise the accessible aria-labels to match? Since my understanding is that those are supposed to be essentially the same, but more contextualized for assistive technology (link purpose)
  • Similar to other comment, I expect these would need to be updated in the partner-facing Figma designs

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aduth yeah I've talked with Annie about making these changes to the doc auth flow in addition to the IPP flow. I'll let her know that we should update the partner-facing Figma designs

Good point about the aria labels, I agree that those should change

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll also aim to get the Spanish and French translations for all of these label changes (the visible and aria labels) included as we do IPP content translations

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the English aria labels in 87f7c0c. I've updated LG-6337 to track getting translations for the Spanish and French translations of this change (eg Change => Update in Spanish and French for the various labels and buttons)

Copy link
Contributor

@zachmargolis zachmargolis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@tomas-nava tomas-nava left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approve!

Copy link

@WheresHJ WheresHJ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@NavaTim NavaTim self-requested a review July 6, 2022 00:27
@sheldon-b sheldon-b merged commit a39d30f into main Jul 6, 2022
@sheldon-b sheldon-b deleted the sbachstein/lg-6349-content-changes-to-doc-auth-flow branch July 6, 2022 01:01
@jmdembe jmdembe mentioned this pull request Jul 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants