From 45654ffc5cc4532c2189c88d46a0374038b53c9f Mon Sep 17 00:00:00 2001
From: Treer <treer.git@the-bordello.com>
Date: Sat, 30 Apr 2016 21:36:19 +1000
Subject: update font-awesome library to 4.6.1 Perhaps this should be done as a
 submodule instead?

---
 .../src/_includes/accessibility/background.html           | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 library/font_awesome/src/_includes/accessibility/background.html

(limited to 'library/font_awesome/src/_includes/accessibility/background.html')

diff --git a/library/font_awesome/src/_includes/accessibility/background.html b/library/font_awesome/src/_includes/accessibility/background.html
new file mode 100644
index 000000000..5ca864826
--- /dev/null
+++ b/library/font_awesome/src/_includes/accessibility/background.html
@@ -0,0 +1,15 @@
+<div id="background">
+  <h2 class="page-header">Icon Fonts &amp; Accessibility</h2>
+  <p>
+    Modern versions of assistive technology, like screen readers, will read CSS generated content (how Font Awesome icons are rendered), as well as specific Unicode characters. When trying our default markup for rendering icons, assisistive technology may have the following problems.
+  </p>
+
+  <ul>
+    <li>
+      The assistive technology may not find any content to read out to a user
+    </li>
+    <li>
+      The assistive technology may read the unicode equivalent, which could not match up to what the icon means in context, or worse is just plain confusing
+    </li>
+  </ul>
+</div>
-- 
cgit v1.2.3