History of H80 change

In completion of my assigned action, ACTION-256 (https://www.w3.org/WAI/GL/track/actions/256) I researched the history of the change in technique H80 from Sufficient to Advisory.  As a result of this I am marking the action complete.

History:
January 3, 2012 http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/complete.html (Sufficient)

Public comment April 30, 2012 http://lists.w3.org/Archives/Public/public-comments-wcag20/2012Apr/0031.html

LC-2612 in comment tracker: https://www.w3.org/2006/02/lc-comments-tracker/35422/NOTE-WCAG20-TECHS-20120103/2612

October 25, 2012 WG Survey https://www.w3.org/2002/09/wbs/35422/20121025misc/results#x2612

October 25, 2012 Minutes http://www.w3.org/2012/10/25-wai-wcag-minutes.html#item01

July 11, 2013 Review http://www.w3.org/WAI/GL/2013/WD-UNDERSTANDING-WCAG20-20130711/complete-diff.html (Moved to Advisory)

September 5, 2013 http://www.w3.org/TR/2013/NOTE-UNDERSTANDING-WCAG20-20130905/complete.html (Advisory)

Other comments on H80:
https://www.w3.org/2006/02/lc-comments-tracker/35422/WD-WCAG20-TECHS-20140107/2898

Based on my reading of the history and recollection of the discussions we've had, this technique is marked as advisory because while JAWS does allow the user to hear the heading that immediately precedes the current location  (therefore allowing a user to gain additional context for a link that provides insufficient information for the user to understand the purpose of that link), JAWS seems to be the only screen reader that does this.  As a result this technique is useful, but for now only in constrained environments, so rather than regarding it as a sufficient way to meet 2.4.4. (Link Context) the Working Group opted to make it Advisory.

AWK