I am horrified to say that it is mid-2023 and browsers are moving backward on accessibility support for elements with CSS display properties.
Chrome decided anything with `display: contents` is just text. Safari regressed overall but did tables dirty.
Firefox is the only one to have improved and now has the best support overall.
adrianroselli.com/2022/07/its-…
It’s Mid-2022 and Browsers (Mostly Safari) Still Break Accessibility via Display Properties
It was late 2020 when I last tested how browsers use CSS display properties to break the semantics of elements.Adrian Roselli
Adrian Roselli
in reply to Adrian Roselli • • •I don’t know which is worse, Safari repeatedly claiming for a year that display bugs are getting fixed in the next version or Chrome just silently tanking support.
I don’t have the energy today to file new bugs. But I did update the open Can I Use bug:
github.com/Fyrd/caniuse/issues…
Consistency needed in `display: contents` · Issue #6469 · Fyrd/caniuse
GitHubAdrian Roselli
in reply to Adrian Roselli • • •To reiterate, I want to thank the Firefox team @mozilla for fixing tables with `flex` and `grid` applied to them.
Huge improvement, better experience, much accessibility.