| Tip |
SurveyGizmo |
| Include instructions and helpful tips at the top |
Yes
Up to user |
| Make your design, font-size, and color contrast appropriate |
Yes
complete theme control |
| Use Web Standards: in XHTML, CSS, and carefully with Javascript |
Yes |
Make sure form elements have associated label tags
(Note: For IE 6 you must use the for='id' attribute. Wrapping in the label won't work.) |
Yes
Yes |
| Use field focus indicators |
Yes |
| Keyboard navigable structure |
Yes |
| Access Keys - can be problematic |
Yes
User can add |
| Fieldsets & Legends |
Next release |
| Table questions - can be problematic |
Our next release includes labels, header attributes and summaries. Captions where applicable. |
| Don't depend on Javascript for basic interaction |
Yes |
| Avoid Javascript-dependent questions |
We are working towards using Javascript only for progressive enhancement |
| Navigable Per Question Error Handling |
Our next release includes per-question errors and question map for screen readers that shows questions with errors at the top of the screen |
Use images sparingly.
- Survey should function without images enabled or the ability to see them.
- Don't replace already accessible web standard form elements like radio buttons with images.
- All images should use Alt tags
- Use captions where appropriate |
Yes |
| All survey pages should have language attribute in the html tag and proper character set |
Yes |
| Ideally, deliver the same version of content to all users. The Web Accessibility Initiative considers delivering separate versions of content to disabled users a bad practice |
Yes |
