Accept or Decline Cookies

[thansidwell]

People need a way to

• Save properties to a list (in development)
• Preserve the filters (not yet built)
  • So when you click on a Get Access option and go back you don't have to enter your filters manually again.
• Preserve their location and zoom level on the map
  • So when you go to another page and come back to the map you return to where you were

We decided that the best way to do that is with cookies. However we also need to

• Let users know we are saving cookies into their browser
• Give them an option to decline
• If they decline, show them they need to accept it to use certain features

Here's the experience broken down.

Banner

• When users go to the website a banner appears at the bottom of the viewport fixed to the bottom.
  • Add a blue background, heading, description, decline button and accept button matching the prototype.
  • The banner should appear on every page you visit.
• When you click "Accept"
  • The banner will disappear
  • We can then store cookies to their browser.
• Clicking "Decline"
  • The banner will disappear
  • We do not store cookies to their browser. Perhaps we should delete any cookies that we have saved to their browser at that moment.

Footer

• On a footer there's a new "Cookie Settings" link
• Rework the footer so all the elements are center aligned and seperated by " — "
  • When they are spread out they draw more attention to themselves than needed
• Clicking this will make the banner appear again so users can change their choice

Save Button

• On a property, when a user clicks "Save"
• If they have accepted cookies the property is saved as expected
• If they have declined cookies the banner appears again
• If they decline again the property does not save
• If they accept then the property is saved as expected

https://github.com/CodeForPhilly/vacant-lots-proj/assets/1965986/bbb5c7c4-8fd2-48ca-925a-30ae64115a65

View the Prototype

[CodeWritingCow]

@thansidwell can you assign this ticket to me? Thanks!

By the way, the video shows the "Decline" button preceding the "Accept" button. In general, I think it's more common for "Accept" to precede "Decline" in website UIs. Also, would it be better if "Accept" appears first, so users might be encouraged to click "Accept"?

[thansidwell]

@CodeWritingCow, Done!

I hear you on the order. It's actually a debatable topic in UX. For instance, Windows puts the primary action first while Apple puts it last. Here's an article about it. I'm persuaded that the primary action last is the better approach.

[CodeWritingCow]

@CodeWritingCow, Done!

I hear you on the order. It's actually a debatable topic in UX. For instance, Windows puts the primary action first while Apple puts it last. Here's an article about it. I'm persuaded that the primary action last is the better approach.

@thansidwell Thanks for sharing the article. It was a great read, and I learned a lot from it. (As a Mac user, I'm ashamed to admit that I didn't notice Apple's "primary action last" principle until you pointed it out.) So on this UX topic, I'll defer to you and follow your design!

[Moylena]

Pending final review and approval