Optimize ARIA overview

[backflip]

From #201:

Note to myself: I suppose we should keep a conclusion, but write something like this:

ARIA can be the right thing to use in those rare where standard HTML does not offer a solution for an implementation requirement (for example, some advanced control patterns like tabs). Be very careful though and sure to test it thoroughly using screen readers, as not every ARIA feature is generally supported yet.

Or the conclusion of the deleted "Good practices" page:

There are only rare situations where HTML is not enough. In those (and only those) situations, using ARIA is advised. In other situations, when the use of a clean and semantically correct HTML structure can provide a solution, usage of ARIA is strongly discouraged. This is due to its non-homogenous support among browsers and screen readers.

We should maybe add this to the "Conclusion" on the "Purpose" page?

Originally posted by @jmuheim in #201

[ralf57]

@jmuheim what about this?