Voluntary Product Accessibility Template (VPAT)

Date: May 30, 2018

Name of Product: Siteimprove Intelligence Platform

Website: https://siteimprove.com

Scoping Requirements

Criteria: WCAG Conformance. User interface components and content of platforms and applications shall conform to Level A and Level AA Success Criteria and Conformance Requirements specified for web pages in WCAG 2.0.

Web Content Accessibility Guidelines (WCAG) 2.0

Principle 1: Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

Guideline 1.1 Text Alternatives

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

Criteria Supporting Feature Notes
1.1.1 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. Supported with Exceptions

Graphs and diagrams

  • We do not in all cases have sufficient alternative text for data shown in graphs and diagrams. When we do have alternative text it is not always clear for AT users how to find the text alternative.

Guideline 1.2 Time-based Media

Provide alternatives for time-based media.

Criteria Supporting Feature Notes

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.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  

Guideline 1.3 Adaptable

Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

Criteria Supporting Feature Notes
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. Supported with Exceptions

Empty table columns

  • Some tables expose empty columns, that are not a part of the visual layout, for screen reader users.
1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. Supported  
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. Supported  

Guideline 1.4 Distinguishable

Make it easier for users to see and hear content including separating foreground from background.

Criteria Supporting Feature Notes
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. Supported  
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  
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 situations listed in WCAG 2.0 1.4.3. Supported with Exceptions

We have a few instances of low contrast left.

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. Supported with Exceptions

In-app tutorials

  • Information in the Guides and FAQs flyout becomes obscured off-screen when zoomed in to 125% or higher.
  • This feature is provided by a third party which we continually work with to help them improve the accessibility of their product.

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  

Principle 2: Operable

User interface components and navigation must be operable.

Guideline 2.1 Keyboard Accessible

Make all functionality available from a keyboard.

Criteria Supporting Feature Notes
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. Supported with Exceptions

Analytics Date Picker

  • It is not currently possible to use the Date Picker in the Analytics Feature

Table export

  • It is not currently possible to access the ‘include sub-table’ export option when exporting tables.
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. Not Supported

Sites and Groups drop-down menus

  • Some page functionality is not accessible once you activate and tab out of the Sites and Groups drop-down menus.

Analytics Filters drop-down

  • It is not possible to edit the filter or filter notes from the Analytics Filter drop-down menu. There are alternative ways to access this functionality.

Guideline 2.2 Enough Time

Provide users enough time to read and use content.

Criteria Supporting Feature Notes
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  

Guideline 2.3 Seizures

Do not design content in a way that is known to cause seizures.

Criteria Supporting Feature Notes
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. Not applicable  

Guideline 2.4 Navigable

Provide ways to help users navigate, find content, and determine where they are.

Criteria Supporting Feature Notes
2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. Supported  
2.4.2 Page Titled: Web pages have titles that describe topic or purpose. Supported  
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. Supported with Exceptions

Site and group selector

  • Unpredictable focus order for the site and group selector.

Time and period selector

  • Unpredictable focus order for the time and period selector.

Analytics filter selector

  • Unpredictable focus order for the analytics filter selector.
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. Supported  
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. Supported  
2.4.6 Headings and Labels: Headings and labels describe topic or purpose. Supported  
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. Supported with Exceptions

Page Search

  • The URL / Page Title select options do not highlight when they receive focus.


  • Some table display filters do not highlight when they receive focus.
  • Some table rows only partially highlight when they receive focus.

Other components

  • Several other components have only hardly visible keyboard focus.

Principle 3: Understandable

Information and the operation of user interface must be understandable.

Guideline 3.1 Readable

Make text content readable and understandable.

Criteria Supporting Feature Notes
3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. Supported  
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  

Guideline 3.2 Predictable

Make Web pages appear and operate in predictable ways.

Criteria Supporting Feature Notes
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. Supported  
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 Supported  
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. Supported with Exceptions

Page Reports

  • Navigation in the page reports is not consistent when changing between page reports. The page report navigation in Policy differs from the others.
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. Supported  

Guideline 3.3 Input Assistance

Help users avoid and correct mistakes.

Criteria Supporting Feature Notes
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. Supported with Exceptions

Table Filters

  • The way we name filters used for filtering table data is not obvious for AT users.
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:

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

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

Guideline 4.1 Compatible

Maximize compatibility with current and future user agents, including assistive technologies.

Criteria Supporting Feature Notes
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. Supported with Exceptions


  • In the Accessibility Tools Issues table the table structure seams to break down in some combinations of ATs.


  • We continuously work on improving code quality.
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. Supported with Exceptions

Expandable tables

  • Some tables, with expandable content do not properly convey role and state information to assistive technologies.


  • The export functions, where users can export table data to Excel etc. exist inside expandable areas that do not convey their role and state to AT users.


  • The help functions, found near the top of many pages, exist inside expandable areas that do not convey their role and state to AT users.

Table data search

  • The search function found in conjunction with most page-showing-tables do not convey its role properly for AT users.


  • Site, group, date, time etc. pickers are all implemented using a component that does not fully convey its name, role, value and states through code.

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
May 2018
  • We fixed all instances across the platform of <img> elements with missing alt attributes.
  • We fixed all instances across the platform of labels not connected to a form field.
  • We reduced form fields with no description from 60 to 15 instances and still work on the remaining.
  • We reduced low contrast issues from 106 to 12 instances and still work on the remaining.
  • We 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.