Accessibility Statement

Last updated January 1, 1970 · Offerable is intended for use only by residents of the United States.

Our Commitment

Offerable is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

Standards Compliance

Offerable is designed to comply with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more accessible to people with disabilities.

Accessibility Features

Our application includes the following accessibility features:

  • Keyboard Navigation: All interactive elements can be accessed and operated using keyboard alone without requiring mouse input.
  • Screen Reader Support: The application is compatible with assistive technologies including screen readers such as NVDA, JAWS, and VoiceOver.
  • Color Contrast: Text and interactive elements meet WCAG AA minimum contrast ratios (4.5:1 for normal text, 3:1 for large text).
  • Responsive Design: The application is fully responsive and usable on mobile devices, tablets, and desktop computers.
  • Form Accessibility: All form fields include descriptive labels and clear error messages.
  • Focus Indicators: Visible focus indicators are provided for keyboard navigation.
  • Light and Dark Mode: Users can select light or dark theme based on their visual preferences and accessibility needs.
  • Adjustable Text Size: Users can adjust browser text size without breaking layout or functionality.

Known Limitations

While we are committed to accessibility, we recognize that some limitations may exist. Known limitations include:

  • PDF Export Feature: Exported PDF files may not be fully accessible to all screen readers. We are working to improve PDF accessibility and recommend contacting us if you need an alternative format.
  • Chart Visualizations: Some data visualizations may require additional context or alternative descriptions. Users can request text-based summaries of charts via our contact form.
  • Third-Party Components: Some third-party integrations may have accessibility limitations outside our direct control.

We are actively working to remediate these limitations.

Testing and Validation

Offerable conducts regular accessibility testing using:

  • Automated accessibility scanning tools
  • Manual keyboard navigation testing
  • Screen reader compatibility testing (NVDA, JAWS, VoiceOver)
  • Contrast and color accessibility verification
  • Responsive design testing across devices

Reporting Accessibility Issues

If you encounter an accessibility barrier or believe we are not meeting WCAG 2.1 AA standards, please report it to us using our contact form.

When submitting an accessibility report, please:

  • Select "Accessibility Issue" in the subject line (or "Other" if not available, and specify it's an accessibility issue).
  • Include a description of the accessibility barrier.
  • Specify which browser and assistive technology you are using (if applicable).
  • Provide steps to reproduce the issue.
  • Leave your contact information so we can follow up.

Response Time: We aim to respond to all accessibility reports within 5 business days.

Third-Party Services

Offerable uses third-party services including Supabase, Cloudflare, and Google Gemini API. While we have selected providers with strong security and performance records, we cannot guarantee their accessibility compliance. If you encounter accessibility issues related to these services, please report them via our contact form and we will work with the providers.

Continuous Improvement

Accessibility is an ongoing commitment. We regularly review and update our practices to ensure we are meeting or exceeding WCAG 2.1 AA standards. We welcome feedback and suggestions for improvement via our contact form.

Last Updated

This accessibility statement was last updated on January 1, 1970. We will review and update this statement quarterly or whenever significant changes are made to the application.