Skip to content

Add instructional text to the 2FA setup screen#686

Merged
monfresh merged 1 commit intomasterfrom
two-factor-changes
Nov 8, 2016
Merged

Add instructional text to the 2FA setup screen#686
monfresh merged 1 commit intomasterfrom
two-factor-changes

Conversation

@theresaanna
Copy link

Why:

  • Presumably, users found it confusing before

What:

  • Adds emphasis to first part of info paragraph
  • Adds instructional text to each form field
  • Moves the label string for the phone field out of the view and into a translation string

Visual:
screen shot 2016-11-04 at 1 14 50 pm

Copy link
Contributor

@jessieay jessieay left a comment

Choose a reason for hiding this comment

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

Looks awesome! One comment about using HTML within I18n.

Copy link
Contributor

Choose a reason for hiding this comment

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

I18n protip: we can keep this lead text in the same translation and bold it by taking advantage of I18n's built-in HTML support.

How:

append _html to the translation name (so this would be otp_setup_html), and add the css you need into the translation inline. Like this:

<strong>Every time you log in,</strong> we will send you a one-time passcode via text we will send you a one-time passcode via text message or phone call. This helps safeguard your account.

The Rails view will automatically interpret this string as HTML now. (don't forget to also change the key in the view to be = t('devise.two_factor_authentication.otp_setup_html')

Copy link
Author

Choose a reason for hiding this comment

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

Thanks, that's great to know! Will implement. 👍

Copy link
Contributor

Choose a reason for hiding this comment

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

To me, "any time" implies that there is a setting where they can change their choice, even after authenticating, but we don't have that feature. The only times they can make a choice are:

  • right before they are about to receive an OTP, such as on the phone setup screen or on the delivery method screen
  • when already having received an OTP and deciding they want to change the delivery method ("call me with the code instead", or "text me the code instead")

Copy link
Contributor

@brendansudol brendansudol Nov 7, 2016

Choose a reason for hiding this comment

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

you're right @monfresh but I feel like that subtle difference is fine here

Copy link
Author

Choose a reason for hiding this comment

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

Perhaps we should ask @esgoodman and @jeanninehunter to weigh in here? What do each of you think about this language given the feature set?

Copy link
Contributor

Choose a reason for hiding this comment

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

All good points. However, I can easily see how we might be more precise without destroying plain language simplicity. Let's go with this for otp_method.instruction:

You can change your choice the next time you sign in

cc @jeanninehunter

**Why**:
- Presumably, users found it confusing before

Rework 2FA setup info and instruction text

**Why**:
- Makes instructional language more accurate
- Simplifies translation strings for info paragraph
@theresaanna
Copy link
Author

Changes implemented! Ready for a second review.

@monfresh monfresh merged commit afd08f5 into master Nov 8, 2016
@monfresh monfresh deleted the two-factor-changes branch November 8, 2016 22:43
amoose pushed a commit that referenced this pull request Nov 10, 2016
**Why**:
- Presumably, users found it confusing before

Rework 2FA setup info and instruction text

**Why**:
- Makes instructional language more accurate
- Simplifies translation strings for info paragraph
juliasolorzano pushed a commit that referenced this pull request Jul 23, 2021
* Updating capitalization of login.gov to Login.gov.

* Updating ASCII because fun is important.

* Fixin dat YAML.

* MOAR YML!

* Update config/locales/user_mailer/es.yml

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

* Update config/locales/user_mailer/es.yml

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

* Update config/locales/user_mailer/es.yml

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

* Update config/locales/user_mailer/fr.yml

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

* Update vendor/assets/javascripts/local-time.js

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

* Update vendor/assets/javascripts/local-time.js

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

* Update vendor/assets/javascripts/local-time.js

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

* Update saml_idp with better logic for matching_cert (#5220)

* Bring back a default cert, to fix NoMethodErrors on nil (#5224)

* Add regression spec for NoMethodError

* Remove .erdconfig (#5226)

**Why**: We removed the ERD in #4960

* Update APP_NAME in application.rb.

* Revert Gemfile.lock.

* Update config/locales/idv/fr.yml

Co-authored-by: Zach Margolis <zachmargolis@users.noreply.github.com>

* Update Gemfile

Co-authored-by: Zach Margolis <zachmargolis@users.noreply.github.com>

* Run `make normalize_yaml`

* Update spec that used lowercase login to use uppercase

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>
Co-authored-by: Zach Margolis <zachmargolis@users.noreply.github.com>
Co-authored-by: Jonathan Hooper <jonathan.hooper@gsa.gov>
Co-authored-by: Zach Margolis <zachary.margolis@gsa.gov>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants