LocalizedControlTypeReasonable fails with German locale
ollypsilon opened this issue · 10 comments
The following accessibility issue needs investigation.
App: MSACCESS
Element path: Bild 'Mit Access verknüpfte Tabelle'
Issue Details: The LocalizedControlType should be reasonable based on the element's ControlTypeId. Section 508 502.3.1
How To Fix: Set a meaningful LocalizedControlType UI Automation property for this element.
This accessibility issue was found using Accessibility Insights for Windows, a tool that helps debug and find accessibility issues earlier. Get more information and download this tool at https://aka.ms/AccessibilityInsights.
Beside automatic issue text above here's the element's details:
“Bild” is image in German, so this appears to be a false positive .
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!
Some more info here: Neither Axe.Windows nor AIWin currently support running with non-English localized resources, so in this case the rule is comparing the German-localized name to the English-localized name and not finding a match.
We could potentially alter the rule to exclude scenarios where the locale language doesn't match the process language, but we'd need to work out the details of how this works, how to document it, etc.
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!
We've identified 2 options here: Either:
- Disable this rule if the language is not English OR
- Provide a localized dictionary of appropriate names and check the localized name. If we don't have a localized version available, then skip the rule
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!
Plan is to disable this rule if running on a non-English language setting
This has been addressed in Axe.Windows 2.1.2, which was picked up in #1620. It will be in the next Canary release
@ollypsilon, this is fixed in our Canary release available at at https://github.com/microsoft/accessibility-insights-windows/releases/tag/v1.1.2334.01. It will soon ship to Production.
Per our policy, closing the issue as it's available in Canary.