Nobody is saying everything needs to be that way. But some things do. This is an attempt to make those things work better with search engines.
There's never been a case that's gone to verdict on the matter, so its still somewhat of a gray area. But the reason they don't go to verdict is because the offending company has always agreed to a large cash settlement. Target's $6MM settlement with the Federation for the Blind is the most recent case.[1]
There's plenty of large websites that drop the ball here (e.g., Reddit), but that doesn't mean its safe to do so. Ignore accessibility at your own risk.
[1]http://www.webstandards.org/2008/08/28/what-the-target-settl...
Can you give an example of a Web application, which relies on Javascript to function, which also has content that even _should_ be indexed but is hiding behind Ajax?
Does Google need to index Backpack or something?
280 Slides the application doesn't need to be indexed. They don't need to know where the New button is. They don't need to know where the scrollers are.
But shared presentations do need to be indexed. Fortunately, it's not all that difficult to construct the content in such a way that it can be indexed. We give out unique URLs for presentations which aren't # delimited, so we could actually serve the text content alongside the viewable presentation. We don't currently, but it would be a relatively easy change.