diff options
| author | Bradley Taunt <bt@btxx.org> | 2024-07-02 14:28:49 -0400 |
|---|---|---|
| committer | Bradley Taunt <bt@btxx.org> | 2024-07-02 14:28:49 -0400 |
| commit | dc6db80fa72286704849ef61ee0e5ccb5841cb09 (patch) | |
| tree | 9235d796229d49211c27a07b9d18585d503baa94 /_posts/2018-09-07-simple-accessibility.md | |
| parent | 088c87bcb58be576308da503d4f11a68843c5013 (diff) | |
Conversion to barf for testing purposes
Diffstat (limited to '_posts/2018-09-07-simple-accessibility.md')
| -rw-r--r-- | _posts/2018-09-07-simple-accessibility.md | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/_posts/2018-09-07-simple-accessibility.md b/_posts/2018-09-07-simple-accessibility.md deleted file mode 100644 index 035dc63..0000000 --- a/_posts/2018-09-07-simple-accessibility.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -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. |