Voluntary Product Accessibility Template (VPAT)

Name of Product: The Siteimprove Intelligence Platform: Accessibility, Quality Assurance, Data Privacy, SEO, Ads, Analytics, Performance, Siteimprove Accessibility Checker (browser extension), Siteimprove Browser Extension (browser extension), Siteimprove CMS plugins
Product Description: Digital optimization platform
Report Date: October 27, 2021
Contact Information: vpat@siteimprove.com
Notes: This report covers conformance for the Siteimprove web application and does not discuss documentation or support services.
Evaluation Methods Used: Automatic testing using the Siteimprove Accessibility product, Manual testing using the Siteimprove Accessibility Checker, Manual screen reader testing, Manual keyboard testing, Manual audits of select pages


Release notice: On February 10th, 2021 we released a new accessibility product. Through automated tests, screen reader testing, and extensive manual testing we consider this new accessibility product to be highly accessible and conforming to WCAG 2.1 Level AA in all aspects.
This means that the items listed on this VPAT are related to other products in the Siteimprove Intelligence Platform, and they are all in the process of being remediated.
If you experience accessibility-related bugs in any of our products, or if you have any suggestions for improvements, please reach out to us via vpat@siteimprove.com. We are always interested in your feedback for building better products.

Executive Summary

VPAT stands for Voluntary Product Accessibility Template. The ITI VPAT® is the leading global reporting format for assisting buyers and sellers in identifying information and communications technology products and services with accessibility features. It is used by government, private, and public sector companies, initially in the US, as a statement of product accessibility, and is gaining global recognition.

We use the VPAT for evaluating the accessibility of our product according to the Web Content Accessibility Guidelines (WCAG). For an extended report including Section 508 and EN 301 549, please refer to our downloadable VPAT (PDF version).

The Siteimprove Platform has been developed with accessibility in mind, and the majority of all functionality is accessible and usable.

For the purpose of identifying accessibility issues, we have installed a thorough procedure, which, in addition to automated accessibility evaluations and heuristic evaluations, involves manual testing performed by experts in a variety of browser and assistive technology combinations. The effort has resulted in uncovering a number of areas where we can improve. These include:

  • Several tooltips with limited screen-reader and keyboard support
  • Several interactive maps with limited screen-reader support
  • Several charts with low color contrast

We are currently working on upgrading these areas to improve all critical functionality and ensure that the experience is accessible and usable for all users with and without assistive technologies.

If you encounter bugs related to the accessibility of our products, or simply have an idea for an improvement, we would like to hear from you. Please do not hesitate to contact our accessibility program manager at vpat@siteimprove.com.

Scoping Requirements

Note: This VPAT reports on the entire Siteimprove Intelligence Platform as a whole and does not restrict itself to individual products. 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.

Product documentation and support services are not covered in this VPAT.

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

Analytics product:

  • Missing alternative text on the trend arrow

General platform:

  • Some tooltips need a better label

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.


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.


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.


1.3.1 Info and Relationships

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

Partially Supports
  • Instructions for the widget library
  • "Last 12 months" visualization need improved compatibility with screen-readers
  • Analytics Live feature tooltip is not conveyed to screen-reader
  • Users of the JAWS screen reader might experience the following bug: Sorting a table may result in incorrect row headers being announced. We’re working with JAWS on solving the bug in their software
  • Some regions don't have accessible names
  • One instance of an empty container element
  • Some form fields lack appropriate labels

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
  • Incorrect use of heading structure in some tool tips

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.

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
  • Some charts only use color to convey meaning/separate different regions

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 The product does not play audio automatically.

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
  •  Some tooltips are not keyboard accessible
  • Dashboard Widgets cannot be rearranged using keyboard only
  • Copy URL button in analytics module is difficult to access with keyboard navigation
  • Some tooltips contain links
  • Link sorting in “My policies” is not keyboard accessible
  • Share Widget "Add from group" modal is not keyboard accessible
  • Site Picker "pin" button has two tab-stops
  • Some input fields don't have an ideal keyboard navigation
  • Date-picker widget has some keyboard accessibility issues

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.
Partially Supports
  • Detail panel in Ads module contains a keyboard trap

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

The product does not use character key shortcuts.

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.


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.

Supports All animations also support being turned off by disabled animations from the settings on the user’s computer.

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.

All animations also support being turned off by disabled animations from the settings on the user’s computer.

2.4.1 Bypass Blocks

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
Partially supports
  • Some tables are missing a button to skip content
  • "Edit tags" function is missing a bypass block
  • One “Skip to main content” link not accessible to keyboard-only users. This is not an issue for screen-reader users.

2.4.2 Page Titled

Web pages have titles that describe topic or purpose.

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
  • Some modals have illogical focus order 
  • In-platform feedback/help module has some issues with focus order
  • Setting target and selecting keywords in SEO module has illogical focus order
  • Campaign calendar in Analytics module has some issues with focus order
  • Policy module has some minor issues with 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
  • Some modules have unlabeled buttons
  • Some pages have duplicate button names
  • Some modules have generic link texts
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.
Partially supports
  •  Labels on some buttons and links in SEO module are read differently than the text that is shown visually
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.

3.2.1 On Focus

When any component receives focus, it does not initiate a change of context.

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
  • Platform tables: 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.

3.3.2 Labels or Instructions

Labels or instructions are provided when content requires user input.
Partially Supports
  • Shortcut menu in Analytics module lacks instructions for screen reader users 
  • Some input fields in Ads module lack labels

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.
Partially Supports
  •  Some elements do not have unique ID’s

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
  • Some elements are not announced correctly to Screen Reader
  • Some elements lack labels

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

The product does not have live audio.

1.2.5 Audio Description (Prerecorded)

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


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.

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.

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 contrasts
  • Some instances of contrast issues in the platform

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
  • Few issues with fixed font size

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.

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.
Partially supports 
  • Some content in in-platform tutorials is cut off when zoomed in 400%
  • Error message in feedback module is obscured on 400% zoom
  • Content on some pages is cut off on 400% zoom

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  
  • Contrast ratio between some areas in SEO and Ads module is lower than 3:1

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.

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:

  • Dismissible: 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.
Partially supports  
  • A few Tooltips in some table column headers are not dismissable using the keyboard
  • Tooltips in dropdowns can't be dismissed with Esc key

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.

2.4.6 Headings and Labels

Headings and labels describe topic or purpose.
Partially Supports


  • When editing filter in Analytics module, the submit button has misleading label
  • One dropdown in Accessibility Module is not programmatically tied to its label

2.4.7 Focus Visible

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Partially Supports


  • In-platform help module is lacking some focus styling
  • One button lacks focus styling

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.

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 Quality Assurance

3.2.4 Consistent Identification

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

The product follows a styleguide which intends to ensure uniformity in look and behavior between components of the same type. This styleguide is continuously maintained.

• Some links open in a new window without notifying screen reader 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.

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.

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
  • Auto-populated search results in navigation menu is not announced by screen-reader

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 Evaluated


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

1.2.9 Audio-only (Live)

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

Not Evaluated  

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 Evaluated  

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 Evaluated  

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 Evaluated  

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 Evaluated  

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 Evaluated  

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 Evaluated  

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 Evaluated  

2.2.4 Interruptions

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

2.2.5 Re-authenticating

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

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 Evaluated  

2.3.2 Three Flashes

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

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 Evaluated  

2.4.8 Location

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

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 Evaluated  

2.4.10 Section Headings

Section headings are used to organize the content.
Not Evaluated  

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 Evaluated  

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 Evaluated  

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 Evaluated  

3.1.4 Abbreviations

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

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 Evaluated  

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 Evaluated  

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 Evaluated  

3.3.5 Help

Context-sensitive help is available.
Not Evaluated  

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 Evaluated  

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 2021
  • Missing alt text added on trend arrows
  • Issue with navigation solved
  • Screen reader experience with tooltips improved
  • All iFrames now have accessible names, headings and description
  • Screen reader experience with table columns improved
  • Inaccessible use of colors has been changed
  • Issue with tooltip and chat function in in-platform feedback feature has been solved
  • Misleading button label changed
  • Alt text on behavior maps improved
  • Tooltip improved
  • Issues with landmarks solved
  • Screen reader experience improved on mapping tables
  • Issue with focus order fixed
  • Inaccessible buttons fixed
  • Screen reader experience improved for column headers
  • Issue with modal solved
  • Heading hierarchy issues mitigated
  • Issue with focus trap fixed
  • Keyboard navigation in dropdowns improved
  • Missing focus styling on charts has been implemented
  • Tooltips in table headers improved
  • Illogical focus order in help module fixed
  • Missing accessible names fixed
  • Empty headings fixed
  • Issue with dropdown labels solved
  • Screen readers now announce auto-updated search results when filtering tables
  • Inaccessible graphics improved
  • Aria-live issues on table footers fixed
  • Missing skip-to-main-content link has been added
July 2021
  • Inaccessible modal fixed
  • Missing alt attributes added to button
  • Issue with generic link texts fixed
  • Issues with visible focus styling on some charts have been resolved
  • Untoggleable tooltips can now be toggled
  • Dropdowns missing proper labelling have been fixed
  • Resolved issue with illogical accessible name on a button
June 2021
  • Issue with generic button label fixed
  • A number of missing text alternatives added
  • Issue with “open in new tab” button fixed
  • Issue with “open in new tab” links fixed
  • Color contrast issues fixed
 May 2021
  • Solved: several cases of links opening in new window without notifying user
  • Link with missing text alternative fixed
  • Missing focus styling on checkbox added
  • Better labels added to dropdowns to enhance screen reader experience
April 2021
  • Inaccessible issue field solved
  • Issue with focus on links in heatmap tables solved
  • Some contrast issues fixed
  • Issues with keyboard accessibility in SEO module solved
  • Day/Hour widget accessibility issues fixed
  • Issue with modal not being announced by screen-reader solved
  • Link removed from tooltip
  • Screen reader experience improved for accessibility score gauge
  • Screen reader experience improved for some charts
  • Unconnected input label fixed
  • Missing landmarks fixed in Accessibility module
  • Tooltips are now more accessible
  • Screen reader experience with some icons have been improved
  • Missing role on drop-down added
  • Next page button in Chrome extension now has meaningful label
  • Missing text alternative on button fixed
  • Missing alt tags on some images has been fixed
March 2021
  • Some cases of inaccessible tooltips have been fixed
  • Issues with keyboard and screenreader accessibility has been solved
  • Missing labels on some input fields have been added
  • Contrast issues in SEO module has been fixed
February 2021
  • Missing labels on tooltips have been added
  • Focus issues in one modal fixed
  • Inaccessible tool-tip behavior fixed
  • Missing bypass block added
  • Tooltip on target score conformance chart has been made accessible
  • Issue with generic region names fixed
  • Accessibility issue with in-platform-feedback dialog solved
  • Contrast issues on a number of components fixed
  • Issue with too many tab-stops solved
  • Screen reader experience with some link stylings enhanced
  • Issue with some charts skipping heading levels fixed
  • Issue with loading animation solved
  • Loading state on buttons made accessible
  • Screen reader experience on progress bar has been enhanced
January 2021
  • Issue with color contrast on mouseover fixed
  • Radio button groups now support arrow up/down navigation
  • Policy Page Report: Settings and Notes button are now keyboard accessible
  • Map Chart and search panel in data privacy are now keyboard-accessible
  • Asset Location Map, Monitored Pages graphs in Performance are now keyboard-accessible
  • Issues with keyboard-accessibility in CMS plugin has been fixed
  • Cards expand/collapse functionality is now keyboard-accessible
  • Issues with illogical focus order in Site and Group selectors, Time and Period selector, Analytics filter selector and Campaign Calendar has been fixed
  • "Learn more" links now have a screen-reader label
  • Issue with lacking focus indicators in interactive components has been solved
  • Input fields in Feedback module now have label/instructions
  • Notifications are now properly announced
December 2020
  • Reflow issues in feedback module solved
  • Focus styling on feedback module is now visible regardless of background color
  • Contrast issues in feedback module solved
  • Input fields in feedback module have been improved for screen readers
November 2020
  • Website Certificate Calendar markings are now announced properly by screen readers
  • Malware details pages now have a descriptive title
October 2020
  • Issue with hidden links remaining in tab order was fixed
  • Button labels has been made less generic
  • Screen reader experience has been enhanced when browsing "broken links" table
  • Fixed issue with pop-over which was unreachable by keyboard
  • Issue with color contrast was fixed
  • Illogical tab-order in Insights was fixed
  • Site Picker "pin" button no longer has two tab-stops
September 2020
  • Dashboard Picker has invisible table column and needs some semantic improvements
  • Asset Location Map needs accessibility mark-up improvements
  • Keyboard navigation for tooltips in Policy module needs improvement
  • Login page and Switch account lacks keyboard navigation
  • Policy details tooltips are not keyboard accessible
  • Page Report: Low contrast on printed HTML attributes
  • In "Essentials", 'All tags' is hidden in column but still focusable
  • Linked Account dialog checkboxes need labels
  • Search notification is not announced by screen-reader within Top Ranking Pages
August 2020
  • Added name of site to "Open in new window" and "Edit" links in the Site Picker
  • Added keyboard navigation to spelling mistake summary in the Quality Assurance module
  • Optimized screen reader label for the site picker
  • Added proper label to "Edit tags" buttons in the Accessibility module
July 2020


  • Added visual patterns to all chart legends in Accessibility module
  • Improved labels for icon-only buttons in Ads module
  • Added keyboard navigation to maps and tooltips in Performance module
  • Align keyboard tabbing with natural reading order for maps in Performance module
June 2020
  • Improved tooltip screen reader labels and added keyboard tabbing in Accessibility NextGen Page Reports
  • Changed site picker and filter bar to also be a landmark in newer products
  • Improved all new tables for screen reader users by marking key cells as row headers
  • Improved keyboard navigation for Siteimprove CMS plugin
  • Improved screen reader error announcements for Dashboard Reports
  • Improved keyboard navigation for SEO tags in "Add keywords" modal
  • Added closing the Feedback module with the Escape key
April 2020
  • Map Chart and search panel in Data Privacy are no longer keyboard inaccessible
February 2020
  • Improved color contrasts for dropdowns and Status tags in Analytics module
  • Improved icon and button labels in Feedback module
  • Connected labels with checkboxes on "Manage Account" page in Ads module
January 2020
  • Improved color contrasts in Performance module
  • Improved site picker dropdown semantics
  • Improved difficulty level labels in SEO module
December 2019
  • Added missing alt texts to icon buttons
  • Improved screen reader experience in the Cookie Banner
  • Improved contrast for "Create Activity Plan" in Analytics module
October 2019
  • Improved keyboard navigation for tooltips in the Quality Assurance Page Report
  • Improved keyboard navigation and semantics for "Edit readability" modal in the Quality Assurance module
September 2019
  • Improved semantics and keyboard navigation for components' Help and Export tabs
  • 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 the Accessibility module
  • Fixed semantics on decision widget in the Accessibility module
  • Added visible focus to interactive modal elements in the Settings module
  • Added proper role to Notification area
  • Added label to progress gauges in the Accessibility module
July 2019
  • Exposed Modal close button to screen-readers
  • Added keyboard navigation to filter popover tooltips in the Analytics module
  • Added keyboard navigation to misspelling filter dropdown in the Quality Assurance module
  • Added keyboard navigation to search filter dropdowns in the 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
February 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
January 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
December 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 users could not close splash-screens and tutorial windows
November 2017
  • Solved issues with invisible keyboard focus, bad contrast and missing accessible names for buttons in the Feedback and Share modules
October 2017
  • Improved landmark structure
  • Released new main navigation with improved semantics and states