Merge pull request #201 from Access4all/content/aria-is-good

ARIA is good

pages/knowledge/aria/README.md

@@ -6,4 +6,4 @@ changed: "2018-05-02"
 
 # ARIA - when HTML simply is not enough
 
-**There are indeed situations where standard HTML does not provide functionalities for all the requirements developers may have for implementing modern and interactive websites. For this, the Accessible Rich Internet Applications (ARIA) technical specification was introduced. In this chapter, we introduce how it is purposely used, show its potential and shortcomings as well as alternatives to it.**
+**There are indeed situations where standard HTML does not provide functionalities for all the requirements developers may have for implementing modern and interactive websites. For this, the Accessible Rich Internet Applications (ARIA) technical specification was introduced. In this chapter, we introduce how it is purposely used, show its potential as well as its shortcomings (and alternatives, if needed).**

pages/knowledge/aria/bad-practices/README.md

@@ -6,9 +6,9 @@ changed: "2018-04-12"
 
 # Bad ARIA practices
 
-**There are certain situations where ARIA is a good (and maybe the only) way to go. But if done wrong, usage of ARIA often leads to even worse accessibility. Especially accessibility novices tend to misuse ARIA to optimise smelly code. Here we explain some of the typical dos and do nots.**
+**There are certain situations where ARIA is a good (and maybe the only) way to go. But if done wrong, usage of ARIA often leads to even worse accessibility. Especially accessibility novices tend to misuse ARIA to "optimise" smelly code.**
 
-ARIA is often misunderstood as "general repair kit" for accessibility problems. Developers new to accessibility usually think that ARIA that can be used to fix accessibility problems for all sorts of bad HTML code. In general though, throwing some ARIA attributes into the mix of bad semantics does not leverage any problem. Most of the time, the exact opposite is the case.
+ARIA is often misunderstood as "general repair kit" for accessibility problems. Developers new to accessibility usually think that ARIA can be used to fix accessibility problems for all sorts of bad HTML code. In general though, throwing some ARIA attributes into the mix of bad semantics does not leverage any problem (most of the time, the exact opposite is the case).
 
 ## Fixing broken semantics
 
@@ -150,9 +150,3 @@ So in most cases this holds true: if you face a situation where a screen reader
 Sometimes, developers try to hide focusable elements (or elements that contain focusable children) from screen readers using `aria-hidden`. This leads to unpredictable behaviour in many screen readers, as the browser still allows to focus such elements using the `Tab` key, but because of `aria-hidden` screen readers will not announce it.
 
 If you are really curious and want to learn more about this, skip ahead and read [Hiding elements from screen readers using aria-hidden](/examples/hiding-elements/from-screen-readers).
-
-The purpose of hiding something from a specific user group leads us to the next misuse of ARIA. Read on.
-
-## Conclusion: caution with ARIA!
-
-ARIA is an intriguing approach to make the web a more accessible place. In most situations though, it is neither needed (because there are usually better ways to achieve the same result) nor useful (because browser and screen reader support is still shaky).