Accessibility Conformance Report

Voluntary Product Accessibility Template (VPAT) — Version 2.5

Product: OilPriceAPI — REST API & Documentation

Version: v1 (current)

Report Date: April 6, 2026

Description: OilPriceAPI is a cloud-hosted REST API that provides real-time and historical energy commodity price data. The product consists of API endpoints (consumed programmatically), a documentation website, and a customer dashboard. This report covers all user-facing components.

Evaluation Methods: Manual inspection of HTML semantics, keyboard navigation testing, screen reader testing (VoiceOver), automated scanning (Lighthouse Accessibility audit), contrast ratio verification.

Jump to Standard

WCAG 2.1 Level AA|Revised Section 508|EU EN 301 549

WCAG 2.1 — Level A & AA

Web Content Accessibility Guidelines (WCAG) 2.1 published by the W3C Web Accessibility Initiative (WAI). This section reports conformance at Level A and Level AA.

Criteria	Name	Conformance	Remarks
1.1.1	Non-text Content	Supports	API documentation images include alt text. API responses are JSON (machine-readable text).
1.2.1	Audio-only and Video-only	Not Applicable	No audio or video content is provided.
1.2.2	Captions (Prerecorded)	Not Applicable	No prerecorded media content.
1.2.3	Audio Description or Media Alternative	Not Applicable	No prerecorded media content.
1.2.4	Captions (Live)	Not Applicable	No live media content.
1.2.5	Audio Description (Prerecorded)	Not Applicable	No prerecorded media content.
1.3.1	Info and Relationships	Supports	Documentation uses semantic HTML (headings, lists, tables). API responses use structured JSON.
1.3.2	Meaningful Sequence	Supports	Content follows a logical reading order in all pages.
1.3.3	Sensory Characteristics	Supports	Instructions do not rely on shape, size, or visual location alone.
1.4.1	Use of Color	Supports	Color is not the sole means of conveying information. Status indicators use text labels.
1.4.2	Audio Control	Not Applicable	No auto-playing audio.
1.4.3	Contrast (Minimum)	Supports	Text meets 4.5:1 contrast ratio against backgrounds across the documentation site.
1.4.4	Resize Text	Supports	Text can be resized up to 200% without loss of functionality.
1.4.5	Images of Text	Supports	Text is used instead of images of text throughout documentation and marketing pages.
1.4.10	Reflow	Supports	Responsive layout reflows at 320px width without horizontal scrolling.
1.4.11	Non-text Contrast	Supports	UI components and graphical elements meet 3:1 contrast ratio.
1.4.12	Text Spacing	Supports	Content adapts to user-adjusted text spacing.
1.4.13	Content on Hover or Focus	Supports	Tooltips and hover content are dismissible and persistent.
2.1.1	Keyboard	Supports	All interactive elements are keyboard accessible. API is consumed programmatically.
2.1.2	No Keyboard Trap	Supports	Focus can be moved away from all components using the keyboard.
2.1.4	Character Key Shortcuts	Not Applicable	No single-character keyboard shortcuts are used.
2.2.1	Timing Adjustable	Not Applicable	No time limits on content. API rate limits are per-request.
2.2.2	Pause, Stop, Hide	Not Applicable	No auto-updating, moving, or blinking content.
2.3.1	Three Flashes or Below Threshold	Supports	No flashing content.
2.4.1	Bypass Blocks	Supports	Skip navigation links provided on documentation pages.
2.4.2	Page Titled	Supports	All pages have descriptive, unique titles.
2.4.3	Focus Order	Supports	Tab order follows logical content sequence.
2.4.4	Link Purpose (In Context)	Supports	Link text describes the destination or purpose.
2.4.5	Multiple Ways	Supports	Content reachable via navigation, search, site map, and direct URLs.
2.4.6	Headings and Labels	Supports	Headings and labels describe topic or purpose.
2.4.7	Focus Visible	Supports	Keyboard focus indicators are visible on interactive elements.
2.5.1	Pointer Gestures	Not Applicable	No multipoint or path-based gestures required.
2.5.2	Pointer Cancellation	Supports	Actions activate on pointer up, not down.
2.5.3	Label in Name	Supports	Accessible names match visible labels.
2.5.4	Motion Actuation	Not Applicable	No motion-activated functionality.
3.1.1	Language of Page	Supports	HTML lang attribute is set on all pages.
3.1.2	Language of Parts	Supports	Language changes within content are marked where applicable.
3.2.1	On Focus	Supports	No unexpected context changes on focus.
3.2.2	On Input	Supports	No unexpected context changes on input.
3.2.3	Consistent Navigation	Supports	Navigation is consistent across pages.
3.2.4	Consistent Identification	Supports	Components with the same function are identified consistently.
3.3.1	Error Identification	Supports	Form validation errors are identified in text. API errors return descriptive JSON messages.
3.3.2	Labels or Instructions	Supports	Form fields have associated labels. API endpoints are documented.
3.3.3	Error Suggestion	Supports	Error messages suggest corrections. API error responses include resolution guidance.
3.3.4	Error Prevention (Legal, Financial, Data)	Not Applicable	No legal commitments or financial transactions occur through the API itself.
4.1.1	Parsing	Supports	HTML validates without significant errors. API returns valid JSON.
4.1.2	Name, Role, Value	Supports	UI components use proper ARIA attributes where needed.
4.1.3	Status Messages	Supports	Status messages use ARIA live regions so assistive technology can announce them.

Revised Section 508 (U.S.)

The Revised Section 508 Standards (2017) published by the U.S. Access Board. Applicable to U.S. federal and federally-funded procurements. Section 508 incorporates WCAG 2.0 Level A & AA by reference; the criteria below address additional 508-specific requirements.

Criteria	Name	Conformance	Remarks
E205	Electronic Content	Supports	All electronic content (web pages, documentation) conforms to WCAG 2.1 Level AA.
E207	Software	Not Applicable	OilPriceAPI is a cloud-hosted REST API, not installable software.
E501	Scope — Closed Functionality	Not Applicable	No closed functionality; the API is consumed programmatically by developer-built applications.
E502	Interoperability with Assistive Technology	Supports	Web interfaces work with screen readers (NVDA, JAWS, VoiceOver). API responses are plain text/JSON.
E503	Applications	Not Applicable	No native applications; web-only interfaces.
E602	Support Documentation	Supports	API documentation at docs.oilpriceapi.com is accessible via keyboard and screen readers.
E603	Access to Functionality	Supports	All functionality available through documented, standards-based REST API endpoints.

EN 301 549 (EU)

European standard EN 301 549 V3.2.1 (2021-03) for ICT accessibility. Required for EU public procurement under Directive 2016/2102.

Criteria	Name	Conformance	Remarks
4.2	Functional Performance Statements	Supports	Users without vision, with limited vision, without colour perception, without hearing, with limited manipulation, and with limited cognition can use the API and its documentation.
5	Generic Requirements	Not Applicable	Closed functionality provisions do not apply — API is open and programmatically consumed.
6	ICT with Two-Way Voice Communication	Not Applicable	No voice communication features.
7	ICT with Video Capabilities	Not Applicable	No video content or capabilities.
8	Hardware	Not Applicable	Cloud-hosted API service; no hardware component.
9	Web Content	Supports	Web content conforms to WCAG 2.1 Level AA (see WCAG section above).
10	Non-web Documents	Not Applicable	No non-web documents provided.
11	Software	Not Applicable	OilPriceAPI is a web service, not installable software. SDKs are open-source libraries.
12	Documentation and Support Services	Supports	Documentation is web-based and accessible. Support is available via email and live chat.
13	ICT Providing Relay or Emergency Service Access	Not Applicable	Not a relay or emergency service.

GSA OpenACR (Machine-Readable)

The U.S. General Services Administration (GSA) OpenACR format provides a machine-readable version of this accessibility conformance report. The OpenACR specification enables automated processing by procurement systems.

{
  "openacr_version": "0.1.0",
  "product": {
    "name": "OilPriceAPI",
    "version": "v1",
    "description": "Cloud-hosted REST API for real-time and historical energy commodity prices",
    "vendor": {
      "name": "Oil Price API",
      "contact": "[email protected]",
      "website": "https://www.oilpriceapi.com"
    }
  },
  "report_date": "2026-04-06",
  "last_modified": "2026-04-06",
  "evaluation_methods": [
    "Manual testing",
    "Keyboard navigation",
    "Screen reader (VoiceOver)",
    "Lighthouse audit"
  ],
  "standards": [
    {
      "standard": "WCAG 2.1",
      "level": "AA",
      "conformance": "Supports"
    },
    {
      "standard": "Revised Section 508",
      "conformance": "Supports"
    },
    {
      "standard": "EN 301 549 V3.2.1",
      "conformance": "Supports"
    }
  ],
  "summary": "OilPriceAPI is a REST API service. The majority of WCAG criteria relating to visual, auditory, and interactive UI elements are Not Applicable as the core product is consumed programmatically. The documentation website and customer dashboard conform to WCAG 2.1 Level AA."
}

Notes

Product type: OilPriceAPI is primarily a REST API consumed programmatically via HTTP. The accessibility of applications built using our API data is the responsibility of those application developers.
Documentation: Our API documentation at docs.oilpriceapi.com and marketing website at oilpriceapi.com are designed to be accessible.
SDKs: Our Python, Node.js, and Go SDKs are open-source libraries that output text-based data, inherently compatible with assistive technologies.
Feedback: We welcome accessibility feedback. Please contact [email protected] to report accessibility issues or request accommodations.

This report is based on the ITI VPAT 2.5 template. "Supports" means the functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation. "Partially Supports" means some functionality of the product does not meet the criterion. "Not Applicable" means the criterion is not relevant to the product.

← Back to Home