Accessibility Statement

1. Commitment to Accessibility

Tereda Software LLC ("Tereda Labs," "we," "us," or "our") is committed to ensuring digital accessibility for all users, including persons with disabilities. We hold ourselves to the standards required for federal technology procurement and apply those same standards to our own web presence and all deliverable software.

Accessibility is not an afterthought in our engineering process — it is a core requirement integrated from the earliest stages of design and architecture through testing, deployment, and ongoing maintenance. We believe that inclusive design produces better software for everyone, and we structure our development practices accordingly.

2. Conformance Standards

Tereda Labs targets conformance with the following accessibility standards across our web properties and deliverable software:

WCAG 2.1 Level AA — The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA success criteria serve as our primary accessibility benchmark for all new development. WCAG 2.1 extends WCAG 2.0 with additional criteria addressing mobile accessibility, low vision, and cognitive and learning disabilities.

Section 508 of the Rehabilitation Act (29 U.S.C. § 794d) — Products and services delivered to federal agencies conform to the Revised Section 508 Standards (36 CFR Part 1194), which incorporate WCAG 2.0 Level AA criteria by reference. Section 508 requires that information and communication technology (ICT) developed, procured, maintained, or used by federal agencies be accessible to people with disabilities.

As a best practice, we target WCAG 2.1 Level AA for all new development, which meets and exceeds the WCAG 2.0 Level AA baseline required by the Revised Section 508 Standards. Where contract terms specify additional accessibility requirements, we incorporate those into our design and testing processes from the outset of the engagement.

3. Accessibility of This Website

teredalabs.com is designed and developed to substantially conform with WCAG 2.1 Level AA. We have implemented the following accessibility features across this website:

• Semantic HTML structure — Pages are built with proper heading hierarchy, landmark regions, and meaningful document structure to support assistive technology navigation.
• ARIA landmarks and labels — Navigation, main content, and footer regions are identified with ARIA landmarks and descriptive labels to help screen reader users orient within pages.
• Keyboard navigability — All interactive elements, including navigation menus, links, buttons, and form controls, are operable using keyboard input alone without requiring a mouse.
• Sufficient color contrast — Text and interactive elements maintain minimum color contrast ratios of 4.5:1 for normal text and 3:1 for large text, consistent with WCAG 2.1 SC 1.4.3 (Contrast Minimum).
• Focus indicators — Visible focus indicators are provided for all interactive elements so keyboard users can track their position on the page.
• Skip navigation links — A "Skip to main content" link is provided at the top of every page, allowing keyboard and screen reader users to bypass repetitive navigation and move directly to the primary content.
• Responsive design — Pages reflow and adapt across viewport sizes and zoom levels, supporting users of assistive technologies, magnification software, and mobile devices without loss of content or functionality.

4. Accessibility of Delivered Software

All software systems delivered by Tereda Labs are designed with accessibility as a core requirement, not an afterthought. Our accessibility engineering practices for deliverable software include:

• WCAG 2.1 AA integrated into design specifications — Accessibility requirements are defined during the design phase and included in acceptance criteria for every user-facing component. Designs are reviewed for conformance before implementation begins.
• Automated testing in CI/CD — Automated accessibility scanning using axe-core and Lighthouse is integrated into our continuous integration and continuous delivery pipelines. Accessibility regressions are flagged as build failures and must be resolved before deployment.
• Manual testing with assistive technologies — We conduct manual testing with screen readers (NVDA, JAWS, VoiceOver), keyboard-only navigation, and voice control to validate that automated tools alone cannot catch — including logical reading order, meaningful focus management, and real-world usability.
• Color contrast and focus management validation — All color combinations are validated against WCAG contrast ratios, and focus management is tested across dynamic content updates, modals, and single-page application route changes.
• Form labeling and error identification — All form inputs are programmatically associated with visible labels per WCAG SC 1.3.1 (Info and Relationships). Error messages are descriptive, programmatically associated with the relevant input per WCAG SC 3.3.1 (Error Identification), and input purpose is identified per WCAG SC 3.3.2 (Labels or Instructions).

5. VPAT / Accessibility Conformance Report (ACR)

Tereda Labs provides Voluntary Product Accessibility Templates (VPATs) using the ITI VPAT 2.5 template upon request. VPATs document the conformance level of individual products against WCAG 2.1, the Revised Section 508 Standards, and EN 301 549 (European accessibility standard) where applicable.

Accessibility Conformance Reports (ACRs) are generated for each deliverable product and document the specific level of conformance — Supports, Partially Supports, Does Not Support, or Not Applicable — for each criterion. ACRs are available for procurement evaluation and are updated with each major release.

To request a VPAT or ACR for any Tereda Labs product, contact [email protected].

6. Testing Methodology

Tereda Labs employs a three-layer accessibility testing approach to ensure comprehensive coverage across automated, manual, and real-world evaluation:

Layer 1: Automated scanning — axe-core, Lighthouse, and WAVE are integrated into our development pipeline and run against every build. Automated scanning catches a broad range of detectable issues including missing alt text, improper heading hierarchy, color contrast failures, missing form labels, and ARIA misuse. Automated tools typically detect approximately 30–40% of accessibility issues, which is why we do not rely on them exclusively.

Layer 2: Manual testing — Trained testers evaluate every user-facing feature using keyboard navigation, screen reader testing with NVDA, JAWS, and VoiceOver, high-contrast mode, and text scaling to 200%. Manual testing catches issues that automated tools cannot detect, including logical tab order, meaningful reading sequence, appropriate use of live regions, and cognitive accessibility of interactions.

Layer 3: Assisted review — We conduct periodic reviews with users of assistive technologies to validate real-world usability. These reviews surface practical barriers that may not be apparent through automated or manual testing alone, including workflow efficiency, comprehension, and the overall user experience for people who rely on assistive technology daily.

7. Known Limitations

While we strive for comprehensive conformance, we recognize that accessibility is an ongoing process. Some content may not yet meet every WCAG 2.1 Level AA success criterion due to the evolving nature of web technologies, third-party integrations, or content that is still being evaluated and remediated.

If you encounter content on teredalabs.com or within any Tereda Labs product that is not fully accessible, please report it using the contact method below and we will prioritize remediation. We treat accessibility barriers as defects with the same urgency and tracking as security vulnerabilities.

8. Reporting Accessibility Barriers

If you encounter accessibility barriers on this website or in any software delivered by Tereda Labs, we want to hear from you. Please contact us at:

Email: [email protected]

When reporting an accessibility issue, please include the following information to help us investigate and resolve it efficiently:

• URL — The web address of the page where you encountered the barrier.
• Description of the issue — What you were trying to do and what happened (or did not happen).
• Assistive technology used — The name and version of any assistive technology (screen reader, magnification software, voice control, etc.), browser, and operating system you were using.

We will acknowledge accessibility reports within 5 business days and provide a remediation timeline based on the severity and scope of the reported barrier. Critical barriers that prevent access to essential content or functionality are prioritized for immediate resolution.

9. Continuous Improvement

Accessibility at Tereda Labs is not a one-time effort — it is an ongoing commitment embedded in our standard development lifecycle. Our continuous improvement practices include:

• Lifecycle integration — Accessibility reviews are conducted as part of the standard development lifecycle for every project, from requirements gathering through design, implementation, testing, and deployment.
• Issue tracking and remediation — Accessibility defects are tracked through our issue management process with defined severity levels, remediation timelines, and verification steps. Remediation is confirmed through retesting before closure.
• Annual accessibility audit — We conduct a comprehensive accessibility audit of all public-facing properties at minimum annually, evaluating conformance against current WCAG guidelines and Section 508 requirements.
• Staff training — Development, design, and quality assurance personnel receive training on accessible development practices, including semantic HTML, ARIA authoring patterns, keyboard interaction models, and assistive technology testing procedures.

For questions about this accessibility statement, our conformance posture, or to request a VPAT or Accessibility Conformance Report, contact:

Accessibility and legal inquiries: [email protected]

Tereda Software LLC
Connecticut, USA