summaryrefslogtreecommitdiff
path: root/snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/background.html
diff options
context:
space:
mode:
Diffstat (limited to 'snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/background.html')
-rw-r--r--snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/background.html15
1 files changed, 0 insertions, 15 deletions
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
deleted file mode 100644
index ac26a4a..0000000
--- a/snippets/Fork-Awesome-1.2.0/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>