search

microsoft / axe-windows

Automated accessibility testing engine for Windows applications
MIT License
136 stars 62 forks source link

[BUG] Should NameIsInformative rule filter out more frameworks? #874

Closed DaveTryon closed 1 year ago

DaveTryon commented 1 year ago

Describe the bug

The NameIsInformative rule exists for some very old framework bugs and is mostly noise for current frameworks. At the moment, the rule applies to all non-Win32 frameworks. Should we modify the Condition to apply it only to the frameworks that are known to have this problem in their old versions?

microsoft-github-policy-service[bot] commented 1 year ago

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!

DaveTryon commented 1 year ago

We're trying to decide what changes, if any, are appropriate here.

microsoft-github-policy-service[bot] commented 1 year ago

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

microsoft-github-policy-service[bot] commented 1 year ago

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

DaveTryon commented 1 year ago

We left the frameworks unchanged, but excluded Text and Group controls. We also updated the HowToFix text to make it clearer what the criterion is. Marking as resolved, will close it out once we release a new version of Axe.Windows

DaveTryon commented 1 year ago

We should close this only once we release an updated version of Axe.Windows