If the attribute is still being supported by browsers, the companies do not have to rush and spend money to fix it. That’s a business decision. Eventually the browsers will stop supporting the obsolete attributes then their code will “break” if they have not implemented a change by then.
Most people, especially businesses with large complex sites, are reluctant to change something that seems to be working for them. Besides that, changing a complex site even a tiny bit has the potential of introducing unexpected bugs, so considerable testing is needed. Time is salary money. Failures caused by bugs can cost the company big money in lost sales so developing a test plan and paying the testers is cheaper than risking a code failure… and so it goes.
Let’s consider the issue of one asasass and inline styls vs CSS styles or px vs ems, or ,
Trying to convince him to invest in himself by taking HTML and CSS classes or even taking our good adivice is like talking to a fence post. He either refuses to change or reverts back to the junky archaic inline code as soon as he can. We keep nudging him forward, though.
We all have our priorities. I have no idea what yours are. I hope you do, because you only get one shot at life. I’ve tried to make mine something I could be pleased to remember when I get old and not wasted.