Your default should be WCAG-compliant. That's the whole point! A visually-impaired user shouldn't have to customise your site for it to be readable. Your site w

Your default should be WCAG-compliant. That's the whole point! A visually-impaired user shouldn't have to customise your site for it to be readable. Your site will be failing some accessibility metrics until you do that, and that will affect your search ranking etc. Plus it's generally a good audience-friendly thing to do. I was aware of the poll, but putting that up after the fact and it being only about the timestamp is a bad signal, too. It says that you're willing to pull the rug on whole sets of features at a whim and just because _you_ think it's the right thing to do. If you're trying to foster a community, I'd argue that this is not the best approach. These sorts of things could be reversible experiments - such as a banner at the top of the page saying "We're trying out removing timestamps and counters like likes! Click here to give us feedback or to switch back to the old UI." And then you keep track of everyone who switched back or re-enabled the feature you're fiddling with. Or you let people switch for a while and give their opinion after the test period.