Accessibility Statement

01 Our commitment

DealCap is committed to ensuring digital accessibility for people with a wide range of disabilities — including visual, motor, auditory, and cognitive. We actively work to improve the user experience for everyone and apply relevant accessibility standards across our web application and marketing pages.

This commitment applies to dealcap.net and all subpaths, including the deal analyzer at /analyze, the pricing page at /pricing, and these legal pages.

02 Conformance standard

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. WCAG 2.1 AA is the standard required by:

• The European Accessibility Act (EAA), effective June 2025
• Section 508 of the US Rehabilitation Act
• The UK Equality Act 2010
• ADA Title III as interpreted by US federal courts

Current status: Partially conformant. We meet the majority of WCAG 2.1 AA criteria. Known gaps are listed in Section 04 below and are actively being addressed.

03 Measures taken

The following accessibility measures are in place across DealCap:

Keyboard navigation

• All interactive controls (buttons, inputs, sliders, dropdowns) are reachable via keyboard Tab navigation.
• Focus styles are visible on all interactive elements.
• Modal dialogs trap focus correctly and return focus on close.

Screen reader support

• All form inputs have associated aria-label or visible <label> elements.
• Metric cards use aria-label to describe their value and context (e.g., "Cap Rate 9.4%, above target").
• Charts include accessible text summaries where SVG/canvas elements are used.
• Icons that convey meaning have aria-label; decorative icons have aria-hidden="true".

Color & contrast

• Text contrast ratios meet the WCAG AA minimum of 4.5:1 for normal text and 3:1 for large text in both light and dark themes.
• Status indicators (positive/warning/negative) use both color and a text label or icon — color is never the sole means of conveying information.

Responsive & motor-friendly design

• Tap targets are at least 44×44px on mobile.
• The layout reflows at all zoom levels up to 400% without requiring horizontal scrolling for primary content.
• Sliders support both mouse drag and keyboard arrow-key input.

Typography & readability

• Font sizes are set in relative units (rem/em) and scale with browser text size settings.
• Line height and paragraph spacing meet WCAG 1.4.12 (Text Spacing).
• Language is declared in the HTML lang attribute.

04 Known limitations

The following known issues are currently being worked on. We aim to resolve all of them by our next review in October 2026:

• Sensitivity chart: The Recharts-based price sensitivity chart does not yet expose data via ARIA roles. A data table alternative is displayed below the chart, but the chart itself is not fully screen-reader accessible.
• Amortization table: Long tables (360 rows for a 30-year loan) are paginated but pagination controls do not currently announce page changes to screen readers via a live region.
• PDF exports: PDF files generated by DealCap are not yet tagged for accessibility (PDF/UA standard). Exported files may not be fully readable by screen readers.
• Mobile bottom sheet: The settings bottom sheet on mobile uses aria-modal but does not yet prevent background content from being announced on all screen readers.

05 Third-party content

Some parts of DealCap rely on third-party components whose accessibility we do not fully control:

• Clerk (authentication): Sign-in and sign-up modals are provided by Clerk. Clerk maintains its own accessibility standards. If you encounter issues with the authentication flow, please contact us and we will relay the feedback.
• Stripe (payment): The Stripe Checkout and billing portal are provided by Stripe, which maintains WCAG 2.1 AA conformance for its hosted pages.

06 Feedback & contact

We welcome accessibility feedback. If you experience any barrier on DealCap that prevents you from accessing content or using a feature, please let us know — we aim to respond within 5 business days and resolve confirmed issues within 30 days.

When reporting an issue, it helps to include: the page URL, the assistive technology you use (e.g., VoiceOver on iOS, NVDA on Windows), and a description of the problem.

07 Formal enforcement

If you are not satisfied with our response to an accessibility complaint, you may contact the relevant enforcement body in your jurisdiction:

• United States: US Department of Justice, Civil Rights Division — ada.gov
• European Union: Your national market surveillance authority under the European Accessibility Act (EAA).
• United Kingdom: Equality and Human Rights Commission — equalityhumanrights.com