Skip to main content

Home/ Web Accessibility/ Group items tagged feedback

Rss Feed Group items tagged

Vernon Fowler

Hiding Content for Accessibility - Snook.ca - 0 views

  • This clip technique is also what's provided in the .visuallyhidden helper class in HTML5 Boilerplate.
  • We've only begun using and testing this technique, so even this may not be perfect. Any feedback and suggestions are quite welcome.
Sandra Earl

Introducing WysiHat: An eventually better open source WYSIWYG editor - (37signals) - 0 views

  • WysiHat is a WYSIWYG JavaScript framework that provides an extensible foundation to design your own rich text editor. WysiHat stays out of your way and leaves the UI design to you. Although WysiHat lets you get up and running with a few lines of code, the focus is on letting you customize it. We are giving developers early access to the project while we continue to work out the remaining issues. Note: It’s extremely early. Contributors are welcome so please check out the project on GitHub and send us your feedback.
Vernon Fowler

WebAIM: Usable and Accessible Form Validation and Error Recovery - 0 views

  • Errors on top
  • As one would guess, the "Errors on top" approach causes the error message to appear before the form. When presented, focus should generally be set directly to this error message. This allows screen reader and keyboard users to immediately access the error message without having to find it amongst the rest of the page contents. The message should also be visually apparent. Focus can be set to the message with client-side scripting using JavaScript focus() or similar, or the server-generated page can include an anchor name in the URI (e.g., http://myserver.com/form.php#errormessage) which will set focus directly to a named anchor or element id located at the beginning of the feedback message.
  • also helpful to inform the user as to the number of errors that were detected
  • ...2 more annotations...
  • provide a link within the error message that will set focus to the appropriate form control
  • Regardless of the mechanism used to identify and recover from form errors, aria-invalid="true" should generally be set on each invalid form control. This attribute causes screen readers to identify the control as being "invalid" or in need of attention.
1 - 4 of 4
Showing 20 items per page