Accessibility
Accessibility Statement
We want this site to work for everyone reading it, including people using a keyboard, a screen reader, magnification, or a browser with scripts turned off. Here is specifically what has been done, and where it is still weak.
- Keyboard operable
- Works without JavaScript
- Contrast checked
What has been done
These are properties of how the site is built rather than intentions.
- Every interactive control — the situation selector, the service filter, the menus and the question panels — is a native HTML control, so it works with a keyboard and is announced correctly by assistive technology.
- The site is fully readable and fully actionable with JavaScript blocked. Scripts only add convenience, never content.
- A skip link is the first thing in the page, so keyboard users can jump past the menu straight to the content.
- Focus is always visible. Every focusable element gets a clear focus ring rather than relying on the browser default being noticed.
- Text and interface colours are checked against their backgrounds, and the palette used across the site meets the WCAG AA contrast ratio or better.
- Meaning is never carried by colour alone. Warnings, urgency levels and status all pair colour with an icon, a label or a shape.
- Every image has descriptive alternative text and explicit dimensions, so the layout does not shift as the page loads.
- Headings run in order, so the page can be navigated by heading structure.
- Motion respects the reduced-motion setting, and the site remains usable in forced-colours and high-contrast modes.
- Pages are readable when zoomed and reflow to narrow screens without sideways scrolling.
Where it is still weak
Stating the gaps is more useful than claiming there are none.
- The map embedded on the homepage is supplied by Google. Its internal accessibility is outside our control, which is one reason the full address and a plain directions link sit beside it in text.
- The coverage diagram is a decorative illustration of the service area rather than a functional map. It carries a text description, and every community it marks is also listed as ordinary text and as a link.
- We aim to meet WCAG 2.1 Level AA. We have not commissioned an independent audit, so we describe this as our target and our own testing rather than as a certified conformance claim.
If something blocks you
If any part of this site stops you getting the information you need, call and tell us. Say which page it was and what happened, and we will give you the information on the call regardless — you should never have to fight a website to find out whether a tree is dangerous.
We treat reports of access barriers as defects, not feedback, and fix them in the same way we would fix a broken page.
- Phone: 877-269-2454
- 410 S Newport Ave, Tampa, FL 33606, USA
- Serving Tampa Bay, Florida
Last updated: 2 August 2026
Tell us what did not work
Call and describe what happened. We will get you the information you were after, and then fix the page.
- Phone: 877-269-2454
- Serving Tampa Bay, Florida
Information on this page is general guidance for property owners and managers in the Tampa Bay area. It is not an arboricultural assessment, a legal opinion, a permitting determination or an insurance decision. Tree condition and site risk can only be judged in person.
