From dcfb172704f3afb68a30425029ec834be2883274 Mon Sep 17 00:00:00 2001 From: bt Date: Sat, 8 Jun 2024 13:22:19 -0400 Subject: More content porting, on-going markdown changes for lowdown support --- build/simple-accessibility/index.html | 32 +++++++++++++++++++++----------- 1 file changed, 21 insertions(+), 11 deletions(-) (limited to 'build/simple-accessibility') diff --git a/build/simple-accessibility/index.html b/build/simple-accessibility/index.html index 11a9d74..68de724 100644 --- a/build/simple-accessibility/index.html +++ b/build/simple-accessibility/index.html @@ -1,39 +1,49 @@ - + Simple Accessibility - - + + +
-

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

+ +

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

Content

+ +

Content

+
  1. Use proper HTML structures (aside, header, main, footer elements as needed)
  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. +
  4. Ensure your website/app can be navigated completely (and properly) with only a keyboard
-

Images

+ +

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.

+ +

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