Ultimately I think this is what ::theme should help solve. https://meowni.ca/posts/part-theme-explainer/ I believe Polymer provides a shim for css custom properties support, are you currently using that or doing everything vanilla?

Yep! I talked a bit about the hiring process here: https://hashnode.com/ama/with-rob-dodson-cjiofjep90001l9vpzt7tpja3#cjiov9yjo00jx7gs191k1o9kl And the day to day here: https://hashnode.com/ama/with-rob-dodson-cjiofjep90001l9vpzt7tpja3# But in addition to those answers, I'd also say that the experience of being a developer at Google has been truly amazing. The folks on my team spend a lot of time thinking about and working on their communication skills. Which means we're fortunate enough to have a team that is super supportive and constructive. We boost one another up, and that's just awesome.

Hm good question. I don't actually know the answer. My hunch is that they're probably just different, with the front-end/UI roles tacking a bit more toward the knowledge required to do that job.

haha I remember doing the sweet hacks thing but also can't recall which episode that was >:( If it comes back to me I'll post a follow up! What do you think about the growing support amongst frameworks for compiling native elements? Cheers Do you mean things like React Native? Or is there some new hotness that I am not yet aware of? (very possible).

If you're doing something new I would really look at Polymer 3. I imagine Polymer 2 will be supported for quite some time, but 3.0 and Lit HTML are just really cool and give you much easier access to things like npm.

Tweeted! https://twitter.com/rob_dodson/status/1010968129281744896 We'll see what folks say :)

Hm, good question. I don't know of any resources off of the top of my head... Let me tweet this question out and see if other folks in the community have ideas.

I think progress is going really well. The main hurdle we're working through right now is around privacy, and making sure that folks don't feel like they have to leak the fact that they're using assistive technology just to get an improved web experience. Alice, Dominic, and James are doing amazing work in this space (see discussion: https://github.com/WICG/aom/issues/81) . Probably the best way to help it progress is to read through the spec/explainer, and bring up any issues you see. In particular, use cases where AOM seems like it would work but maybe doesn't—that stuff is super useful.

Aye aye, sir!

Oof yeah, Shadow DOM and accessibility can be tough. The main thing to be mindful of is that so much of ARIA is based on ID references, so you have to be really careful to make sure your labels and whatnot are inside the same scope. I showed off a workaround I use sometimes in this video ( https://www.youtube.com/watch?v=rr3c62Wnaeo) . We're hoping to make this better with AOM ( https://github.com/WICG/aom ) because it will let you label things with an element reference, instead of a string ID. If I recall, I believe Shadow DOM does reset the scoping for tabindex. So if you have something that's tabindex=10 inside a shadow root, it will be first in the tab order once focus moves into that shadow scope. But it won't be first in the tab order for the entire page.