microsoft/accessibility-insights-windows

[BUG] Suggestion for requesting support for unsupported actions

DaveTryon opened this issue · 2 comments

DaveTryon commented

Is your feature request related to a problem? Please describe.
When AIWin encounters a UIA Action that it doesn't know how to support, it displays a message that tells the user "if you want this action to be provided in this tool, please click below button", followed by a button that says "I want this Action!!!"

Screenshot showing this for the GetIAccessible action on the LegacyIAccessiblePattern:
image

Clicking on the button does absolutely nothing. There is no user feedback, and the button handler does nothing. It once sent a telemetry data point, but that was removed as we prepared for our 2019 GA release.

Describe the solution you'd like
Instead of a do-nothing button, replace the text with a suggestion to open an issue requesting support for the missing action. Maybe something like: "Accessibility Insights for Windows does not yet support the LegacyIAccessiblePattern.GetIAccessible action. To request support for this action, please upvote an existing issue at https://github.com/microsoft/accessibility-insights-windows/issues. If no issue already exists, you can open a new issue (feature request) to request support for this action."

This is better in several ways:

  1. The user action is actually recorded
  2. The user knows what is happening
  3. The user has visibility into the status of the feature request
  4. The feature request fits into our existing workflow
  5. There is an opportunity to have a conversation with the user to understand the context of the feature request
  6. There is a history of requests, allowing for upvoting or referring to previous requests

Describe alternatives you've considered
It would be simple to create a telemetry data point to send here, but that does very little. If the user has opted out of telemetry, it does exactly nothing. Even if the user has opted in to telemetry, it does nothing to cover points 2-6 listed in the proposed solution.

Additional context
It's less than a day of work to implement this change, but I've marked this as a feature request purely for workflow reasons.

msftbot commented

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!