summaryrefslogtreecommitdiff
path: root/posts/simple-accessibility.md
diff options
context:
space:
mode:
authorBradley Taunt <brad@bt.ht>2023-11-27 12:25:51 -0500
committerBradley Taunt <brad@bt.ht>2023-11-27 12:25:51 -0500
commit14d227d46a2177a8928333894252d6299f531097 (patch)
treed41d48383d012f53823c9816a820e4e88c572c41 /posts/simple-accessibility.md
parentf6eed1a8c2f4fbf91fac9edd11e50f5c0ec939a2 (diff)
Trying to render posts all at once
Diffstat (limited to 'posts/simple-accessibility.md')
-rw-r--r--posts/simple-accessibility.md23
1 files changed, 23 insertions, 0 deletions
diff --git a/posts/simple-accessibility.md b/posts/simple-accessibility.md
new file mode 100644
index 0000000..6796e55
--- /dev/null
+++ b/posts/simple-accessibility.md
@@ -0,0 +1,23 @@
+# Simple Accessibility
+
+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.