As a sidenote, as I now recall it, I was just too shocked by the phasing out of framesets in order to recognize the "undeprecation" of <b> and <i>. (I really fa

As a sidenote, as I now recall it, I was just too shocked by the phasing out of framesets in order to recognize the "undeprecation" of <b> and <i>. (I really fail to see where it helps, if future browsers fail to present historic documents in appropriate and meaningful context. Even more so, when 99% of these structures could be easily translated to semantic regions and landmarks, like header/banner, main, footer, aside, etc, even navigations could be inferred with ease by screen readers. Moreover, screen readers now have to support dynamic updates of isolated regions anyway in order to cope with JS frameworks. There was probably never a time, when frames would have posed that small a problem than at this point in time.)