core aam roles known entries

[dtsengchromium]

• Add initial Android mappings
• [core-aam]: fill in known Android role mappings

[netlify]

✅ Deploy Preview for wai-aria ready!

Name	Link
🔨 Latest commit	a2941bf
🔍 Latest deploy log	https://app.netlify.com/projects/wai-aria/deploys/692627fbb0ff9f0008c75d9b
😎 Deploy Preview	https://deploy-preview-2682--wai-aria.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[cyns]

Great start!
I noticed that a lot of roles map to android.view.View. Is this sufficient to express their semantics and behavior? Similarly, is GridView sufficient to express the semantics of a data table using the table role?

[dtsengchromium]

Thanks! This can be a topic at the next wg meeting and I can try to attend and help fill the group in on the general effort. tl;dr mappings to android.view.View reflect the current usage in Chrome. As background, classnames represent existing Android widgets. This can be anything from the Android sdk or perhaps beyond. The widget itself defines the more granular details of how the "role" works on Android. For cases where we have no mapping or no closest match, we may default to android.view.View which at least surfaces a base level of support and interpretation by ATs. For the specification process, we can also default to android.view.View or simply leave as TBD if the group prefers.

…

On Thu, Dec 4, 2025 at 11:00 AM Cynthia Shelly ***@***.***> wrote: ***@***.**** commented on this pull request. Great start! I noticed that a lot of roles map to android.view.View. Is this sufficient to express their semantics and behavior? Similarly, is GridView sufficient to express the semantics of a data table using the table role? — Reply to this email directly, view it on GitHub <#2682 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADLR7MFGODWNWORKWRIZ2F34ACAD7AVCNFSM6AAAAACNGFABQOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTKNBRGYYTMMJWGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>