From 8d2ce11daf87267091ffec971cd46d16937cc69c Mon Sep 17 00:00:00 2001 From: pdp8 Date: Thu, 25 Aug 2022 19:48:19 +0200 Subject: fork-awesome removed --- .../accessibility/accessibility-manual.html | 121 --------------------- .../doc/_includes/accessibility/background.html | 15 --- .../src/doc/_includes/accessibility/other.html | 17 --- 3 files changed, 153 deletions(-) delete mode 100644 snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/accessibility-manual.html delete mode 100644 snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/background.html delete mode 100644 snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/other.html (limited to 'snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility') diff --git a/snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/accessibility-manual.html b/snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/accessibility-manual.html deleted file mode 100644 index 6878507..0000000 --- a/snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/accessibility-manual.html +++ /dev/null @@ -1,121 +0,0 @@ -
- -

- - Manually make your icons accessible -

- -

When using icons in your UI, there are manual techniques and ways to help assistive technology either ignore or better understand {{ site.forkawesome.name }}.

- -

Icons used for pure decoration or visual styling

-

If you're using an icon to add some extra decoration or branding, it does not need to be announced to users as they are navigating your site or app aurally. Additionally, if you're using an icon to visually re-emphasize or add styling to content already present in your HTML, it does not need to be repeated to an assistive technology-using user. You can make sure this is not read by adding the aria-hidden="true" to your {{ site.forkawesome.name }} markup.

- -
-{% highlight html %} - -{% endhighlight %} -an icon being used as pure decoration -
- -
-{% highlight html %} -

- - Fork Awesome, a fork of the iconic font and CSS toolkit -

-{% endhighlight %} -an icon being used as a logo -
- -
-{% highlight html %} - View this project's code on Github -{% endhighlight %} -an icon being used in front of link text -
- -

Icons with semantic or interactive purpose

-

- If you're using an icon to convey meaning (rather than only as a decorative element), ensure that this meaning is also conveyed to assistive technologies. This goes for content you're abbreviating via icons as well as interactive controls (buttons, form elements, toggles, etc.). There are a few techniques to accomplish this: -

- -

If an icon is not an interactive element

-

- The simplest way to provide a text alternative is to use the aria-hidden="true" attribute on the icon and to include the text with an additional element, such as a <span>, with appropriate CSS to visually hide the element while keeping it accessible to assistive technologies. In addition, you can add a title attribute on the icon to provide a tooltip for sighted mouse users. -

- -
-{% highlight html %} -
-
- - Time to destination by car: -
-
4 minutes
- -
- - Time to destination by bike: -
-
12 minutes
-
-{% endhighlight %} - an icon being used to communicate travel methods -
- -
-{% highlight html %} - -60 minutes remain in your exam - - -30 minutes remain in your exam - - -0 minutes remain in your exam -{% endhighlight %} - an icon being used to denote time remaining -
- -

If an icon represents an interactive element

-

- In the case of focusable interactive elements, there are various options to include an alternative text or label to the element, without the need for any visually hidden <span> or similar. For instance, simply adding the aria-label attribute with a text description to the interactive element itself will be sufficient to provide an accessible alternative name for the element. If you need to provide a visual tooltip on mouseover/focus, we recommend additionally using the title attribute or a custom tooltip solution. -

- -
-{% highlight html %} - - - -{% endhighlight %} - an icon being used to communicate shopping cart state -
- -
-{% highlight html %} - - - -{% endhighlight %} - an icon being used as a link to a navigation menu -
- -
-{% highlight html %} - - - -{% endhighlight %} - an icon being used as a delete button's symbol with a title attribute to provide a native mouse tooltip -
- - -
- -
-
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 @@ -
-

About Icon Fonts & Accessibility

-

- 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. -

- - -
diff --git a/snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/other.html b/snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/other.html deleted file mode 100644 index d3054ba..0000000 --- a/snippets/Fork-Awesome-1.2.0/src/doc/_includes/accessibility/other.html +++ /dev/null @@ -1,17 +0,0 @@ -
-

Other cases and information

-

- While the scenarios and techniques here help avoid some serious issues and confusion, they are not exhaustive. There are many complex contexts and use cases when it comes to accessibility, such as users with low vision who need a high color contrast ratio to see UI. There are some great tools and resources to learn from and work on these issues out there. Here are a few reads we recommend. -

- - - -

- We'll continue to work on these under the larger topic of accessibility, but in the meantime, let us know if any bugs or issues. -

-
-- cgit v1.2.3