Sample Form
<label for="email">Email</label>
<input id="email" type="email" aria-required="true" />
Form validation
Dave Rupert davatron5000
🚀
davatron5000
/ accessibleforms.md
Created
February 19, 2013 17:47
davatron5000
/ colorcontrast.md
Created
February 19, 2013 17:43
davatron5000
/ wave-your-website.md
Created
February 6, 2013 15:31
davatron5000
/ use-title-attributes-correctly.md
Last active
December 12, 2015 05:09
Short answer: Don't use them, except in special circumstances.
HTML title attributes are often perceived as an accessibility (and SEO) bonus, but the opposite is true. For screen reader users the content included inside of the title attribute is typically unncessary, redundant, and possibly not even used. Conversely, content being put in the title attribute is being hidden from the (probable) majority of your users. If information is being hidden from the majority of your users, then it's probably not necessary.
There are a few times when using a title attribute is appropriate:
- For
<frame>and<iframe>elements - For providing a label when a text label would be redundant
davatron5000
/ myth-screen-readers-dont-use-javascript.md
Last active
December 12, 2015 05:08
A common misconception among web developers is that screen readers only read the non-JavaScript page. Due to this misconception, we sometimes assume it's unnecessary to make JavaScript apps and other functionality accessible. This is categorically false.
According to a May 2012 survey conducted by WebAIM, 98.6% of screen reader users have JavaScript enabled.
Be sure to make efforts to ensure that the JavaScript functionality (apps, custom UI controls, forms, etc) within your site is accessible. It could be as simple as opting for native links and form inputs instead of custom scripted form elements.
davatron5000
/ role-application.md
Last active
December 11, 2015 20:48
Summary: Use role="application" very sparingly, if at all.
NEVER use role="application" on a widely containing element such as <body> if your page consists mostly of traditional widgets or page elements such as links that the user does not have to interact with in focus mode. Using role="application" unnecessarily can cause huge headaches for any assistive technology user trying to use your site/application. Only put it on the <body> element if your page consists solely of a widget or set of widgets that all need the focus mode[^focusmode] to be turned on.
Do Use
- Use if your page has no resemblance to a classic document in roughly over 90% of its content
- Use clear labels within your application
davatron5000
/ futureproof_a11y.md
Created
January 18, 2013 01:43
| layout | post | |
|---|---|---|
| title | How-to: Future proof your accessibility efforts. | |
| description | Ways to make your accessibility effort as future proof as possible. | |
| categories |
|
davatron5000
/ futureproof_a11y.md
Last active
December 11, 2015 05:19
| layout | post | |
|---|---|---|
| title | How-to: Future proof your accessibility efforts. | |
| description | Ways to make your accessibility effort as future proof as possible. | |
| categories |
|
Backstory: I decided to crowdsource static site generator recommendations, so the following are actual real world suggested-to-me results. I then took those and sorted them by language/server and, just for a decent relative metric, their Github Watcher count. If you want a heap of other projects (including other languages like Haskell and Python) Nanoc has the mother of all site generator lists. If you recommend another one, by all means add a comment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <h1>Contact</h1> | |
| <form action="#" method="post"> | |
| <div> | |
| <label for="name">Text Input:</label> | |
| <input type="text" name="name" id="name" value="" tabindex="1" /> | |
| </div> | |
| <div> | |
| <h4>Radio Button Choice</h4> | |