Chris de Almeida

I had to create my own component that extends this one in order to get this functionality. It would be nice if it was built in.

@jkusa - A computed property would not have worked for me as I need knowledge of the DOM element in question, and `this.$()` would only give you the container. Anyhow,...

it would be nice to at least have an option to toggle. so you could preserve the existing behavior, but people could opt-in for WCAG AA compliance if they wanted....

**it's worth noting that WCAG 3 will use a new system [APCA (Advanced Perceptual Contrast Algorithm)](https://github.com/Myndex/apca-w3).** as an aside, I ended up creating [a11y-badges](https://github.com/a11y-badges/a11y-badges) for exactly this reason. I have...

current status?

not _as_ confusing: ```js const numFormat = new Intl.NumberFormat('en-US', { style: 'unit', unit: 'byte', notation: 'compact' }); let num = 1; for (let i = 0; i < 15; i++)...

see also: #730

agree, a blanket ban would be overly broad. I'm not sure we could nail down a qualified prohibition either. open to ideas

in my `index.html` I do not have hardcoded script/src tags. Due to unique requirements of our application, the `src` path is modified dynamically at runtime. So I think it is...

`""`