Skip to content

Section element table should have platform-specific details removed or possibly corrected #361

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

Closed
joanmarie opened this issue Jan 21, 2022 · 1 comment · Fixed by #362
Closed

Comments

@joanmarie
Copy link
Contributor

joanmarie commented Jan 21, 2022

The current mappings for section say:

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"?

@scottaohara
Copy link
Member

makes sense. i agree those shouldn't be necessary if just pointing to core aam

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants