All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.
- What questions will you answer with this data?
This data will help understanding the extent of the use of the accessibility tool in Firefox Developer Tools. This is a brand new panel that recently landed on Nightly and has no panel specific telemetry associated with it. It is landed as an optional tool (can be enabeld in DevTools settings), we currently do not measure which tools are enabled/disabled in the settings.
- Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements? Some example responses:
-
Understand how engaged our developer audience is with accessibility tools in context of using developer tools overall.
-
Determine how discoverable accessibility tools are within DevTools and Firefox itself.
-
Determine what functionality is used the most or least to consequently improve developer audience's user expereince.
- What alternative methods did you consider to answer these questions? Why were they not sufficient?
This is a brand new functionality (accessibility panel) that is now part of the Developer Tools and we have no telemetry associated with it at the moment. The only information that is collected is relateted to the general use of DevTools (e.g. opened/closed/active time).
- Can current instrumentation answer these questions?
Yes
- List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the Mozilla wiki.
Note that the data steward reviewing your request will characterize your data collection based on the highest (and most sensitive) category.
| Which tools are checked/unchecked (in other words registered/unregistered) by the user within the Developer tools options. | Category 2 | [Bug 1447302](https://bugzilla.mozilla.org/show_bug.cgi?id=1447302) |
| Number of times the accessibility panel was opened. | Category 2 | [Bug 1447302](https://bugzilla.mozilla.org/show_bug.cgi?id=1447302) |
| Active use time of the accessibility panel. | Category 2 | [Bug 1447302](https://bugzilla.mozilla.org/show_bug.cgi?id=1447302) |
| Number of times the accessibility service was enabled within the accessibility tool. | Category 2 | [Bug 1447302](https://bugzilla.mozilla.org/show_bug.cgi?id=1447302) |
| Active duration time the accessibility service was enabled within the accessibility tool. | Category 2 | [Bug 1447302](https://bugzilla.mozilla.org/show_bug.cgi?id=1447302) |
| Number of times the picker tool was used within the accessibility tool. | Category 2 | [Bug 1447302](https://bugzilla.mozilla.org/show_bug.cgi?id=1447302) |
| Active duration time the picker tool was used within the accessibility tool. | Category 2 | [Bug 1447302](https://bugzilla.mozilla.org/show_bug.cgi?id=1447302) |
| How often the accessibility object is inspected in the accessibility panel (and from where, e.g. context menu, DOM inspector panel). | Category 2 | [Bug 1447302](https://bugzilla.mozilla.org/show_bug.cgi?id=1447302) |
| How often the DOM node is inspected from the accessibility panel (via navigation from an accessible object to a corresponding DOM node). | Category 2 | [Bug 1447302](https://bugzilla.mozilla.org/show_bug.cgi?id=1447302) |
- How long will this data be collected? Choose one of the following:
- I want to permanently monitor this data. Yura Zenevich
- What populations will you measure?
- Which release channels?
All channels
- Which countries?
All countries
- Which locales?
All locales
- If this data collection is default on, what is the opt-out mechanism for users?
Same as the rest of browser telemetry gathered.
- Please provide a general description of how you will analyze this data.
We are planning on running a shield study for the Dev Edition channel where the pannel would be enabled by default for a test population of users. These measurements will help answer questions about discoverability, use and overall satisfaction with the tool.
Dashboard with data visualized.
- Where do you intend to share the results of your analysis?
This is for internal use mostly. Dashboard will be accessible to all employees. The shield study will help determine if this tool is a good candidate to be a default tab in the Developer Tools on release.