From 6d2c067f0d6bc78eef7ececcec3eba71cbb5d80c Mon Sep 17 00:00:00 2001
From: David Luevano Alvarado <david@luevano.xyz>
Date: Tue, 1 Jun 2021 03:21:33 -0600
Subject: add fork awesome, contact and donate pages, update general style and
 update readme

---
 .../src/doc/_includes/accessibility/background.html       | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 static/fork-awesome/src/doc/_includes/accessibility/background.html

(limited to 'static/fork-awesome/src/doc/_includes/accessibility/background.html')

diff --git a/static/fork-awesome/src/doc/_includes/accessibility/background.html b/static/fork-awesome/src/doc/_includes/accessibility/background.html
new file mode 100644
index 0000000..ac26a4a
--- /dev/null
+++ b/static/fork-awesome/src/doc/_includes/accessibility/background.html
@@ -0,0 +1,15 @@
+<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 {{ site.forkawesome.name }} 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-54-g00ecf