[sasaf5]

Thanks for all the additional info! I should have added that my preference is for the definition of a unified gospel throughout the codebase/organization, Google's just being the one we ended up picking.

>Working with tabs allows everyone to work on the same codebase with their own preference.

This is where the problem starts. As someone who has to integrate code from a dozen devs, it seems that everyone has a sligthly different usage of tabs (TFA adding one more). If we can ever set everyone on the same page with tabs, I am fine with it. It's just that in production it always seems to cause problems. Spaces are easier to specify.

For the case of disability support, I'd risk to guess that different usages of tabs would end up derailing accessibility software just as much as it derails integration. But I'd prefer deferring this opinion to someone who has experience with it.