Need general policy for which browsers to support in which contexts

cfarm commented 7 years ago

Make it clear which browsers, functionality to test, and how.

Tasks

draft a policy/recommendation from FEWD perspective

For an upcoming meeting (12/5):

[x] Cat will create a Google Doc
[x] Share out to get questions/suggestions from FEWDs in advance.
[x] During meeting, we'll start live-drafting the policy together!
[x] Go line by line through current list of support and discuss and make decisions on changes.

once FEWDs approve draft

[ ] present it to stakeholders (designers, product owners, Adam)
[ ] adjust with feedback as needed
[ ] get signoff on making this the standard

Acceptance criteria

Make sure you have an experience that’s as feature complete/accessible as possible for each browser in list.
Do we want to specify CSS/HTML features too? Especially what fallbacks are needed or polyfills - with and without js
What level of support are we committing to from now on?
With what methods will we test and achieve that support?(For example, we may decide to manually test some browsers until automated testing is implemented, etc).

cfarm commented 7 years ago

we labeled this HH meaning "double high priority" 😸

contolini commented 7 years ago

How do we talk to stakeholders about the importance of browser support?
If you feel you can’t support our baseline browsers given complex project requirements, what should you do?
If your think your project has a unique user demographic with unusual device usage, how can you safely stray from our standard browser support guidelines?

cfarm commented 7 years ago

More wishlist for outcomes for this task

Understand when we can adopt the newest browser features
Standardize our decision-making process
Feature-based descriptions of support such as specific DOM events or component/UI interactions

cfarm commented 7 years ago

@jimmynotjim and @virginiacc volunteered to draft a proposal to define an active vs passive browser support policy based on Virginia's idea

cfarm commented 6 years ago

@Scotchester volunteered to do the following task for this:

Sketch potential application of active/passive support policy. It should help us answer the question, “How would we apply the policy to pages/browsers?”

cfarm commented 6 years ago

@Scotchester please share an update when you're back!

Scotchester commented 6 years ago

Here's what I developed so far. It's definitely not pretty, but if the general format works for people, we could ask a designer to help pretty it up. Feedback welcome!

screen shot 2018-01-23 at 10 59 29

cfarm commented 6 years ago

@jimmynotjim I think the policy should be added to the Browser Support Guide (or linked, at least) https://github.com/cfpb/development/blob/cb01b571ad3d97124466261cbc31a751eabe7a9d/guides/browser-support.md

cfarm commented 6 years ago

Some quotes from these 2 pieces would be helpful to include in our policy when describing our approach to JavaScript fallback/progressive enhancement implementations:

https://www.gov.uk/service-manual/technology/using-progressive-enhancement https://gds.blog.gov.uk/2013/10/21/how-many-people-are-missing-out-on-javascript-enhancement/

jimmynotjim commented 6 years ago

@cfarm good idea, I'll take a deeper look at them tonight/tomorrow, pull some good parts out, and then list them in the resources section.

jimmynotjim commented 6 years ago

We finished this too, yay!

cfpb / development