ARIA7 Remove Example 1

Changing accessible name from rendered/visible text  generally causes accessibility issues. Especially, changing accessible name completely different one from rendered/visible text causes serious accessibility issues.

ARIA 1.0 Recommendation provides some examples of similar issues. In a note of |aria-hidden| 
http://www.w3.org/TR/2014/REC-wai-aria-20140320/states_and_properties#aria-hidden

> Note: Authors are advised to use extreme caution and consider a wide range of disabilities when hiding visibly rendered content from assistive technologies. For example, a sighted, dexterity-impaired individual may use voice-controlled assistive technologies to access a visual interface. If an author hides visible link text "Go to checkout" and exposes similar, yet non-identical link text "Check out now" to the accessibility API, the user may be unable to access the interface they perceive using voice control. Similar problems may also arise for screen reader users. For example, a sighted telephone support technician may attempt to have the blind screen reader user click the "Go to checkout" link, which they may be unable to find using a type-ahead item search ("Go to…").

As Example 1 of ARIA7 changes accessible name from "Read more..." to "Storms hit east coast", people who use voice control or who are blind and communicating with sighted person may face serous issues.

Thus we should get rid of Example 1 of ARIA7.