Name of Product: Zingtree Classic
Platform: Web
Date: June 2020
Contact information: info@zingtree.com
Zingtree Accessibility (WCAG)
WCAG 2.1 AA accessibility information for Zingtree.com.
WCAG 2.1 AA Standard
Compliance
Comments
Text Alternatives 1.1.1: Provide alt attributes for meaningful images. An alt attribute is a short description of an image that a screen reader can “read” to the user..
Supported
Images - like screen shots - have Alt tags.
Prerecorded Media. 1.2.1, 1.2.2, 1.2.3, and 1.2.5: Provide transcripts and synchronized captions for all media with audio content. Also provide an audio description for videos with content that is not described in the audio, for example, charts that appear on the screen but are not described in the audio.
Not Applicable
Live-Streamed Media. 1.2.4. Use real-time captioning for all live-streamed media with audio content
Not applicable
Good Code 1.3.1,1.3.2, 2.4.3, and 4.1.1: Use good semantic structure and syntax to enable the user to access all information and navigate the page in a logical manner.
Supported
Consistent headers are on all pages.
Sensory Characteristics 1.3.3: Do not provide instructions that refer solely to visual location or orientation, such as “the blue box on the top left,” or solely use sound, color, or other sensory characteristics.
Supported
Use of Color 1.4.1: Do not rely on color to convey meaning. Color-blind users may have trouble with a website if color is used to convey important information. Required fields should not be indicated only with color.
Supported
Audio Control 1.4.2: Provide a way for users to control audio independent of the computer audio setting. A screen reader user may not be able to hear the screen reader over the audio the application is generating.
Not Applicable
Contrast 1.4.3: Ensure appropriate color contrast so that content can be read by people with visual impairments.
Supported
(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Supported
Resize Text 1.4.4: Define text using em, not pt or px, to ensure it is resizeable.
Supported
Text is resizeable via browser controls
Images of Text 1.4.5: Do not create graphics that look like text, instead use text and style it with CSS.
Supported
Keyboard 2.1.1 and Bypass Blocks 2.4.1: Make sure all website functionality is available via keyboard navigation. Also, provide a means for users to skip over repetitive sections of the site.
Supported
Standard keyboard browser navigation is supported. There are no special keyboard overrides.
No Keyboard Trap 2.1.2: Ensure there are no keyboard traps. This occurs when the user can get to a certain point with the keyboard, but then can’t access the rest of the website.
Not Applicable
No special keyboard support outside of standard browser options
Timing Adjustable 2.2.1: Provide sufficient time for users to respond to timed content and provide users the ability to extend the time if necessary.
Not Applicable
Pause, Stop, Hide 2.2.2: Enable the user to control the movement, blinking, or scrolling of any content.
Supported
Standard scroll bars in use where needed
Flashes 2.3.1: Ensure content and multimedia do not flicker at a rate known to induce seizures among optically sensitive users.
Not Applicable
Page Title 2.4.2: Provide a title for each web page that describes its topic or purpose to ensure the user knows what page they’re on
Supported
All pages have a title (for SEO purposes too!)
Focus Order 2.4.3: If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability
Not Applicable
Link Purpose 2.4.4: Make the purpose of links clear: Use descriptive text for links, and not “click here,” or “read more,” and identify links to PDFs, Word documents, Excel spreadsheets etc.
Supported
Multiple Ways 2.4.5: Provide multiple ways for the user to locate content, such as a navigation bar, search, and site map
Supported
Headings and Labels 2.4.6: Use headings appropriately to convey content hierarchy
Supported
No content hierarchy needed
Visible Focus 2.4.7: Provide a visual indicator of where the cursor is.
Supported
Via standard browser control.
Page Language 3.1.1: Declare the language, using the language tag, that the website is written in. If there are multiple languages on a page, it is crucial to indicate when the language changes and then when it reverts to the original language.
Supported
All pages have lang="en" tag.
Language of Phrases 3.1.2: Use language tags around foreign words so that the screen reader uses the correct speech synthesizer
Not Applicable
On Focus 3.2.1 and On Input 3.2.2: Give the user a choice before changing context, such as when a link will open a new browser window or when to submit a form
Supported
Consistent Navigation 3.2.3 and Consistent Identification 3.2.4: Use consistent navigation and identification cues throughout the site. For example, use the same iconography, text cues, templates, and navigational elements.
Supported
All nav headers come from a single source code file
Error Identification 3.3.1 and Error Suggestion 3.3.3: Provide meaningful error messages that describe the appropriate solution.
Supported
Labels 3.3.2: Associate all form elements with a label tag.
Supported
Via Bootstrap 3
Error Prevention 3.3.4: Provide the user an opportunity to confirm information they have entered for impactful transactions, such as legal and financial transactions. For example, “Do you want to transfer $5000?”Supported
Supported
When deleting content or other critical functions.
Name, Role, Value 4.1.2: Ensure all technologies, including assistive technologies, can determine what an element is and does. Screen reader software must be able to determine, for example, if an element is a menu and if it is expanded or collapsed; or if a magnifying glass icon launches search or zoom functionality.
Supported
All elements use Bootstrap 3