Most of the time when I see a J programmer "read" some J code, it really means taking the spec and slowly, incrementally building up towards the same solution as the code they were handed. I have not seen them have much success at "reading" more than a couple lines of idiomatic code without being told what it does. I doubt it would scale up beyond a few lines of code (≈ a few "paragraphs" of code in Blub), having seeing a veteran mistake some quartic-time code for the Floyd-Warshall algorithm (which is cubic time).
I have not found this definition of "read" to be common in other language communities.
Now, I don't know either K or Q, but I have a very, very, very hard time believing that they are too terse and unreadable because of that.
From my experience, the "improvements in readability" are of course good, but they only shorten the time to master the language. Once you learn the language well enough, it becomes readable. And the very few syntactic issues which are objectively hard to distinguish/are confusing the eye, etc. tend to be worked around with formatting and font settings.
Written Japanese is totally impossible to read if you don't know it - and it takes reasonably longer to learn it. However, once you know it, it's readable. A Japanese person reading a newspaper in Japanese uses as much effort as me reading a newspaper in my native language.