-
Notifications
You must be signed in to change notification settings - Fork 166
LG-7620: Update IPP CTA language to include Baltimore option #7058
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
64da62e
7148f0e
f922b0f
c942b49
86f34af
a9d9440
a9cdafc
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -185,7 +185,7 @@ en: | |
| review: Re-enter your %{app_name} password to protect your data | ||
| troubleshooting: | ||
| headings: | ||
| are_you_near: 'Are you near Washington, D.C.?' | ||
| are_you_near: 'Are you located near Washington, D.C. <br/>or Baltimore, MD?' | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Continuing the discussion from the previous thread, another reason for non-breaking spaces vs. explicit newlines can be to avoid situations where variations in screen size or locale can result in scenarios where a line break would need to occur before the explicit line break. Example in French + iPhone SE: This feels like a bit of an edge case so I'm not especially concerned about it in this instance, more that the general practice of trying to control line breaks like this can be more trouble than it's worth.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks, @aduth. I went ahead and merged, but I want to investigate this some more. I'm not sure I'm following entirely, but it actually seems like we want some combination of a line break opportunity element and non-breaking spaces:
Something like this would occur: I think this is a situation where my asking design their input on this would have helped a bit. I'll open a follow-up PR |
||
| missing_required_items: Are you missing one of these items? | ||
| need_assistance: 'Need immediate assistance? Here’s how to get help:' | ||
| still_having_trouble: Still having trouble? | ||
|
|
||


There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we check if the line break element here may have some unintended impact on accessibility, such as a pause when reading? From what I recall, it may. We could consider adding an
aria-hiddenattribute to have it ignored by assistive technology. (This would need to be added as part of theformatHTMLmapping, like in the example in the new documentation introduced with #7034).Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, @aduth looping in @svalexander do you know what the effects might be? According to this answer
<br/>means "read without pause."