Skip to main content
false

Splunk’s Commitment Statement

Splunk believes in making machine data accessible, usable, and valuable to everyone. Splunk is committed to maintaining and enhancing its products' accessibility for all users, including those with diverse abilities who require the use of assistive technologies, through the following measures:

  • Include accessibility as part of our mission statement
  • Include accessibility throughout our internal policies
  • Provide continual accessibility training resources for our staff
  • Employ formal accessibility quality assurance methods

Product Accessibility Status

At Splunk, we leverage the internationally recognized accessibility regulations, standards, and best practices, specified in the W3C Web Content Accessibility Guidelines (WCAG) 2.1 Level A and AA, to the extent possible, Section 508 of the US Rehabilitation Act, and EU’s EN 301 549 Accessibility Requirements. Through internally trained staff and support from third-party testing services, we are committed to providing products designed to be accessible by those who require assistive technologies.

The Voluntary Product Accessibility Template (VPAT) is a standardized document that outlines how information technology products conform with accessibility standards. The VPAT is used to develop Accessibility Conformance Reports (ACRs) that detail the accessibility of Splunk product features. The documents listed in this section are VPATs / ACRs that reflect Splunk product conformance to applicable accessibility requirements.

Any VPAT posted in this section, or anywhere else on Splunk’s website, or otherwise publicly available, shall not be construed to be included in any contract, either explicitly or implicitly, in whole or in part, absent Splunk’s express acknowledgment through language in the contract itself that such report or its substantive equivalent is included.

Splunk Enterprise Security (ES)

Splunk Security Orchestration, Automation and Response (SOAR)


Splunk IT Service Intelligence (ITSI)


User Behavior Analytics (UBA)



Frequently Asked Questions

How does Splunk develop, test, and assess its products for accessibility? What standards does Splunk follow? 

At Splunk, we follow WCAG 2.1 Level A and AA Success Criteria and Section 508 guidelines to test our product.


How does Splunk ensure that products are current with changing legal requirements and accessibility best practices?

We update our accessibility review process with each update of Section 508, EN 301 549, and WCAG guidelines. Additionally, we have dedicated design resources focusing on accessibility across the Splunk product portfolio.


Describe the accessibility-related plans/roadmap for Splunk products.

We have an internal compliance roadmap for Splunk products that have current VPATs, and we are in process of developing VPATs for other Splunk offerings.


What department at Splunk is responsible for the electronic accessibility policy and compliance?

A task force that includes representatives for Design, Product Management, Product Compliance, Engineering / QA, Legal, and Field drives accessibility guidelines and compliance.


What is the process for Splunk customers to report product accessibility issues and to request their remediation?

Customers should contact Splunk's Customer Support team. For the U.S., the number is 855-SPLUNK-S. You can also contact support@splunk.com or visit the Splunk Support Portal. Support tickets can be created, after logging in, via the support portal, or via phone. Upon creating a support case, you will receive an email with the case number and a URL to the case on the Splunk Support Portal. 


What kind of response-time guarantee does Splunk provide for issues having to do with accessibility compliance?

Splunk treats accessibility issues in the same manner as other product issues – based on severity and priority. Please refer to the SLA timeframes


It is expected that Splunk products are tested for accessibility. Please outline your testing framework for accessibility.

At Splunk, we follow WCAG 2.1 Level A and AA guidelines and Section 508 standards and test our product against these standards.


Describe the assistive technologies Splunk support/have worked with / have tested with.

We test on Splunk-supported web browsers with assistive technologies such as JAWS, NVDA, and VoiceOver.


Which role is used to determine the scope of accessibility testing?

The scope of accessibility testing as reflected in VPATs / ACRs encompass the accessible pages and components of a standard end-user role (non-admin).