You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
region role if the section element has an accessible name. Otherwise, the generic role.
And the Core-AAM has mappings for both scenarios. So I think the platform-specific stuff can be removed. (Aside: The interfaces listed for IA2 and ATK don't really need to be stated here or in any table in the Core-AAM. The web would literally be completely broken if elements with text or child elements failed to implement those interfaces).
If the platform-specific entries are to remain for now in the HTML-AAM, the UIA entry seems to conflict with what is in the Core-AAM. Is the Localized Control Type really "section"?
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
The current mappings for
section
say:And the Core-AAM has mappings for both scenarios. So I think the platform-specific stuff can be removed. (Aside: The interfaces listed for IA2 and ATK don't really need to be stated here or in any table in the Core-AAM. The web would literally be completely broken if elements with text or child elements failed to implement those interfaces).
If the platform-specific entries are to remain for now in the HTML-AAM, the UIA entry seems to conflict with what is in the Core-AAM. Is the Localized Control Type really "section"?
The text was updated successfully, but these errors were encountered: