Voluntary Product Accessibility Template (VPAT)

Date: August 8, 2019

Name of Product: Siteimprove Intelligence Platform

Website: https://siteimprove.com

Scoping Requirements

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Success Criteria, Level A

Criteria Supporting Feature Notes

1.1.1 Non-text Content

Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except in situations listed in WCAG 2.0 1.1.1.
Partially Supports
  • Some graphs and diagrams do not have sufficient alternative text for the data shown
  • Trend arrows are missing alternative text

1.2.1 Audio-only and Video-only (Prerecorded)

For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:

  • Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.

Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.

Not Applicable  

1.2.2 Captions (Prerecorded)

Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

Not Applicable  

1.2.3 Audio Description or Media Alternative (Prerecorded)

An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

Not Applicable  

1.3.1 Info and Relationships

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Partially Supports
  • Help and Export options do not visually convey that they are tabs
  • Reset CAPTCHA feature is not accessible
  • Dashboard Picker does not convey its expanded state
  • Instructions for the widget library
  • Interactive components in the "Edit Readability Test" dialog does not convey proper semantic roles to screen-readers
  • Cookie Banner needs better semantics for screen-readers
  • Search Preferences and the "Last 12 months" visualization need improved compatibility with screen-readers
  • Google Maps iframes need descriptions
  • Analytics Live feature tooltip is not conveyed to screen-reader

1.3.2 Meaningful Sequence

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
Partially Supports
  • Site Picker "pin" button has two tab-stops
  • Instructions for the widget library and general use of Dashboards need improvements
  • Dashboard Picker has invisible table columns

1.3.3 Sensory Characteristics

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.
Supports  

1.4.1 Use of Color

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Partially Supports
  • Some links are identified only by color

1.4.2 Audio Control

If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
Not Applicable  

2.1.1 Keyboard

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
Partially Supports
  • "Include sub-table" export option is not keyboard accessible
  • Some tooltips are not keyboard accessible
  • Dashboard Widgets cannot be rearranged using keyboard only
  • Page Report: HTML View is not optimized for screen-reader use
  • "Edit Readability Test" is not keyboard accessible
  • Heat Map table links are not focusable
  • Create Campaign page does not support keyboard input of dates
  • Some tooltips contain links
  • Policy Page Report: Settings and Notes button are not keyboard accessible
  • Link sorting in “My policies” is not keyboard accessible
  • Map Chart and search panel in Data Privacy are not keyboard accessible
  • Share Widget "Add from group" modal is not keyboard accessible
  • My History, Site Overview, Analytics, and DCI Score within the CMS Plugin are not keyboard accessible
  • Cards expand/collapse functionality within the CMS Plugin is not keyboard accessible

2.1.2 No Keyboard Trap

If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
Supports  

2.1.4 Character Key Shortcuts

If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:

  • Turn off: A mechanism is available to turn the shortcut off;
  • Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc.);
  • Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.
Not Applicable

 

2.2.1 Timing Adjustable

For each time limit that is set by the content, at least one of the instances in WCAG 2.0 2.2.1 is true.
Not Applicable

 

2.2.2 Pause, Stop, Hide

For moving, blinking, scrolling, or auto-updating information, all of the following are true:

  • Moving, blinking, scrolling:For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and

Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

Not Applicable  

2.3.1 Three Flashes or Below Threshold

Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.
Supports

 

2.4.1 Bypass Blocks

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
Supports  

2.4.2 Page Titled

Web pages have titles that describe topic or purpose.
Supports  

2.4.3 Focus Order

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.

Partially Supports
  • Site and Group selectors, Time and Period selector and Analytics filter selector have illogical focus order

2.4.4 Link Purpose (In Context)

The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.
Partially Supports
  • Budget Analysis and Data Explorer pages in Ads have image links missing alternative text
2.5.1 Pointer Gestures
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
Not Applicable  

2.5.2 Pointer Cancellation

For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
Essential: Completing the function on the down-event is essential.
Not Applicable  

2.5.3 Label in Name

For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
Not Applicable

 

2.5.4 Motion Actuation

Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:

  • Supported Interface: The motion is used to operate functionality through an accessibility supported interface;
Essential: The motion is essential for the function and doing so would invalidate the activity.
Not Applicable  

3.1.1 Language of Page

The default human language of each Web page can be programmatically determined.
Supports  

3.2.1 On Focus

When any component receives focus, it does not initiate a change of context.
Partially Supports
  • Tooltips within the Page Report Misspellings menu are invoked when focused

3.2.2 On Input

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
Partially Supports
  • Table "Page Size" dropdown submits when user presses Esc

3.3.1 Error Identification

If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.
Not Applicable  

3.3.2 Labels or Instructions

Labels or instructions are provided when content requires user input.
Partially Supports
  • Linked Account dialog checkboxes need labels
  • Some inputs are missing labels within the CMS Plugin

4.1.1 Parsing

In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.
Supports  

4.1.2 Name, Role, Value

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and 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.
Partially Supports
  • Full-screen mode needs instructions for exiting
  • Some Iframes in Analytics are missing accessible names
  • Search notification is not announced by screen-reader within Top Ranking Pages

Success Criteria, Level AA

Criteria Supporting Feature Notes

1.2.4 Captions (Live)

Captions are provided for all live audio content in synchronized media.

Not Applicable

 

1.2.5 Audio Description (Prerecorded)

Audio description is provided for all prerecorded video content in synchronized media.

Not Applicable  

1.3.4 Orientation

Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
Not Applicable  

1.3.5 Identify Input Purpose

The purpose of each input field collecting information about the user can be programmatically determined when:

  • The input field serves a purpose identified in the Input Purposes for User Interface Components section; and
The content is implemented using technologies with support for identifying the expected meaning for form input data.
Not Applicable  

1.4.3 Contrast (Minimum)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:

  • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
  • Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
Logotypes: Text that is part of a logo or brand name has no contrast requirement.
Partially Supports
  • Input field placeholders have insufficient color contrast
  • Create Activity Plan feature has insufficient color contrast
  • Feedback feature has insufficient color contrast
  • Status Tags, Landing Page Optimization page, and Connect to Analytics dialog have insufficient color contrast

1.4.4 Resize text

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
Partially Supports
  • Information in the Guides and FAQs fly-out tutorials becomes obscured off-screen when zoomed in to 125% or higher
  • Feedback feature hides text behind buttons when zoomed to 200%

1.4.5 Images of Text

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following:

  • Customizable: The image of text can be visually customized to the user's requirements;
Essential: A particular presentation of text is essential to the information being conveyed.
Not Applicable  

1.4.10 Reflow

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:

  • Vertical scrolling content at a width equivalent to 320 CSS pixels;
  • Horizontal scrolling content at a height equivalent to 256 CSS pixels.
Except for parts of the content which require two-dimensional layout for usage or meaning.
Not Applicable  

1.4.11 Non-text Contrast

The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):

  • User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
Partially Supports
  • Some icons disappear in High Contrast Mode

1.4.12 Text Spacing

In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:

  • Line height (line spacing) to at least 1.5 times the font size;
  • Spacing following paragraphs to at least 2 times the font size;
  • Letter spacing (tracking) to at least 0.12 times the font size;
  • Word spacing to at least 0.16 times the font size.
Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.
Not Applicable  

1.4.13 Content on Hover or Focus

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

  • Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
  • Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
  • Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.
Supports  

2.4.5 Multiple Ways

More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.
Supports  

2.4.6 Headings and Labels

Headings and labels describe topic or purpose.
Partially Supports
  • “Difficulty Level” does not have a label or text alternative within SEO Overview

2.4.7 Focus Visible

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Partially Supports
  • Some interactive components in Ads lack visible focus indicators

3.1.2 Language of Parts

The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.
Not Applicable  

3.2.3 Consistent Navigation

Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.
Partially Supports
  • Navigation differs in Policy Page Report compared to Accessibility, SEO and QA

3.2.4 Consistent Identification

Components that have the same functionality within a set of Web pages are identified consistently.
Supports  

3.3.3 Error Suggestion

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.
Not Applicable  

3.3.4 Error Prevention (Legal, Financial, Data)

For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:

  • Reversible: Submissions are reversible.
  • Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Not Applicable  

4.1.3 Status Messages

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

Partially Supports
  • Notifications are not always properly announced

Success Criteria, Level AAA

Criteria Supporting Feature Notes

1.2.6 Sign Language (Prerecorded)

Sign language interpretation is provided for all prerecorded audio content in synchronized media.

Not Applicable

 

1.2.7 Extended Audio Description (Prerecorded)

Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media.

Not Applicable  
1.2.8 Media Alternative (Prerecorded)
An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.
Not Applicable  

1.2.9 Audio-only (Live)

An alternative for time-based media that presents equivalent information for live audio-only content is provided.

Not Applicable  

1.3.6 Identify Purpose

In content implemented using markup languages, the purpose of User Interface Components, icons, and regions can be programmatically determined.
Not Applicable  

1.4.6 Contrast Enhanced

The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following:

  • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1;
  • Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
Logotypes: Text that is part of a logo or brand name has no contrast requirement.
Not Applicable  

1.4.7 Low or No Background Audio

For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true:

  • No Background: The audio does not contain background sounds.
  • Turn Off: The background sounds can be turned off.
20 dB: The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds.
Not Applicable  

1.4.8 Visual Presentation

For the visual presentation of blocks of text, a mechanism is available to achieve the following:

  • Foreground and background colors can be selected by the user.
  • Width is no more than 80 characters or glyphs (40 if CJK).
  • Text is not justified (aligned to both the left and the right margins).
  • Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.
Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.
Not Applicable  

1.4.9 Images of Text (No Exception) Control

Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.

Not Applicable  

2.1.3 Keyboard (No Exception)

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Not Applicable  

2.2.3 No Timing

Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.
Not Applicable  

2.2.4 Interruptions

nterruptions can be postponed or suppressed by the user, except interruptions involving an emergency.
Not Applicable  

2.2.5 Re-authenticating

When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.
Not Applicable  

2.2.6 Timeouts

Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.
Not Applicable  

2.3.2 Three Flashes

Web pages do not contain anything that flashes more than three times in any one second period.
Not Applicable  

2.3.3 Animation from Interactions

Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.
Not Applicable  

2.4.8 Location

Information about the user's location within a set of Web pages is available.
Not Applicable  

2.4.9 Link Purpose (Link Only)

A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.
Not Applicable  

2.4.10 Section Headings

Section headings are used to organize the content.
Not Applicable  

2.5.5 Target Size

The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when:

  • Equivalent: The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;
  • Inline: The target is in a sentence or block of text;
  • User Agent Control: The size of the target is determined by the user agent and is not modified by the author;
Essential: A particular presentation of the target is essential to the information being conveyed.
Not Applicable  

2.5.6 Concurrent Input Mechanisms

Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.
Not Applicable  

3.1.3 Unusual Words

A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
Not Applicable  

3.1.4 Abbreviations

A mechanism for identifying the expanded form or meaning of abbreviations is available.
Not Applicable  

3.1.5 Reading Level

When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.
Not Applicable  

3.1.6 Pronunciation

A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.
Not Applicable  

3.2.5 Change on Request

Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
Not Applicable  

3.3.5 Help

Context-sensitive help is available.
Not Applicable  

3.3.6 Error Prevention (All)

For Web pages that require the user to submit information, at least one of the following is true:

  • Reversible: Submissions are reversible.
  • Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Not Applicable  

Product Accessibility Improvements and Fixes

We know we’re not perfect, but we’re continuously improving the Siteimprove Intelligence Platform so it can one day be fully accessible to everyone. Below you’ll find a regularly updated log of improvements and fixes of known problems.

Month Issues fixed
September 2019
  • Improved contrast for probability/severity icons
August 2019
  • Improved tab-order for Site and Group dropdowns
  • Improved keyboard navigation for Title/URL dropdowns
  • Fixed keyboard navigation on responsibility filter in Accessibility module
  • Fixed semantics on decision widget in Accessibility module
  • Added visible focus to interactive modal elements in Settings module
  • Added proper role to Notification area
  • Added label to progress gauges in Accessibility module
July 2019
  • Exposed Modal close button to screen-readers
  • Added keyboard navigation to filter popover tooltips in Analytics module
  • Added keyboard navigation to misspelling filter dropdown in QA module
  • Added keyboard navigation to search filter dropdowns in SEO module
  • Added keyboard navigation to table tooltips for Page Level data
  • Added text alternative to icons in site picker
  • Added labels to progress-indicating gauges
  • Improved keyboard navigation for search filter dropdowns
  • Improved screen-reader usability for Help and Export tabs
  • Improved screen-reader usability for menu toggle button
  • Improved tab order for Close button in notifications
  • Improved table filter labels
  • Improved focus state color contrast for buttons
  • Improved focus order for search popover
June 2018 – June 2019
  • Fixed all issues regarding empty table columns
  • Fixed all issues with low contrast
  • Fixed issues with keyboard functionality for the Analytics Date Picker and Export Tables
  • Fixed issues with functionality for the Sites and Groups drop-down menus
  • Fixed issues with the Analytics Filters drop-down
  • Fixed issues with focus order for tables, the Site and group selector, Time and period selector and Analytics filter selector
  • Fixed issues with the role and state information for Expandable tables, Export option, Help and Table Data Search and Picker components
May 2018
  • Fixed all instances across the platform of <img> elements with missing alt attributes
  • Fixed all instances across the platform of labels not connected to a form field
  • Reduced form fields with no description from 60 to 15 instances and still work on the remaining
  • Reduced low contrast issues from 106 to 12 instances and still work on the remaining
  • Revised wrong aria states on some buttons in the Accessibility Issues tables
Feb 2018
  • Added navigational landmarks in page reports.
  • Solved issues with how screen readers read the issues lists in page reports.
  • Added labels to numerous input fields across the platform.
  • Fixed numerous contrast issues across the platform.
  • Fixed links only identified by color issues in page reports.
Jan 2018
  • Changed all tab-panel components to follow ARIA-role and keyboard navigation recommendations from WAI-ARIA Authoring Practices.
  • Solved several instances of missing visible keyboard focus.
  • Added label and state to” Add as favorite” buttons in site picker.
  • Added alternative text to severity icons in the Accessibility and SEO modules.
Dec 2017
  • Solved an issue where keyboard and screen reader users could not navigate past the first 200 pages in a result set.
  • Solved an issue where keyboard and screen reader user could not close splash-screens and tutorial windows.
Nov 2017
  • Solved issues with invisible keyboard focus, bad contrast and missing accessible names for buttons in the feedback and share modules.
Oct 2017
  • Improved landmark structure.
  • Released new main navigation with improved semantics and states.