Web Accessibility - For Users of Content Management Systems - Forms and Frames Supplement

More information for users of content management systems regarding how to evaluate your website for accessibility if it contains forms and frames.

 Forms

Organization

  • Instructions do not rely upon shape, size, or visual location (e.g., "Click the square icon to continue" or "Instructions are in the right-hand column").

  • Instructions do not rely upon sound (e.g., "A beeping sound indicates you may continue.").

  • The tab order through a form is logical and intuitive.

  • It is visually apparent which page element has the current keyboard focus (i.e., as you tab through the form, you can see where you are.)

  • When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.

  • Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, and properly positioned form labels. (Advanced: fieldsets/legends can also be used.)

Image Buttons

  • All form image buttons have appropriate, equivalent alternative text.

  • Form buttons have a descriptive value.

  • The purpose of each form image button can be determined from the link text alone, or from the link text and its context (e.g., surrounding paragraph, list item, table cell, or table headers).

  • Form image buttons with the same text that go to different locations are readily distinguishable.

  • Labels for forms buttons are informative. Avoid duplicating label text (e.g., "First Name") unless the structure provides adequate differentiation between them.

Inputs

  • Form inputs have associated text labels.

  • Text labels are associated with form input elements. (Advanced: Related form elements are grouped with fieldset/legend.)

  • Labels for forms inputs are informative. Avoid duplicating label text (e.g., "First Name") unless the structure provides adequate differentiation between them.

  • When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.

Input Validation and Errors

  • Required form elements or form elements that require a specific format, value, or length provide this information within the element's label.

  • If utilized, form validation errors are presented in an efficient, intuitive, and accessible manner. The error is clearly identified, quick access to the problematic element is provided, and user is allowed to easily fix the error and resubmit the form.

  • If an input error is detected, provide suggestions for fixing the input in a timely and accessible manner.

Optional for Forms

  • The purpose of each form image button can be determined from the link text alone.

  • There are no form image buttons with the same text that go to different locations.

  • Provide instructions and cues in context to help in form completion and submission.

  • If the user can submit information, the submission is reversible, verified, or confirmed.

 Frames

Organization

  • Frames are appropriately titled.

  • The reading and navigation order (between frames and within a frame) is logical and intuitive.

  • If a page uses frames and the frames are appropriately titled, this is a sufficient technique for bypassing individual frames.

  • It is visually apparent which page element has the current keyboard focus (i.e., as you tab through the page, you can see where you are.)

  • When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.

  • Navigation links that are repeated on web pages do not change order when navigating through the site.

  • Elements that have the same functionality across multiple web pages are consistently identified.

Optional for Frames

None applicable.




Keywords:web, accessibility, accessibility standards, Section 508, WCAG 2.0, forms, frames supplement, for users of content management systems, cms   Doc ID:50811
Owner:Sandi A.Group:Accessibility
Created:2015-04-23 15:14 CDTUpdated:2015-06-30 12:55 CDT
Sites:Accessibility, DoIT Help Desk
Feedback:  0   0