From f797bb14f7413df2abac6326c6df769004e50aa1 Mon Sep 17 00:00:00 2001
From: David Luevano Alvarado <david@luevano.xyz>
Date: Mon, 1 May 2023 09:35:25 -0600
Subject: small bugfix, add toc settings, update example site and delete
 unnecessary static assets

---
 .../src/doc/_includes/accessibility/background.html       | 15 ---------------
 1 file changed, 15 deletions(-)
 delete mode 100644 pyssg.xyz/live/static/fork-awesome/src/doc/_includes/accessibility/background.html

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

diff --git a/pyssg.xyz/live/static/fork-awesome/src/doc/_includes/accessibility/background.html b/pyssg.xyz/live/static/fork-awesome/src/doc/_includes/accessibility/background.html
deleted file mode 100644
index ac26a4a..0000000
--- a/pyssg.xyz/live/static/fork-awesome/src/doc/_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 {{ 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