Background
We are collecting feedback on https://www.mediawiki.org/wiki/Reading/Web/Accessibility_for_reading/Reporting. Sorting through feedback is currently manual. We should work out a strategy for how to handle feedback going forward so it gets to the right people. If we don't do anything with this feedback it will reflect badly on the team.
User story
As a reader who reports issues I want to make sure my issues get heard.
Requirements
Answer the following questions:
- What ways are there to report the number of clicks received on the report links to communities? (note: the expected format would be
| page name | number of clicks to report link |
| "this is a page" | x |
For example, we can take inspiration from the current contrast reporting
- What ways are there to automatically post feedback received in written form on https://www.mediawiki.org/wiki/Reading/Web/Accessibility_for_reading/Reporting to the specific wiki that feedback is from?
- How are anonymous users using the feedback button. What volume of users are clicking it every day? Is there anything useful we can get from their feedback?
BDD
- For QA engineer to fill out
Test Steps
- For QA engineer to fill out
Design
- Add mockups and design requirements
Acceptance criteria
- Add acceptance criteria
Communication criteria - does this need an announcement or discussion?
- Add communication criteria
Rollback plan
- What is the rollback plan in production for this task if something goes wrong?
This task was created by Version 1.2.0 of the Web team task template using phabulous