About this statement
Tradehaus LLC wants its website and application to be usable by everyone, including people who use a screen reader, a keyboard without a mouse, voice control, or larger text. This statement says what we work toward, where we fall short today, and how to reach us when something gets in your way.
It covers tradehaus.com and the Tradehaus application (together, the “Services”).
1. The standard we work toward
We work toward the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, wherever that is reasonably achievable. Today the Services are partially conformant: most of what we have built meets the standard, and some parts do not yet.
We have not yet had an independent audit. What follows is our own assessment, and we will update this statement when one is done.
2. What we do
- Structure. Pages use headings, landmarks and labels so a screen reader can move through them and name what it finds.
- Keyboard. Controls can be reached and used from the keyboard, and the one in focus is shown.
- Images. Images that carry meaning have a text description. Decorative ones are hidden from screen readers.
- Motion. If your device is set to reduce motion, animations are turned down or off.
- Text and color. Text can be enlarged with your browser’s zoom, the application has light and dark modes, and color is not the only way information is shown.
- How we build. Accessibility is considered when a feature is designed and checked when it is built, not added afterward.
3. Where we fall short
These are the parts we know are harder to use with assistive technology today:
- Maps. The map is provided by Google and is largely visual. The same projects are available as lists, which work with a screen reader and keyboard.
- Diagrams. Some views, such as the diagram of how firms are connected, are visual. Where we can, the same information is offered as a list.
- Routes and driving. Drive mode is designed for use in a vehicle and relies on the map and on voice.
- Files you and others add. PDFs, plans and photos that people upload are shown as they were provided and may not be accessible.
- AI answers and drafts. Text produced by Arlo may not always be structured well for a screen reader.
- Services from others. Payment, scheduling and sign-in pages are run by their providers, and we do not control how accessible they are.
- Public records. Descriptions come from government filings as they were written, including abbreviations and shorthand.
If one of these stops you doing something, tell us. We will find another way to get you what you need.
4. Tell us about a barrier
Write to [email protected] and tell us:
- the page or feature;
- what you were trying to do, and what happened;
- the browser and any assistive technology you use, if you are willing to say.
We reply within 5 business days. We will then fix the problem, offer a way around it, or get you the information in another form, and tell you which and when.
5. What we rely on
The Services are built with HTML, CSS, JavaScript and WAI-ARIA, and are meant to work with current versions of the major browsers and the screen readers commonly used with them.
6. Changes to this statement
We review this statement when the Services change in ways that affect accessibility, and at least once a year. The date at the top shows when it last changed.
7. Contact
Tradehaus LLC
16185 Los Gatos Blvd., Suite 205
Los Gatos, CA 95032
[email protected]