Free for May: AI Visibility Audit — see how your site shows up in ChatGPT and Google's AI Overviews.Run yours →

← Trust Center

Trust Center · Accessibility Statement

Accessibility Statement

OpenSource Technologies designs for accessibility from day one rather than triaging after demand letters. Our standards, our testing process, and how to report issues.

Last reviewed: TBD · Pending legal review · OpenSource Technologies, Inc., a Pennsylvania corporation

Draft notice. This document is a structural draft pending legal review. The framework, sections, and OST's general approach are accurate. Specifics (jurisdictions, regulators, exact data-handling language, legal definitions, governing law) are determined per engagement and reviewed by counsel before any production deployment. Use the contact form for engagement-specific compliance questions.

Section 01

Our commitment

OpenSource Technologies is committed to designing and engineering software that is accessible to people with disabilities. This commitment applies to ost.agency, to the platforms we build and operate for clients, and to the engagement-level deliverables we ship.

We approach accessibility as engineering, not afterthought:

  • Designed for accessibility from day one: Information architecture, interaction patterns, and visual design account for accessibility before development starts
  • Built into the development process: Accessibility considerations are part of code review and quality assurance
  • Tested before launch: Automated and manual accessibility testing across screen readers, keyboard-only navigation, and contrast/visual hierarchy
  • Maintained through updates: Accessibility regression testing on each major release

Section 02

Standards we support

OST targets the following accessibility standards across our work:

  • WCAG 2.2 AA: Web Content Accessibility Guidelines, level AA. Our default target for new builds and significant redesigns.
  • Section 508: US federal accessibility requirements. Applied to engagements serving federal-grant recipients and government clients.
  • ADA Title III: US Americans with Disabilities Act, places of public accommodation. Increasingly applied to commercial websites following recent litigation.
  • EN 301 549: European accessibility standard for ICT, where engagements serve EU public sector or EU consumers.

Specific conformance level (A, AA, AAA) and testing depth are scoped per engagement based on the regulatory and business context.

Section 03

What conformance includes

WCAG 2.2 AA conformance for our work generally includes:

  • Color contrast meeting AA ratios for text, controls, and graphical elements
  • Font legibility at every screen size and zoom level
  • Semantic markup for assistive technologies (screen readers, voice control, switch devices)
  • Keyboard-only navigation for every interactive element
  • Tabbing order on mobile, tablet, and desktop
  • Screen reader support with appropriate ARIA labels and live region announcements
  • Accessible video with captions, transcripts, and audio descriptions where applicable
  • Form accessibility with clear labels, error identification, and recovery paths

Section 04

Known limitations

No website is perfectly accessible. We document known limitations and work to address them.

Common limitation categories that may apply:

  • Third-party embedded content (videos, social embeds, analytics widgets) where OST does not control the third-party output
  • Older content from previous site generations not yet remediated
  • Browser-specific or assistive-technology-specific edge cases

If you encounter an accessibility barrier, please report it (see Feedback below).

Section 05

Feedback and reporting

If you have feedback on the accessibility of OST's website or any platform OST has built or operates:

Use the contact form and select "Accessibility feedback or report" in the conversation type dropdown.

Mailing address: OpenSource Technologies, Inc., 650 N Cannon Ave #229, Lansdale, PA 19446, USA.

Please include: the URL or platform you're accessing, the assistive technology and browser you're using, and a description of the issue.

OST commits to acknowledging accessibility feedback within 5 business days and providing a remediation timeline within 30 business days, scoped to the complexity of the issue.

Ask AI