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
{{ message }}
Repository navigation
Feedback on aria-relevant for Android Core AAM #268
The ARIA Working Group just discussed Feedback on aria-relevant for Android Core AAM.
The full IRC log of that discussion
<Zakim> agendum 5 -- [Feedback on aria-relevant for Android Core AAM](https://github.com//issues/268) -- taken up [from jamesn]
<front-endian-jane> spectranaut_: We may have to punt both of these because David isn't here, but he asked for a video link, let's talk about this item later in the meeting
<front-endian-jane> zakim, take up item 7
The ARIA Working Group just discussed Feedback on aria-relevant for Android Core AAM, and agreed to the following:
RESOLUTION: android can specify aria-relevant as not mapped
The full IRC log of that discussion
<Zakim> agendum 5 -- [Feedback on aria-relevant for Android Core AAM](https://github.com//issues/268) -- taken up [from jamesn]
<front-endian-jane> David: It was a year ago when we first talked about Android doing core AAM mappings. It got blocked but is starting up again. We have been discussing every mapping with the Android team so this is the first of potentially many mappings we want to discuss and ask questions about aria-relevant.
<jcraig> q+
<front-endian-jane> David: From the Chrome side of things we've done a lot to try to get it to work, supporting the whole vocabulary of what aria-relevant supports. The request for feedback is first, are there any concerns with us not mapping this to an OS API? We can discuss concerns with the Android team if a subset would be useful. Removals is not useful for us as far as we can tell.
<jamesn> Ack jc
<front-endian-jane> jcraig: There is no problem with Android listing it as not mapped. Voiceover does speak deletion differently as a down pitch. I see it most frequently with rich text fields. We had two live regions in on app, one for additions, one for removals. Some apps did that for a while. In the context of aria-notify I think it's total reasonable to not map it if Android doesn't currently support that.
<front-endian-jane> jcraig: Any implementation can choose to implement any portion of any spec. It isn't our job to tell an implementor what to implement, we can just advise. That is just my opinion, but others should give their opinions too.
<front-endian-jane> Lucas: Is this just about relevant, or other attributes too?
<front-endian-jane> jamesn: It is just about relevant, we have another agenda item for other attributes.
<spectranaut_> +1 to jcraig's advice
<front-endian-jane> jcraig: Other aria attributes aren't mapped, that doesn't mean it doesn't work. It can also mean there isn't a relevant API to map it to. There is no harm in putting "Not Mapped". Sometimes we put in "TBD" but that is less relevant now as we move towards an evergreen spec.
<front-endian-jane> David: We do use TBD on some things, some of which are actually mapped and we haven't gotten to them yet.
<front-endian-jane> jcraig: We are putting a pause on inspectable because how things work and are mapped is changing over time. We made changes to the IDL because of that as well.
<jamesn> RESOLUTION: android can specify aria-relevant as not mapped
<front-endian-jane> zakim, next item
Activity
css-meeting-bot commentedon Sep 3, 2026
The ARIA Working Group just discussed
Feedback on aria-relevant for Android Core AAM.The full IRC log of that discussion
<Zakim> agendum 5 -- [Feedback on aria-relevant for Android Core AAM](https://github.com//issues/268) -- taken up [from jamesn]<front-endian-jane> spectranaut_: We may have to punt both of these because David isn't here, but he asked for a video link, let's talk about this item later in the meeting
<front-endian-jane> zakim, take up item 7
css-meeting-bot commentedon Sep 3, 2026
The ARIA Working Group just discussed
Feedback on aria-relevant for Android Core AAM, and agreed to the following:RESOLUTION: android can specify aria-relevant as not mappedThe full IRC log of that discussion
<Zakim> agendum 5 -- [Feedback on aria-relevant for Android Core AAM](https://github.com//issues/268) -- taken up [from jamesn]<front-endian-jane> David: It was a year ago when we first talked about Android doing core AAM mappings. It got blocked but is starting up again. We have been discussing every mapping with the Android team so this is the first of potentially many mappings we want to discuss and ask questions about aria-relevant.
<jcraig> q+
<front-endian-jane> David: From the Chrome side of things we've done a lot to try to get it to work, supporting the whole vocabulary of what aria-relevant supports. The request for feedback is first, are there any concerns with us not mapping this to an OS API? We can discuss concerns with the Android team if a subset would be useful. Removals is not useful for us as far as we can tell.
<jamesn> Ack jc
<front-endian-jane> jcraig: There is no problem with Android listing it as not mapped. Voiceover does speak deletion differently as a down pitch. I see it most frequently with rich text fields. We had two live regions in on app, one for additions, one for removals. Some apps did that for a while. In the context of aria-notify I think it's total reasonable to not map it if Android doesn't currently support that.
<front-endian-jane> jcraig: Any implementation can choose to implement any portion of any spec. It isn't our job to tell an implementor what to implement, we can just advise. That is just my opinion, but others should give their opinions too.
<front-endian-jane> Lucas: Is this just about relevant, or other attributes too?
<front-endian-jane> jamesn: It is just about relevant, we have another agenda item for other attributes.
<spectranaut_> +1 to jcraig's advice
<front-endian-jane> jcraig: Other aria attributes aren't mapped, that doesn't mean it doesn't work. It can also mean there isn't a relevant API to map it to. There is no harm in putting "Not Mapped". Sometimes we put in "TBD" but that is less relevant now as we move towards an evergreen spec.
<front-endian-jane> David: We do use TBD on some things, some of which are actually mapped and we haven't gotten to them yet.
<front-endian-jane> jcraig: We are putting a pause on inspectable because how things work and are mapped is changing over time. We made changes to the IDL because of that as well.
<jamesn> RESOLUTION: android can specify aria-relevant as not mapped
<front-endian-jane> zakim, next item