Home

Cvent

Localist is able to use Cvent API to automatically import data from your organization’s Cvent account. Localist’s communication with Cvent is only Cvent -> Localist.

What is imported?

Localist Field Cvent Field – Series = No Cvent Field – Series = Yes
Title Event Title Session Title
    if Event Status = “Cancelled” “Cancelled” + Event Title “Cancelled” + Session Title
Description Event Description Session Description
Date From Event Start Date Session Start Date
Date To Event End Date Session End Date
Start Time (one day event) Event Start Time blank
Start Time (multi-day event) blank Session Start Time
End Time (one day event) Event End Time blank
End Time (multi-day event) blank Session End Time
Location Location Location
Address Address 1 Address
City City City
State State State
Event Website Event Website URL Event Website URL
Room Address 3 Room Number
Photo URL Photo URL* Photo URL*
Ticket URL Event Webpage URL Event Webpage URL
Department Department Department
Event Types Category Category
External ID Event Code Event Code + Session Start Date (MMDDYYY)
Attendance Options Attendance Options* Attendance Options*

*custom field in Cvent

Custom Fields in Cvent

Any custom fields in Cvent must match the field names exactly as they appear here for the integration to work properly.

  • Photo URL — this must be a direct URL to the image added by your user in Cvent for it to properly import into Localist. The link must be to the photo itself not a page displaying the image. 
  • Attendance Options — these will be added as Filters in Localist and what is entered in Cvent must match the Filter in Localist exactly.

How is data updated?

Feed Data Takes Precedent

1. Data imported by a feed into Localist will always take precedent over data that has been added or updated in the Localist event. Only the following 3 details can be locked and cut off from further updating:

  • Name
  • Description
  • Location

2. All other details that are brought in via a feed must be changed at the feed source. If it is changed in Localist then the changes will only stick until the next feed import, at which time it will revert back to the data in the feed.

  • Exception:  If a piece of data is not provided by the feed then any changes or additions in Localist will stick even after the next import. For example, if the feed only provides name/date/time/description/place then anything else, such as a Tag or custom field, will remain as updated in Localist.

3. If fields in a feed match fields in Localist then the data must match exactly to what is saved in Localist. It is not possible to assign aliases or alternative spellings. For example, place names must match the Place Pages and filters must match your platform’s already existing classification in order to assign properly.

 

Deleting a Feed Event

1. Deleted in Localist:  If an event has been imported to the calendar then deleted, it will reappear if it is sent back over through the feed. Since feed data takes precedent, if the event is present in the feed then it will be re-added to Localist.

  • Exception:  If an event is rejected from the pending queue then it will not re-appear. If the event is deleted while still in the pending queue then it will be re-imported into the queue.

2. Deleted at the feed source:  If an event is removed from the feed source, the event in Localist will not be removed. This is because it is impossible for Localist to determine wether the event has been deleted/cancelled or if the event is just not present in the feed. In this case you will need to delete the instance in the feed and in Localist.

When does the feed import?

All feeds are imported once every 24 hours, overnight. This schedule cannot be changed on a per-feed or per-platform basis.

How do I set it up?

You need to contact support@localist.com to get this feed set up, it is not available from the feed dropdown options. When you email support, you need to include:

  1. Cvent Account
  2. User
  3. Password 

Customer Spotlight

Houston Methodist Events Calendar

SimpleView

Localist is able to connect with SimpleView to automatically import data from your organization’s SimpleView account. Localist’s communication with SimpleView is only SimpleView -> Localist.

What is imported?

The SimpleView integration provides the following fields that match fields in Localist.

Localist Field SimpleView Field
Title Title
Description Description
Start Date Event Date
End Date last Event Date in list
Start Time Start Time
End Time End Time
Location Location
Address Address
City City
State State
Event Types Event Category
Regions Locations*
Contact Contact
Contact Email Email
Event Website Website
Photo URL Photo URL*
Ticket URL Ticket URL*
Cost Admission
Featured Tabs Featured
External ID Event ID

*custom field in SimpleView and must match exactly to import correctly into Localist

 

Custom Fields in SimpleView

Any custom fields in SimpleView must match the field names exactly as they appear here for the integration to work properly.

  • Regions — these will be added as Filters in Localist and what is entered in SimpleView must match the Filter in Localist exactly.
  • Photo URL — this must be a direct URL to the image added by your user in SimpleView for it to properly import into Localist. The link must be to the photo itself not a page displaying the image. 
  • Ticket URL — this will populate Localist’s standard Ticket URL field and trigger a Buy Tickets button on the events landing page.

How is data updated?

Feed Data Takes Precedent

1. Data imported by a feed into Localist will always take precedent over data that has been added or updated in the Localist event. Only the following 3 details can be locked and cut off from further updating:

  • Name
  • Description
  • Location

2. All other details that are brought in via a feed must be changed at the feed source. If it is changed in Localist then the changes will only stick until the next feed import, at which time it will revert back to the data in the feed.

  • Exception:  If a piece of data is not provided by the feed then any changes or additions in Localist will stick even after the next import. For example, if the feed only provides name/date/time/description/place then anything else, such as a Tag or custom field, will remain as updated in Localist.

3. If fields in a feed match fields in Localist then the data must match exactly to what is saved in Localist. It is not possible to assign aliases or alternative spellings. For example, place names must match the Place Pages and Filters must match your platform’s already existing classification in order to assign properly.

 

Deleting a Feed Event

1. Deleted in Localist:  If an event has been imported to the calendar then deleted, it will reappear if it is sent back over through the feed. Since feed data takes precedent, if the event is present in the feed then it will be re-added to Localist.

  • Exception:  If an event is rejected from the pending queue then it will not re-appear. If the event is deleted while still in the pending queue then it will be re-imported into the queue.

2. Deleted at the feed source:  If an event is removed from the feed source, the event in Localist will not be removed. This is because it is impossible for Localist to determine wether the event has been deleted/cancelled or if the event is just not present in the feed. In this case you will need to delete the instance in the feed and in Localist.

When does the feed import?

All feeds are imported once every 24 hours, overnight. This schedule cannot be changed on a per-feed or per-platform basis.

How do I set it up?

You need to contact support@localist.com to get this feed set up, it is not available from the feed dropdown options. When you email support, you need to include the URL including the API Key for the feed you purchased, similar to the format below:

http://cs.simpleviewnc.com/feeds/events.cfm?apikey=key-goes-here

Customer Spotlight

Discover Long Island

Tags vs. Keywords Transcript

During this Localist Lesson, we’ll be breaking down when and how you should use Tags and Keywords within your Localist platform.

If they sound similar, that’s cause they are! The best way to define Tags & Keywords it to first start by defining another piece of Localist classifications–your Filters. These are the links prominently and permanently displayed in your platform’s sidebar. As such, they should be broad, user-centric and used consistently throughout the year. This would be categories such as Fundraiser, Family-Friendly or Workshop. So, what do you do when you need ultra-specific or temporary categorization? Enter Tags & Keywords. Let’s start with how they compare functionally.
Tags & Keywords are both free-text labels that are assigned to events. Functionally they’re the same, however Tags are publicly displayed on the event details page. In comparison, Keywords are hidden from the public and only seen by search engines.While both are indexed by Localist and search engines, Keywords can be used for things like common misspellings. If you enter the misspelling as a keyword then user’s searching with that spelling will still discover your events.

As for adding Tags & Keywords, this is only available to Event Admins. Event Admins can add Tags & Keywords to their own events or any events they are allowed to edit. Additionally, a Platform Admin can also include Tags & Keywords in both a Bulk CSV upload or in a CSV feed.Since Tags & Keywords are free-text, they are not available in the event submission form. This ensures your organization isn’t overrun with slightly different variations of the same Tag or Keyword.

That said, when an admin starts typing, Localist will suggest already existing Tags or already used Keywords. These suggestions will also display how many events are currently assigned, but you can also refine event results in admin according to a Tag or Keyword. When entering Tags & Keywords, be sure to hit enter after each one to ensure they are saved with the event.

Once Tags & Keywords are saved in an event, they can be used in two ways. First, is basic end user browsing. Clicking on a Tag from the event details page will take users to the search results for all events assigned to that Tag. Just like when clicking a filter, they’ll see all events assigned to that Tag as well as links to subscribe to the results.
Second, is admin curation. This would be for when you want to pull short-term or ultra-specific events into a Channel or Widget. For Tags, these would be things like festivals, conferences, holidays or traditions.Keywords come into play with curation when you need to add specific information that you wouldn’t necessarily want your Users to see, such as indicating the event belongs on your Partner’s widget with the Keyword PartnerWidget. This way you can as specific as you need without worrying about users stumbling across internal details.

So, to recap, Tags & Keywords are only different in the way that they display, with Tags being displayed publicly on the event landing pages and Keywords being hidden from view. Other than that, they are both used…
– As Free text fields only available to Event Admins
– Both are indexed to be used in internal and external searches
– And both are meant for ultra specific or temporary categorization needs for end user browsing or admin curation
Finally, here’s a few examples of how Tags & Keywords work together and with your filters. As you can see, the classification gets more specific from left to right.

For example, “Holidays & Celebrations” is a filter that encompasses happenings throughout the year, while the tag Halloween is only relevant for one month and the keyword ScreamFest2018 can be used to collect specific events in a Channel or Widget.

You can read through our Classifications Best Practice guide at support.localist.com/intro-to-classification. If you have any questions, you can connect directly with the Localist Team by emailing support@localist.com.

The Classroom

Localist Lessons

Quick Takes

Not quite sure what tool is best for your needs? In these Quick Takes, we’re putting some of Localist’s most popular features head-to-head.

 

How-To’s

If you’re new to coding, these simple step-by-step videos will have you implementing customizations like a seasoned pro.

 

Webinars

Making the Most of Your Event Content Series

This 3-part series will focus on industry best practices to refocus your event content strategy and kick your Localist platform up a few (or several) notches.

 

Other Topics

Release Notes (6/28/18)

Tags & Keywords: Smart Matching

Assigning Tags & Keywords just got a whole lot easier! Start typing and Localist will suggest already existing Tags or already used Keywords:

 

You can now refine event lists according to Tags & Keywords in your admin dashboard:

 

Default Date Range: Rolling 30-Day

This is a Global Options setting, and it controls what date range is shown when “All Events” or a filter is selected from your calendar homepage. Before this option, it displayed as “This Month” and was a static view that always showed the entire current month, regardless of the date. With this updated option, these pages will show today+30 days worth of events.

 

Admin CSV Exports

Admins can now exports full CSV’s of events, Places, Groups and Departments. Once you’ve selected the desired link in the left nav, you will find the CSV export button in the top right corner:

If you are exporting events, you can first choose to refine the list then export so the CSV only includes specific events.

 

Widgets: Call-to-Action

A small, but powerful addition! The default “Classic” and “Modern” templates now include a “View all events” call-to-action at the end of the event listings.

 

Filters to Landing Pages Conversion

Want to take advantage of all of the benefits landing pages have over filters? This is the tool for you!

What will automatically update?

  • Events and user permissions tied to the original filter will carry over to the landing page.
  • All widgets, feeds and API calls using the original filter will now reference the landing page moving forward.
  • Once converted, the original filter will be permanently deleted.

What will not automatically update?

  • Since filters are just a word/phrase, the landing page will be created with that as the title. All additional details such as the description and photo will need to be manually added. TIP: you can use our new CSV export tool to export your landing pages, edit the CSV and re-upload to easily update all landing pages at once.

 

WCAG 2.0 Compliance

L1

Compliant Description
 Yes  1.1.1 For all non-text content, one of the following is true: [How to meet 1.1.1] If non-text content presents information or responds to user input, text alternatives serve the same purpose and present the same information as the non-text content. If text alternatives cannot serve the same purpose, then text alternatives at least identify the purpose of the non-text content. If non-text content is multimedia; live audio-only or live video-only content; a test or exercise that must use a particular sense; or primarily intended to create a specific sensory experience; then text alternatives at least identify the non-text content with a descriptive text label. (For multimedia, see also Guideline 1.2 Provide synchronized alternatives for multimedia .) If the purpose of non-text content is to confirm that content is being operated by a person rather than a computer, different forms are provided to accommodate multiple disabilities. If non-text content is pure decoration, or used only for visual formatting, or if it is not presented to users, it is implemented such that it can be ignored by assistive technology.
  Yes  1.2.1 Captions are provided for prerecorded multimedia. [How to meet 1.2.1]
  Yes  1.2.2 Audio descriptions of video, or a full multimedia text alternative including any interaction, are provided for prerecorded multimedia. [How to meet 1.2.2]
  Yes  1.3.1 Information and relationships conveyed through presentation can be programmatically determined, and notification of changes to these is available to user agents, including assistive technologies. [How to meet 1.3.1]
  Yes  1.3.2 Any information that is conveyed by color is also visually evident without color. [How to meet 1.3.2]
  Yes  1.3.3 When the sequence of the content affects its meaning, that sequence can be programmatically determined. [How to meet 1.3.3]
  Yes  2.1.1 All functionality of the content is operable in a non-time-dependent manner through a keyboard interface, except where the task requires analog, time-dependent input. [How to meet 2.1.1] Note: This does not preclude and should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation.
  Yes  2.2.1 For each time-out that is a function of the content, at least one of the following is true: [How to meet 2.2.1] the user is allowed to deactivate the time-out; or the user is allowed to adjust the time-out over a wide range that is at least ten times the length of the default setting; or the user is warned before time expires and given at least 20 seconds to extend the time-out with a simple action (for example, “hit any key”), and the user is allowed to extend the timeout at least ten times; or the time-out is an important part of a real-time event (for example, an auction), and no alternative to the time-out is possible; or the time-out is part of an activity where timing is essential (for example, competitive gaming or time-based testing) and time limits can not be extended further without invalidating the activity.
  Yes  2.3.1 Content does not violate the general flash threshold or the red flash threshold. [How to meet 2.3.1]
  Yes  2.4.1 A mechanism is available to bypass blocks of content that are repeated on multiple Web units. [How to meet 2.4.1]
  Yes  2.5.1 If an input error is detected, the error is identified and described to the user in text. [How to meet 2.5.1]
  Yes  3.1.1 The primary natural language or languages of the Web unit can be programmatically determined. [How to meet 3.1.1]
  Yes  3.2.1 When any component receives focus, it does not cause a change of context. [How to meet 3.2.1]
  Yes  3.2.2 Changing the setting of any form control or field does not automatically cause a change of context (beyond moving to the next field in tab order), unless the authored unit contains instructions before the control that describe the behavior. [How to meet 3.2.2]
  Yes  4.1.1 Web units or authored components can be parsed unambiguously, and the relationships in the resulting data structure are also unambiguous. [How to meet 4.1.1]
  Yes  4.1.2 For all user interface components, the name and role can be programmatically determined, values that can be set by the user can be programmatically set, and notification of changes to these items is available to user agents, including assistive technologies. [How to meet 4.1.2]
  Yes  4.2.1 At least one version of the content meets all level 1 success criteria, but alternate version(s) that do not meet all level 1 success criteria may be available from the same URI. [How to meet 4.2.1]
  Yes  4.2.2 Content meets the following criteria even if the content uses a technology that is not in the chosen baseline: [How to meet 4.2.2] If content can be entered using the keyboard, then the content can be exited using the keyboard. Content conforms to success criterion 2.3.1 (general and red flash).

L2

Compliant Description
   Yes  1.2.3 Audio descriptions of video are provided for prerecorded multimedia. [How to meet 1.2.3]
   Yes  1.2.4 Captions are provided for live multimedia. [How to meet 1.2.4]
   Yes  1.3.4 Information that is conveyed by variations in presentation of text is also conveyed in text, or the variations in presentation of text can be programmatically determined. [How to meet 1.3.4]
   Yes  1.3.5 Information required to understand and operate content does not rely on shape, size, visual location, or orientation of components. [How to meet 1.3.5]
   Yes  1.4.1 Text or diagrams, and their background, have a luminosity contrast ratio of at least 5:1. [How to meet 1.4.1]
   Yes  1.4.2 A mechanism is available to turn off background audio that plays automatically, without requiring the user to turn off all audio. [How to meet 1.4.2]
   Yes  2.2.2 Content does not blink for more than three seconds, or a method is available to stop all blinking content in the Web unit or authored component. [How to meet 2.2.2] Note: For requirements related to flickering or flashing content, refer to Guideline 2.3 Allow users to avoid content that could cause seizures due to photosensitivity .
   Yes  2.2.3 Content can be paused by the user unless the timing or movement is part of an activity where timing or movement is essential. [How to meet 2.2.3]
   Yes  2.4.2 More than one way is available to locate content within a set of Web units where content is not the result of, or a step in, a process or task. [How to meet 2.4.2]
   Yes  2.4.3 Web units have titles. [How to meet 2.4.3]
   Yes  2.4.4 Each link is programmatically associated with text from which its purpose can be determined. [How to meet 2.4.4]
   Yes  2.5.2 If an input error is detected and suggestions for correction are known and can be provided without jeopardizing the security or purpose of the content, the suggestions are provided to the user. [How to meet 2.5.2]
   Yes  2.5.3 For forms that cause legal or financial transactions to occur, that modify or delete data in data storage systems, or that submit test responses, at least one of the following is true: [How to meet 2.5.3] Actions are reversible. Actions are checked for input errors before going on to the next step in the process. The user is able to review and confirm or correct information before submitting it.
   Yes  3.1.2 The natural language of each passage or phrase in the Web unit can be programmatically determined. [How to meet 3.1.2] Note: This requirement does not apply to individual words or phrases that have become part of the primary language of the content.
   Yes  3.2.3 Navigational mechanisms that are repeated on multiple Web units within a set of Web units or other primary resources occur in the same relative order each time they are repeated, unless a change is initiated by the user. [How to meet 3.2.3]
   Yes  3.2.4 Components that have the same functionality within a set of Web units are identified consistently. [How to meet 3.2.4]
   Yes  4.2.3 At least one version of the content meets all level 2 success criteria, but alternate version(s) that do not meet all level 2 success criteria may be available from the same URI. [How to meet 4.2.3]

L3

Compliant Description
    Yes  1.2.5 Sign language interpretation is provided for multimedia. [How to meet 1.2.5]
    Yes  1.2.6 Extended audio descriptions of video are provided for prerecorded multimedia. [How to meet 1.2.6]
    Yes  1.2.7 For prerecorded multimedia, a full multimedia text alternative including any interaction is provided. [How to meet 1.2.7]
    Yes  1.4.3 Text or diagrams, and their background, have a luminosity contrast ratio of at least 10:1. [How to meet 1.4.3]
    Yes  1.4.4 Audio content does not contain background sounds, background sounds can be turned off, or background sounds are at least 20 decibels lower than the foreground audio content, with the exception of occasional sound effects. [How to meet 1.4.4] Note: A 20 decibel difference in sound level is roughly four times (4x) quieter or louder. Background sound that meets this requirement will be approximately four times (4x) quieter than the foreground audio content.
    Yes  2.1.2 All functionality of the content is operable in a non-time-dependent manner through a keyboard interface. [How to meet 2.1.2]
    Yes  2.2.4 Except for real-time events, timing is not an essential part of the event or activity presented by the content. [How to meet 2.2.4]
    Yes  2.2.5 Interruptions, such as updated content, can be postponed or suppressed by the user, except interruptions involving an emergency. [How to meet 2.2.5]
    Yes  2.2.6 When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. [How to meet 2.2.6]
    Yes  2.3.2 Web units do not contain any components that flash more than three times in any 1-second period. [How to meet 2.3.2]
    Yes  2.4.5 Titles, headings, and labels are descriptive. [How to meet 2.4.5]
    Yes  2.4.6 When a Web unit or authored component is navigated sequentially, components receive focus in an order that follows relationships and sequences in the content. [How to meet 2.4.6]
    Yes  2.4.7 Information about the user’s location within a set of Web units is available. [How to meet 2.4.7]
    Yes  2.4.8 The purpose of each link can be programmatically determined from the link. [How to meet 2.4.8]
    Yes  2.5.4 Context-sensitive help is available for text input. [How to meet 2.5.4]
    Yes  3.1.3 A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. [How to meet 3.1.3]
    Yes 3.1.4 A mechanism for finding the expanded form of abbreviations is available. [How to meet 3.1.4]
    Yes  3.1.5 When text requires reading ability more advanced than the lower secondary education level, supplemental content is available that does not require reading ability more advanced than the lower secondary education level. [How to meet 3.1.5]
    Yes  3.1.6 A mechanism is available for identifying specific pronunciation of words where meaning cannot be determined without pronunciation. [How to meet 3.1.6]
    Yes  3.2.5 Changes of context are initiated only by user request. [How to meet 3.2.5]
    Yes 4.2.4 Content implemented using technologies outside of the chosen baseline satisfies all Level 1 and Level 2 requirements supported by the technologies. [How to meet 4.2.4]

Resource Links

Technical

VPAT: https://support.localist.com/vpat/

508 Compliance: https://support.localist.com/508-compliance/

WCAG 2.0 (Accessibility): https://support.localist.com/wcag-2/

Support

Scope of Services: https://support.localist.com/services/

Support Bold: https://support.localist.com/bold/

Coming Soon

  • Implementation Guide

Voluntary Product Accessibility Template®

Version 1.6

The purpose of the Voluntary Product Accessibility Template, or VPAT, is to assist Federal contracting officials and other buyers in making preliminary assessments regarding the availability of commercial “Electronic and Information Technology” products and services with features that support accessibility.  It is assumed and recommended that offerers will provide additional contact information to facilitate more detailed inquiries.

The first table of the Template provides a summary view of the Section 508 Standards.  The subsequent tables provide more detailed views of each subsection. There are three columns in each table.  Column one of the Summary Table describes the subsections of subparts B and C of the Standards. The second column describes the supporting features of the product or refers you to the corresponding detailed table, e.g., “equivalent facilitation.”  The third column contains any additional remarks and explanations regarding the product. In the subsequent tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product with regard to that paragraph.  The third column contains any additional remarks and explanations regarding the product.

 

Date: 02/20/2018

Name of Product: Localist Calendar

Contact for more Information (name/phone/email): Mykel Nahorniak, 703-626-1528, myke@localist.com

 

Summary Table

VPAT™

Voluntary Product Accessibility Template®

 

Criteria Supporting Features Remarks and explanations
 Section 1194.21 Software Applications and Operating Systems  N/A
 Section 1194.22 Web-based Internet Information and Applications
 Section 1194.23 Telecommunications Products  N/A
 Section 1194.24 Video and Multi-media Products  N/A
 Section 1194.25 Self-Contained, Closed Products  N/A
 Section 1194.26 Desktop and Portable Computers  N/A
 Section 1194.31 Functional Performance Criteria  Supported
 Section 1194.41 Information, Documentation and Support  Supported

 

Section 1194.22 Web-based intranet and Internet information and applications- Detail™

Voluntary Product Accessibility Template®

 

Criteria Supporting Features Remarks and explanations
 (a) A text equivalent for every non-text element shall be provided (e.g., via “alt”, “longdesc”, or in element content).  All
 (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.  N/A
 (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.  All
 (d) Documents shall be organized so they are readable without requiring an associated style sheet.  All
 (e) Redundant text links shall be provided for each active region of a server-side image map.  N/A
 (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.  N/A
 (g) Row and column headers shall be identified for data tables.  All
 (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.  All
 (i) Frames shall be titled with text that facilitates frame identification and navigation  All
 (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.  All
 (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text- only page shall be updated whenever the primary page changes.  N/A
 (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology.  All
 (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with 1194.21(a) through (l).  N/A
 (n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.  All
 (o) A method shall be provided that permits users to skip repetitive navigation links.  All
 (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.  All

 

Section 1194.31 Functional Performance Criteria – Detail

VPAT

Voluntary Product Accessibility Template®

 

Criteria Supporting Features Remarks and explanations
 (a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided.  All
 (b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided. All
 (c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided  All
 (d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.  N/A  Audio information is not important for the use of Localist.
 (e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided.  All
 (f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.  All

 

Section 1194.41 Information, Documentation and Support – Detail

VPAT

Voluntary Product Accessibility Template®

 

Criteria Supporting Features Remarks and explanations
 (a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge  Yes  Formats not included in “no additional charge:” video.
 (b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge.  All
 (c) Support services for products shall accommodate the communication needs of end-users with disabilities.  All

508 Compliance

Standard Rank

 

A text equivalent for every non-text element is provided (e.g., ALT tags on images, etc.) Pass

 

Equivalent alternatives for any multimedia presentation are synchronized with the presentation. Pass

 

Web pages are designed so that all information conveyed with color is also available without color, for example from context or markup. Pass

 

Documents are organized so they are readable without requiring an associated style sheet. Pass

 

Redundant text links are provided for each active region of a server-side image map. N/A

 

Client-side image maps are provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. N/A

 

Row and column headers are identified for data tables. Pass

 

Markup are used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Pass

 

Frames are titled with text that facilitates frame identification and navigation. N/A

 

Pages are designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Pass

 

When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script are identified with functional text that can be read by assistive technology. Pass

 

When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet. N/A

 

When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information,field elements, and functionality required for completion and submission of the form, including all directions and cues. Pass

 

A method are provided that permits users to skip repetitive navigation links. Pass

 

When a timed response is required,the user are alerted and given sufficient time to indicate more time is required. N/A

Localist API

For terms of use, concepts and resources, Localist’s master API documentation can be found here: http://www.localist.com/doc/api

Basic Rules

  • Localist’s API is read-only and publicly accessible.
  • Calls will pull 10 items per page by default, but can be increased to up to 100 per page (this is well-above industry standard).
  • The maximum date range that the API call pull from is 370 days from today or the start date you specify.
  • If a start date is not specified, then the API will default to only pulling event data from today.

Building an API Call

All API calls must start with http://your.custom.domain/api/2/

Events: http://your.custom.domain/api/2/events
Places: http://your.custom.domain/api/2/places
Groups: http:/your.custom.domain/api/2/groups
Paging: http://your.custom.domain/api/2/events?type=38570&pp=100&page=1

  • This will pull 100 results per page so to access the next 100 you would change the 1 in page=1 to 2, etc.

Date Range

  • Start and End date: http://your.custom.domain/api/2/events?type=38570&pp=100&page=1& start=2014-10-01&end=2014-11-01
  • Today + number of future days: http://your.custom.domain/api/2/events?days=90 (the maximum is 370 days).

Exporting to a CSV

1. Build an API call.

  • To pull a list of events you would use: http://yourcustomdomain/api/2/events?start=2014-09-01&end=2014-09-30&pp=100&page=1
  • This will pull 100 results per page so to access the next 100 you would change the1 in page=1to 2, etc.
  • Note: Events can be pulled from the start date + 370 days at a time.

2. Enter the API call in your search bar and you will see the data populate.

3. Open http://konklone.io/json/ in another tab.

4. Copy and paste all data that is on the API results page and paste that information in the first box on http://konklone.io/json/.

5. Once pasted, the information will be added to the second box in a table format.

6. Select Download the entire CSV and in this CSV you will have all available data for the first 100 events.