-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate documentation from docs.microsoft.com to accessibilityinsights.io #143
Comments
Thank you for filing this issue. We will triage it by EOD next business day and update the issue. Thank you for contributing to Accessibility Insights! |
@risanaka Pleas turn it into a feature than a bug since the size of work is not fit for a bug. also, it is on the PM side since Docs are owned by PM AFAIK. |
Milestone created for this feature. |
This feature needs investigation, specifically around ownership of this documentation--while it's exclusively used by Accessibility Insights, philosophically, the content could be owned by the UI framework owners (since it describes best practices around accessibility). Someone on the team needs to drive this conversation and clarify ownership. |
Per our discussion, you and @adrianaandreeva need to figure out what to do on this. For context, the links to docs.microsoft.com are in the links.json file that we install in the same folder as AIWin |
This issue has been marked as being beyond the support scope of Accessibility Insights. It will now be closed automatically for house-keeping purposes. |
Is your feature request related to a problem? Please describe.
Today, doc.microsoft.com hosts the How to Fix guidance, but the content is specifically customized for the purposes of Accessibility Insights users; updates and feedback will most likely come from Accessibility Insights users.
Describe the solution you'd like
Accessibility Insights should own the "View Code Sample" content in a documentation repository.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: