universal-design-center

SurveyMonkey and SurveyGizmo Accessibility

The page below summarizes accessibility findings identified through a brief assessment of SurveyMonkey and SurveyGizmo. If you are purchasing SurveyMonkey or SurveyGizmo at CSUN, it is your responsibility to review these findings and ensure the surveys distributed by your respective area comply with accessibility guidelines. 

 Known Accessibility Problems

The problems identified in this section are known accessibility concerns as reported by SurveyMonkey and SurveyGizmo. These problems will require alternative solutions and/or workarounds. For more information about these issues go to SurveyMonkey's 508 Compliance page and SurveyGizmo's Accessibility Compliance page.  



  Accessibility Best Practices for Survey Creator

Because most elements in SurveyMonkey and SurveyGizmo are under the control of survey creators, it is imperative that survey creators follow accessibility best practices when developing a survey. Both SurveyMonkey and SurveyGizmo provide resources to guide survey creators in developing the most accessible survey. Failure to follow these practices will result in access barriers for survey takers with disabilities.

Survey Questions

Question Types

  • Avoid using question types that may not be accessible for survey takers with disabilities.
  • Always make sure questions with input fields are resizable.  For more information, visit SurveyGizmo: Resizing Text Fields.
  • Avoid using videos and images as part of a question. These questions may not be inclusive for survey takers with sight disabilities. Videos may also cause problems for survey takers who are deaf or hard of hearing if the video is missing captions. 
  • To ensure users with visual disabilities have full understanding of a grid question, a table summary is required.
  • If a question is required, always make sure the required question has an asterisk next to it. Do not use color only to differentiate required questions from other question types.

Language

Design

Structure

  • Always add headings to your survey as they help organize information and allow survey takers using screen reader technology to better navigate a survey.  
  • When emphasizing text, use the appropriate program features to bold, underline or italicize text instead of capitalizing text. Cap’s text is not understood by screen reader technology and this can prevent survey takers with disabilities from understanding important information. 
  • A page description is always needed to describe the purpose of the survey. Visit Universal Design Center: Semantic Requirements for more information.

Color

  • Do not use color only to emphasize content
  • Always make sure there is sufficient color contrast between the foreground and background of your survey.

Layout

Mobile View

Time Limits

  • If time limits are present in a survey, a method to extend time limit should be present. Go to SurveyGizmo’s Timer Options for more information.
  • It is recommended to provide a visual countdown or display to let survey takers know how much time remains.
  • Survey takers must be warned beforehand if a survey has a time limit.

Accessibility Validation

Alternative Solutions

Departments must also have a method to let survey-takers know if alternative solutions are available. It is highly recommended to provide a statement near the top of the survey that let as a survey taker know who to contact for assistance and provide links to resources to help them. 

Example:

If you are having problems completing this form due to accessibility-related issues, contact (Department/survey creator contact information). For screen reader assistance visit SurveyMonkey’s taking a Survey with a Screen Reader.  

In addition, departments must establish alternative solutions to use if survey-takers have problems completing a survey due to accessibility barriers.  

Examples of alternative solutions for a survey include: 

  • RSVP Surveys: Provide a survey-taker another method to RSVP instead of a survey. For example, allow a survey-taker to call or email the department as an alternative.  If a survey is used to RSVP to an event, allowing users to RSVP via phone or email would be an effective alternative. 
  • Research & Climate Surveys: An alternative survey format can be made available to survey-takers who need it. Alternative formats could be a paper survey, PDF or other accessible electronic documents.
  • Classroom Polls: If a survey is used for classroom polls or instruction, an alternative method to participate in class assignments should be considered such as an alternative device or program a survey taker can use instead.

Purchasing SurveyMonkey or SurveyGizmo?

If your department is purchasing SurveyMonkey or SurveyGizmo you are required to review and sign a Plan for Alternate Access. Ultimately your department is responsible for ensuring accessibility compliance in the surveys produced through SurveyMonkey or SurveyGizmo. It is your responsibility to review the findings listed in this plan and ensure the surveys distributed by your respective area comply with accessibility guidelines.

Should you require assistance in understanding the steps needed to ensure the accessibility requirements for these products are met, you can contact the Universal Design Center at (818) 677-5898 or via email through .
https://www.csun.edu/universal-design-center/SM-SG-Accessibility
www.csun.edu
crawl=CC-MAIN-2020-16
79257
application/http; msgtype=response
sha1:ZQDYOXVRDGUX7JIFTIMESHQEOF37O2C6
<urn:uuid:5a00005c-7742-4e41-9982-2a785fa0a081>
2020-04-06T14:10:27Z
130.166.238.195
text/html
sha1:C7VZH34RNJG2DBPATWZSWZUB244N5TO7
<urn:uuid:c043a0af-9115-4f4a-9666-5f90b121cd71>
https://www.csun.edu/universal-design-center/SM-SG-Accessibility
response
<urn:uuid:e4377484-ace5-48c3-9b42-26a45b744706>
isPartOf: CC-MAIN-2020-16
publisher: Common Crawl
description: Wide crawl of the web for March/April 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-210.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/