@mattwilcox @eleventy @CraftCMS

Sigh, not this again.

If that were true there would be peer reviewed research about the *accessibility* of it.

Most discussion and decisions about tabs and spaces are about opinion. The few who actually use accessibility solutions have stated that there *tools* solve it for them and that inconsistency and change is more disruptive.

Spaces vs tabs is like Sega vs Nintendo. It’s mostly a sunk cost fallacy.

@mattwilcox

Let me point out once again that my biggest issue is the lack of research in this area.

As for the links (yes, I had read them) they seem to ignore the various types of disabilities or the fact that various assistive technology have already solved that problem in various ways.

There is a reason why nobody seems to do proper research: The problem space is too complex for an easy answer.

@DevWouter To use analogies - I don’t really find “the disableds that use our pavements already have wheelchairs that can deal with our lack of curb drops, why change?” a compelling argument for not putting in curb drops when we build pavements. It also erases both the additional trouble they have to go to, and the people that don’t use the pavements because they don’t have wheelchairs that can manage curbs.

If we are building new pavements; just add curb drops.

@mattwilcox

Curb drops are researched and documented. There are in fact both rules and guidelines when they should and how they should be used.

This is not true for spaces or tabs. As such it becomes hard to claim that it is an improvement.

This problem is exacerbated due to strongly opinionated people, anecdotal reasoning, not understanding the problem and incorrect information.

It saddens me that problem is not new yet we are *still* missing definitive proof.

@mattwilcox

Let me add one more thing. I sincerely *hope* that tabs do improve the life of the various types of disabled developers. I just wish we could proof it.