From e3c672f4648997dbe00624e09c63c990a8ea3596 Mon Sep 17 00:00:00 2001
From: pdp8 <pdp8@pdp8.info>
Date: Mon, 22 Aug 2022 00:52:15 +0200
Subject: audio and video rendering, Fork-Awesome-1.2.0 included

---
 .../src/doc/_includes/accessibility/background.html       | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/background.html

(limited to 'snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/background.html')

diff --git a/snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/background.html b/snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/background.html
new file mode 100644
index 0000000..ac26a4a
--- /dev/null
+++ b/snippets/Fork-Awesome-1.2.0/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