Content Area

Oracle's Accessibility Philosophy and Policies

Oracle is committed to building standards-based products to help customers reduce complexity and get the most out of existing technology investments, and this commitment extends to our approach to accessibility. Oracle uses industry-standard technologies such as HTML, JavaScript and Java to render most user interfaces, and we follow internationally-recognized accessibility standards allowing support for a broad range of assistive technology (AT) such as screen readers, screen magnifiers, and voice recognition.

Accessibility has presented unique challenges to the Information and Communication Technology (ICT) community as a whole due to the range of laws and guidelines related to it, and the rapid pace of changes in technology, and the impact across nearly every aspect of product development from initial design through Support. Learn how Oracle is meeting those challenges below.


The Oracle Accessibility Guidelines are currently based on Section 508 of the Rehabilitation Act of 1973 as amended 1998, and the World Wide Web Consortium's (W3C) Web Content Accessibility Guidelines version 2.0 guidelines at the AA level (WCAG 2.0 AA).

Oracle is committed to developing new products in conformance with the WCAG 2.0 AA standards to the extent practicable; as new products and revisions are released that conform to the WCAG 2.0 standards, we will publish Voluntary Product Accessibility Templates (VPATs) that also include a table of all of the WCAG 2.0 'A' and 'AA' standards, in addition to the Section 508 standards. For VPATs that do not yet contain that additional table, you may use information from the U.S. Access Board and the WAI to assess the degree of conformance with WCAG 2.0 that our products may already exhibit. Before formally adopting all of WCAG 2.0 'AA' standards, Oracle already used extensive success criteria from WCAG 2.0, where there was an obvious mapping from Section 508 or WCAG 1.0, such as the 4.5:1 color luminosity contrast for text, and much of this detail is typically reflected in our VPATs.

In 2006, the U.S. Access Board started work on the Section 508 refresh by launching the TEITAC committee to serve as an advisory board, and in 2015 issued a Notice of Proposed Rule Making that was based on the WCAG 2.0 AA standards. And in 2014, the European Union standard EN 301 549 'Accessibility requirements suitable for public procurement of ICT products and services in Europe' was issued in response to Mandate 376, and it too was based on the WCAG 2.0 AA standards. Oracle has been an active participant in the development of these guidelines and is closely tracking their progress.

Any standard is subject to some amount of interpretation; see Standards Interpretation for a detailed look at how Oracle addresses specific standards.


Oracle products are tested for accessibility using a variety of techniques including automated tools, expert heuristic review, visual inspection, manual operation, and testing with various AT by both disabled and non-disabled users. We report the outcome of that testing using the Voluntary Product Accessibility Template (VPAT). The VPAT was developed by ITI and GSA to assist Federal contracting officials and other buyers in making preliminary assessments regarding the availability of commercial ICT products and services with features that support accessibility. See Voluntary Product Accessibility Templates for an in-depth discussion of how we use the VPAT, and to locate the VPATs for Oracle products.


Oracle's Accessible Customer Service Plan for Ontario, Canada (PDF) outlines the policies, practices and procedures approved by Oracle in order to meet the obligations under the Accessibility for Ontarians with Disabilities Act, 2005 (AODA) and specifically Regulation 429/07. Oracle's Multi-Year Accessibility Plan (PDF) outlines Oracle's commitment to compliance to Ontario’s accessibility standards.