MDN-Browser-Compatibility-Report-2020

Appendix A: Survey Design The complete survey design follows. Note that the screener questions (1 and 2) are the same as in the 2019 MON DNA survey, in order to get a similar audience. Question 3 is also taken verbatim from the 2019 MON DNA survey.

Goal

Survey Question

Output

(what will we do with the

(what we want (actual questions in survey questionnaire)

to know and

data)

why)

Web developers and designers, we want to hear from you!

We know from past surveys that browser compatibility is a very common pain point, and we would like to get a better understanding of these pain points. This survey will take you approximately 10 minutes, and the results and learnings will be shared publicly.

Common Questions

Screener

1) In regards to web applications or web

[Intended for Screening}

question, filter pages do you: out people • Code

Prevent people who are not the target audience from taking the survey.

Design and code

who do not work on the

• None of the above (concludes their

web.

response, end of survey)

Screener

2) How many hours during a typical week

[Intended for Screening}

question, filter do you spend writing, reviewing, testing, or out people debugging code?

Prevent people who are not the target audience from taking the survey.

• 0 hours of coding (concludes their

who do not

code.

response, end of survey)

Between 1 - 4 hours of coding Between 5 - 10 hours of coding Between 11-20 hours of coding More than 20 hours of coding

3) How would you rate your overall

Leading indicator question.

satisfaction with the Web, as a platform and Use this as a metric to set of tools, to enable you to build what you measure over time to see need or want?

if people are becoming more or less happy with

Strongly Satisfied

the web.

Satisfied

Neither Satisfied nor Dissatisfied

Dissatisfied

Made with FlippingBook - professional solution for displaying marketing and sales documents online