> incentivise people to take the time to read
That, technically, is not what I'm proposing.
I suggest a burden on businesses or other parties that want to require a contract, in the form of a forced delay roughly proportional to the length/complexity of the contract they wish to use.
In practice, I expect businesses will find this unacceptable[1]. They would therefor work to find some alternative solution.
It might be that there wasn't a need for contracts in some situations, or that the contract language could be made much simpler/shorter. Alternatively, maybe a handful of "well known" standard contracts could become popular, similar in style to the Creative Commons licenses.
We cannot (and should not) avoid complex contracts entirely, but we might be able to fix a lot of common "simple" situations that shouldn't use a complex contract that few people read. By setting up the time burden, I expect complex contract (that might already have a "cooling off" period) wouldn't be significantly affected, but everyday small-time stuff will be incentivised to move away from the current practice of throwing usually-one-sided legalease at everything.
[1] I have often heard that the reason our current credit card system hasn't been updated to something with actual security (chip+pin, one time numbers, some sort of callback system, etc) is that any of these better methods would slow down transactions, resulting in less sales. Regardless of this being true or not, I'm attempting to utilize the perception.