The "here's how you know" accordion doesn't align with Chrome's choice not to display https

[wslack]

Description

The accordian has text about "https" but there's no visible http:// in the address bar. I wonder if there should be mention of 🔒or something else if this is how other browsers will treat signs that a site has https active.

cc @konklone and @jvehent for their takes as well

[thisisdano]

Good point. I can see adding something to the message around a lock image. But I also defer to @konklone on matters such as these.

[konklone]

Well, to make it more complicated - Chrome has even indicated they expect the lock icon to go away over time, and only mark sites that are insecure. I do generally expect that's how other browsers will go as well, but there will still be variance on this for at least a while.

My experience is that text updates in the USWDS header take a long time to propagate (if they ever do), so you really want to make them as sparingly as possible, and detecting the browser to make browser-specific messages would make it more likely to fall behind as browsers individually evolve. While the message is a little less clear since it's referencing an https:// that no longer shows by default, https:// does show if you click on the URL and it does show in other browsers for now.

I think the message as it stands, since it has a lock icon next to it and https:// is still something people will come across, is probably good to stay for a while. But if you did make a text update, I'd rewrite the opening to something like:

When you see a lock symbol or https:// next to the website name, this ensures...

[wslack]

Hmmm. What about changing it only slightly, then, to

"the https:// in the full URL ensures that you are connecting....

then again, "URL" is a pretty wordy acronym.

[konklone]

Yeah, I thought about using URL (or "location bar") as well, but I think it would be pretty jargon-y for the tone the text is trying to strike for ordinary people. I suspect most folks who know what "URL" means don't need the assistance from this header anyway.

[buckaroogeek]

The fragment resonates with me: "My experience is that text updates in the USWDS header take a long time to propagate". My experience and observation concurs with this. One can still find content on my former agencies web site that was last updated in the 1990s. As a separate issue, I think that solving or addressing this larger problem would be beneficial and valuable. Apologies for the tangent. brad

…

On Tue, Jan 21, 2020 at 11:41 AM Eric Mill ***@***.***> wrote: Yeah, I thought about using URL (or "location bar") as well, but I think it would be pretty jargon-y for the tone the text is trying to strike for ordinary people. I suspect most folks who know what "URL" means don't need the assistance from this header anyway. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3281?email_source=notifications&email_token=AAKDYHUYHPD3LKEMCUNZVMTQ65FV7A5CNFSM4KHJ7WAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJQ7XKQ#issuecomment-576846762>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKDYHS3KPTAYCEIUYYG5BTQ65FV7ANCNFSM4KHJ7WAA> .

[wslack]

Not a tangent @buckaroogeek - this is (for me) about what the north star should be, not making everyone change course.

Maybe just saying "the https:// or lock (🔒) signals...."