From 3f6a9546ec13063d0d5bdf21d30a93d3e8aa6050 Mon Sep 17 00:00:00 2001 From: Bradley Taunt Date: Tue, 2 Jul 2024 14:22:21 -0400 Subject: Rebuild changes based off latest barf --- build/posts/simple-accessibility/index.html | 60 ----------------------------- 1 file changed, 60 deletions(-) delete mode 100644 build/posts/simple-accessibility/index.html (limited to 'build/posts/simple-accessibility') diff --git a/build/posts/simple-accessibility/index.html b/build/posts/simple-accessibility/index.html deleted file mode 100644 index 057d39d..0000000 --- a/build/posts/simple-accessibility/index.html +++ /dev/null @@ -1,60 +0,0 @@ - - - - - - - - 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