aboutsummaryrefslogtreecommitdiff
path: root/_posts/2018-09-07-simple-accessibility.md
diff options
context:
space:
mode:
Diffstat (limited to '_posts/2018-09-07-simple-accessibility.md')
-rw-r--r--_posts/2018-09-07-simple-accessibility.md26
1 files changed, 26 insertions, 0 deletions
diff --git a/_posts/2018-09-07-simple-accessibility.md b/_posts/2018-09-07-simple-accessibility.md
new file mode 100644
index 0000000..035dc63
--- /dev/null
+++ b/_posts/2018-09-07-simple-accessibility.md
@@ -0,0 +1,26 @@
+---
+layout: post
+title: "Simple Accessibility"
+date: 2018-09-07
+---
+
+
+Implementing proper accessibility practices can seem a little daunting at first, but there are a few basic standards you can introduce into your project work-flow that are fairly straightforward:
+
+## Basic design
+
+1. Test that your project has the proper contrast color settings between type, backgrounds, icons etc.
+2. Only use "fancy" grid-ordering for minor layout design - avoid rearranging important content via CSS
+
+## Content
+
+1. Use proper HTML structures (aside, header, main, footer elements as needed)
+2. Make use of the [aria-label attribute](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute)
+3. Ensure your website/app can be navigated completely (and properly) with only a keyboard
+
+## Images
+
+1. Avoid using CSS backgrounds for content images (should only be used for patterns, layout design etc.)
+2. Ensure proper `alt` attributes are provided on all images
+
+It isn't much - but follow these basics and you'll be one step closer to providing better accessibility to your users.