From 07e4a2dafe248280b5610f8c7d09b0f30b530f54 Mon Sep 17 00:00:00 2001 From: Bradley Taunt Date: Mon, 10 Jun 2024 09:41:25 -0400 Subject: Initial modifications to rebuilt only changed files based on mod date, performance updates --- build/posts/simple-accessibility/index.html | 59 +++++++++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 build/posts/simple-accessibility/index.html (limited to 'build/posts/simple-accessibility/index.html') diff --git a/build/posts/simple-accessibility/index.html b/build/posts/simple-accessibility/index.html new file mode 100644 index 0000000..a3d4be6 --- /dev/null +++ b/build/posts/simple-accessibility/index.html @@ -0,0 +1,59 @@ + + + + + + + + Simple Accessibility + + + + + + + +
+

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. +
  2. Only use “fancy” grid-ordering for minor layout design - avoid rearranging important content via CSS
    3. +
+

Content

+
    +
  1. Use proper HTML structures (aside, header, main, footer elements as needed)
    2. +
  2. Make use of the aria-label attribute
    3. +
  3. Ensure your website/app can be navigated completely (and properly) with only a keyboard
    4. +
+

Images

+
    +
  1. Avoid using CSS backgrounds for content images (should only be used for patterns, layout design etc.)
    2. +
  2. Ensure proper alt attributes are provided on all images
    3. +
+

It isn’t much - but follow these basics and you’ll be one step closer to providing better accessibility to your users.

+ \ No newline at end of file -- cgit v1.2.3-54-g00ecf