This may just be a terminology mismatch. I would consider the tasks you've mentioned to just be part of your day-to-day work, and yes, if you're not doing those you can expect to be pulled up by your line manager/pm/whoever's running the show. I usually see accountability talked about in terms of the quality and timeliness of the deliverable. If your team's deliverable isn't on time, it's not because developer 'A' failed to deliver their ticket on time, it's because the team as a whole didn't manage their resources appropriately, didn't spot the slippage and didn't adjust or escalate the issue in time. If there's a bug in the code, it's not because developer 'B' forgot a bounds check, it was down to the whole team to ensure the quality of the deliverable, probably via code review.
Holding the individual solely responsible for this sort of thing is counterproductive, as it tends to lead to people trying to cover up mistakes, which rarely goes well, and means others don't get a chance to learn from it.
None of which is to say that the indivuduals shouldn't be held to the quality of their work. If the work they're delivering consistently isn't up to scratch, whether that's found through code review or a bug report, they first need help to improve, and only if that doesn't work should they face the inevitable consequences.
As per the article:
polyethylene terephthalate (PET)
They're working on increasing to industrial scale.
The description of their process sounds fairly exciting, in that it doesn't need a solvent, uses a cheap, non-toxic catalyst and produces PET precursors. If they manage to get it to industrial scale they'll go some way to solving the plastic problem.