aboutsummaryrefslogtreecommitdiff
path: root/build/simple-accessibility/index.html
diff options
context:
space:
mode:
Diffstat (limited to 'build/simple-accessibility/index.html')
-rw-r--r--build/simple-accessibility/index.html32
1 files changed, 21 insertions, 11 deletions
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 @@
<!doctype html>
-<html lang="en" id="top">
+<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="icon" href="data:,">
<title>Simple Accessibility</title>
- <link href="https://bt.ht/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
- <style>*{box-sizing:border-box;}body{font-family:sans-serif;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{overflow:auto;}table{text-align:left;width:100%;}</style>
+ <link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
+ <link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" />
+<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
</head>
<nav>
- <a href="#menu">Menu &darr;</a>
+ <a href="#menu">Menu &darr;</a>
</nav>
<main>
-<h1>Simple Accessibility</h1>
+<h1 id="simple-accessibility">Simple Accessibility</h1>
+
<p>2018-09-07</p>
+
<p>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:</p>
-<h2>Basic design</h2>
+
+<h2 id="basic-design">Basic design</h2>
+
<ol>
<li>Test that your project has the proper contrast color settings between type, backgrounds, icons etc.</li>
-<li>Only use "fancy" grid-ordering for minor layout design - avoid rearranging important content via CSS</li>
+<li>Only use &#8220;fancy&#8221; grid-ordering for minor layout design - avoid rearranging important content via CSS</li>
</ol>
-<h2>Content</h2>
+
+<h2 id="content">Content</h2>
+
<ol>
<li>Use proper HTML structures (aside, header, main, footer elements as needed)</li>
<li>Make use of the <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute">aria-label attribute</a></li>
-<li>Ensure your website/app can be navigated completely (and properly) with only a keyboard</li>
+<li>Ensure your website&#47;app can be navigated completely (and properly) with only a keyboard</li>
</ol>
-<h2>Images</h2>
+
+<h2 id="images">Images</h2>
+
<ol>
<li>Avoid using CSS backgrounds for content images (should only be used for patterns, layout design etc.)</li>
<li>Ensure proper <code>alt</code> attributes are provided on all images</li>
</ol>
-<p>It isn't much - but follow these basics and you'll be one step closer to providing better accessibility to your users.</p>
+
+<p>It isn&#8217;t much - but follow these basics and you&#8217;ll be one step closer to providing better accessibility to your users.</p>
<footer role="contentinfo">
<h2>Menu Navigation</h2>
<ul id="menu">