BuildEXA

Accessibility Statement

BuildEXA is a software platform used by construction, design, and property management teams — and by the owners, tenants, contractors, and vendors they work with. We want the Service to be usable by the widest possible range of people, including people with disabilities. This Accessibility Statement describes our commitment, the standards we follow, the legal framework in Costa Rica that informs our approach, our current conformance status, and how to request help or an accessible alternative.

Last updated: [PLACEHOLDER: date]

1. Our commitment to accessibility & inclusion

We believe that project managers, engineers, architects, property owners, tenants, vendors, and every other person who touches the BuildEXA platform should be able to do so regardless of disability, assistive technology, or device. Accessibility is treated as an ongoing product and engineering priority, not a one-time project: we review new features for accessibility before release, and we work to remediate issues in existing features as they are identified.

2. Standards we follow

Our technical target is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.1 AA is the internationally recognized benchmark for web accessibility, and we use it to guide design, engineering, and quality-assurance decisions across the BuildEXA web application and related digital experiences.

3. Legal framework

BuildEXA’s operating company is based in Costa Rica, and we ground our accessibility practice in Costa Rican law:

  • Ley N° 7600, “Ley de Igualdad de Oportunidades para las Personas con Discapacidad”— Costa Rica’s foundational law on equal opportunity for persons with disabilities, which extends to access to information, communications, and services.
  • Ley N° 8661, which ratifies the United Nations Convention on the Rights of Persons with Disabilities (CRPD) as part of Costa Rican law, reinforcing the obligation to make information and communication technologies, including software services like BuildEXA, accessible.

The Costa Rican body responsible for accessibility and disability-inclusion policy is the Consejo Nacional de Personas con Discapacidad (CONAPDIS). We look to CONAPDIS’s guidance, together with WCAG 2.1 AA as the applicable technical standard, in shaping our accessibility roadmap.

If BuildEXA serves users located in the European Union or the United Kingdom, additional accessibility obligations (such as those referencing EN 301 549 or the European Accessibility Act) may also apply, in addition to the Costa Rican framework described above.

4. Conformance status

We aim for full conformance with WCAG 2.1 Level AA across the BuildEXA platform. At this time, BuildEXA is partially conformant: many parts of the Service already meet WCAG 2.1 AA success criteria, and we are actively working through the remainder of the platform to close the gaps described in Section 6. “Partially conformant” means that some parts of the content do not yet fully conform to the accessibility standard, but we are treating this as an active, ongoing program of work rather than a completed state.

5. Measures we take

We work toward WCAG 2.1 AA conformance through measures that include:

  • Semantic markup: using semantic HTML elements, headings, landmarks, and ARIA attributes so that screen readers and other assistive technologies can interpret page structure and content correctly.
  • Keyboard navigation: designing interactive elements — menus, forms, dialogs, tables, and dashboards — to be operable using a keyboard alone, without requiring a mouse or touch input.
  • Color contrast: selecting text and interface colors that meet WCAG 2.1 AA contrast ratios, so content is legible for users with low vision or color-vision differences.
  • Visible focus states: ensuring that the element currently in keyboard focus is clearly indicated, so keyboard and switch-device users can track their position on the page.
  • Reduced-motion support: respecting operating-system and browser preferences for reduced motion, and limiting non-essential animation for users who are sensitive to motion effects.
  • Descriptive text alternatives: providing text alternatives for meaningful images, icons, and non-text content where practicable.
  • Ongoing testing: incorporating accessibility checks — including automated tooling and manual review — into our development process for new and existing features.

Known limitations

Despite our efforts, some parts of BuildEXA may not yet be fully accessible. Known limitation areas may include: [PLACEHOLDER: e.g., certain data-dense tables and Gantt/ scheduling views that are difficult to navigate by keyboard or screen reader; PDF exports and third-party-generated documents that may not be fully tagged for accessibility; embedded third-party content or integrations (e.g., mapping, e-signature, or video conferencing widgets) whose accessibility we do not fully control]. We are prioritizing remediation of these areas and will update this statement as issues are resolved.

6. Requesting an accessible alternative or assistance

If you encounter a barrier while using BuildEXA, or if you need information or a document made available in an alternative accessible format, we will work with you to provide the content or complete the task through another means. This may include, depending on the situation, a phone or video walkthrough with a member of our team, a document provided in an alternative format, or a manual workaround for a specific workflow. To request an accessible alternative, please contact us using the details in Section 7 and describe the content or feature you are trying to access.

7. Feedback & contact

We welcome feedback on the accessibility of BuildEXA. If you experience any difficulty accessing any part of the Service, please let us know so we can investigate and, where appropriate, remediate the issue. You can reach us at:

  • Email: [PLACEHOLDER: accessibility@ email]
  • Contact person: [PLACEHOLDER: accessibility coordinator name/role]
  • Mailing address: [PLACEHOLDER: registered address], Costa Rica

We aim to acknowledge accessibility feedback and requests within a reasonable timeframe and to work with you toward a resolution. When you contact us, it is helpful (though not required) to include the web page or feature involved, the assistive technology and browser you were using, and a description of the problem you encountered.

This document is a draft prepared for review by qualified Costa Rican legal counsel and does not constitute legal advice.