Fixes #1020. Clarify a versus button usage.

GoogleChrome · Jul 16, 2019 · 949c895 · 949c895
1 parent dbf3792
commit 949c895
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/src/site/content/en/accessible/use-semantic-html/index.md b/src/site/content/en/accessible/use-semantic-html/index.md
@@ -100,8 +100,10 @@ should you choose?
 
 - If clicking on the element will perform an _action_ on the page, use
   `<button>`.
-- If clicking on the element will _navigate_ the user to a new page (or load new
-  content in a single-page web app) then use `<a>`.
+- If clicking on the element will _navigate_ the user to a new page then use
+  `<a>`. This includes single page web apps which load new content and update
+  the URL using the
+  [History API](https://developer.mozilla.org/en-US/docs/Web/API/History).
 
 The reason for this is that buttons and links are announced differently by
 screen readers. Using the correct element helps screen reader users know which