Josh Schneider

">=0.12.10"

Thanks, @line47!

Hey, @forrestbaer . Good question. I could see the utility of having an optional override of baked-in `aria-live` and related attributes on any component, because the context in which the...

One more thing (going back to look at source). So, in this case, it's the `Choice` component that includes `aria-live`, `aria-relevant`, and `aria-atomic`, and looks at the value of `checkedChildren`...

@forrestbaer, here are 2 PRs from our repo that cite the issue: https://github.cms.gov/CMS-MCT/coverage-tools-frontend/pull/1802 https://github.cms.gov/CMS-MCT/coverage-tools-frontend/pull/1756 In the 2nd case, the fundamental issue is that a state change on a component containing...

> The other thing I was thinking about is in the long run, it might be good to have a component that handles the aria-live announcements on a page. So...

Thanks, @forrestbaer. I'll have to loop back to look at the original issue we had on MCT with these nested `aria-live` attributes and let you know. I still think the...

@forrestbaer, it's been so long, I had to dig in to figure out what looks like it would help. Ultimately, my best assessment is that an actual solution, in this...

In our source code: ```js checkedChildren: ( { const { checked, value } = event.currentTarget; const selected = checked && !currentSelections.includes(value) ? [...currentSelections, value] : currentSelections.filter(f => f !== value);...

Would be very nice if there was something like `aria-live="exception"` or if `aria-live="off"` could be nested inside `aria-live="polite"` and act as an override for one part of the tree, but...