From a5f843ba9ba3dd3ce9ad22a89d57dfcb5fa46586 Mon Sep 17 00:00:00 2001
From: Mario Vavti <mario@mariovavti.com>
Date: Mon, 26 Feb 2018 11:05:48 +0100
Subject: switch to fork-awesome

---
 .../src/_includes/accessibility/background.html           | 15 ---------------
 1 file changed, 15 deletions(-)
 delete 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
deleted file mode 100644
index da97e4762..000000000
--- a/library/font_awesome/src/_includes/accessibility/background.html
+++ /dev/null
@@ -1,15 +0,0 @@
-<div id="accessibility-background">
-  <h4 class="margin-top-none">About Icon Fonts &amp; Accessibility</h4>
-  <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 reading 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