Built to be usable, and honest about the gaps.

Housing is not optional, so a website about housing should not be difficult to use. This statement describes how TrustLine Real Estate LLC has built this site, what we know is still imperfect, and what happens when you tell us something is broken. It is written about this site specifically — not copied from a template.

Last updated August 13, 2026.

Our commitment

We want every visitor to be able to read about a property, understand how a Florida transaction works, and reach Scott Lee — using a screen reader, a keyboard alone, voice control, a magnifier, a phone held at arm's length, or a browser with animation switched off. Where the website cannot do that for you, a person will. That commitment does not expire and it does not require you to explain why.

The standard we aim for

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We say "aim to conform" deliberately. No independent audit of this site has been commissioned yet, and a site that publishes property content supplied by third parties can drift out of conformance between reviews. Claiming full conformance without a test would be the kind of statement this page exists to avoid.

Where we fall short of that target and know it, it is listed under known limitations below rather than left for you to discover.

What this site does today

Structure and navigation

• Pages are built from semantic HTML with real landmarks — a banner header, a primary navigation region, a single main region, and a footer — so assistive technology can jump between them.
• Every page has exactly one first-level heading, and headings descend in order without skipping a level, so a screen reader's heading list reads as an outline of the page.
• A "Skip to main content" link is the first thing that receives focus on every page. It is hidden until focused, then appears at the top of the screen.
• Navigation regions carry distinguishing labels — primary, mobile, breadcrumb, and the footer's link groups — so they are told apart by name rather than by position.
• Breadcrumbs mark the current page, and the current section is marked in the main navigation, so your location is announced rather than only shown.
• Link text is written to make sense read out of context. You should not find a page of identical "learn more" links.

Keyboard and focus

• Everything interactive is reachable and operable with a keyboard alone: navigation, dropdown menus, the mobile menu, accordions, forms, and the back-to-top button.
• Desktop dropdown menus open on keyboard focus, not only on hover, so tabbing through the navigation reveals the sub-pages rather than skipping past them.
• The mobile menu button reports whether it is open, and pressing Escape closes the menu and returns focus to the button you opened it with.
• Accordions are real buttons, not clickable text. Each one reports its expanded state and is tied to the panel it controls; the panel is properly hidden from assistive technology when collapsed, so a screen reader does not read answers you have not opened.
• Focus is always visible. Keyboard focus draws a clear outline offset from the element; form fields show a colored border and a surrounding ring instead. Nothing on this site has its focus styling switched off.
• There are no keyboard traps and no time limits on any interaction.

Motion

• Content fades in gently as you scroll. If your operating system is set to reduce motion, that is respected: the animations are switched off, transitions are reduced to nothing, and smooth scrolling becomes an instant jump. Nothing is hidden as a result — the content simply appears.
• Nothing on this site auto-plays, flashes, blinks, moves on its own, or pops up over what you are reading.
• If JavaScript is switched off in your browser, every animated block is shown anyway. No content on this site depends on script in order to become visible or readable.

Layout, text, and zoom

• The layout is responsive and reflows to a single column on small screens, down to narrow phones — including the navigation, forms, card grids, and the footer.
• Type is sized in relative units so it scales with your browser's text size and with page zoom, rather than staying locked at a fixed pixel size.
• Wide content such as a comparison table sits in a container that scrolls on its own, so it never forces the whole page sideways.
• A print stylesheet strips the navigation, gradients, and decoration, and prints the address behind each external link, so a page you print or save as a PDF stays readable.

Color and contrast

• The palette is built around dark navy text on white or near-white, and white text on deep navy, with the intent of meeting the WCAG AA contrast ratio for body text and interface elements.
• Color is never the only signal. Form errors carry an icon and a written message as well as a color. Alerts carry an icon, a bold heading, and text. The active navigation item is marked for assistive technology, not just underlined. Required fields are marked in the page's code as required, so they are announced, rather than being indicated only by a red asterisk.

Images and icons

• Decorative graphics — background patterns, the skyline illustration, interface icons that sit beside their own label — are marked as decorative and hidden from assistive technology, so they are not read out as noise.
• Meaningful images get descriptive alternative text. The logo is announced as the brokerage name; the equal housing and licensing marks in the footer are labeled rather than silent.
• Our policy for property photography, as it is added: describe what a sighted visitor would learn from the picture — the style of the home, the view, the room — and never leave a meaningful image with an empty or filename-based description.

Forms and error messages

• Every field has a visible label that is properly associated with it, so clicking the label focuses the field and a screen reader announces it.
• Fields carry the correct autocomplete hints, so a browser or password manager can fill your name, email, and telephone number for you.
• When something is wrong, the message appears next to the field it applies to, in words. The field is programmatically marked invalid and pointed at its own error message, so assistive technology reads the reason along with the field.
• Summary messages at the top of a form announce themselves — a success confirmation politely, a problem immediately — and focus moves to the message so you are not left guessing whether the form submitted.
• Error text explains what to do, not just that something failed.

Known limitations

Every honest accessibility statement has this section. Here is ours.

• No independent audit yet. Testing to date has been done in-house with a keyboard, browser zoom, and reduced-motion settings. That is not the same as a formal WCAG 2.1 AA audit by a specialist, and we are not going to describe it as one.
• Third-party property search. The IDX or MLS search is not live on this site yet. When it is, the listing search, map, and property detail views will be generated by an outside provider inside our pages. We will ask that provider for its conformance documentation, but we do not write their code and cannot guarantee it. Until then — and afterwards, if their tool gets in your way — call us and we will search for you and read the results out.
• PDF documents. Disclosures, association documents, surveys, seller net sheets, and inspection reports frequently arrive from other parties as scans or untagged PDFs. Those may not be readable by a screen reader. We cannot re-tag every document we receive, but we can and will read any of them to you or send the contents in an accessible format on request.
• Third-party photography and floor plans. Images supplied by sellers, builders, and photographers arrive with no descriptions attached. We write the alternative text ourselves as listings are published, so very recently added material may still be waiting on that pass.
• Web fonts load from an outside service. The two typefaces come from Google's font service. If that service is blocked, slow, or unavailable, the site falls back to fonts already on your device. Everything remains readable, but spacing and line breaks will differ slightly from the intended design.
• Secondary text contrast. Some supporting text — small print, captions, footer legal text — is set in a lighter gray than the main body copy. We believe it meets the standard, but it is the part of the palette closest to the minimum, and it is on the list to re-measure at the next review.
• Maps and video. None are embedded today. If any are added, they bring their own accessibility characteristics, and this section will be updated when they do.

What we are doing about it

• Reviewing this statement, and re-testing the site, whenever a page or feature is added — not on an annual schedule that quietly slips.
• Testing new pages with the keyboard alone, at 200% browser zoom, and with reduced motion enabled, before they are published.
• Asking any vendor we contract — IDX provider, document platform, scheduling tool — for their accessibility conformance report before signing, and weighting it in the decision.
• Treating a reported barrier as a defect with a fix, rather than as feedback to be filed.

Tell us about a problem

If any part of this site is difficult or impossible to use, we want to hear about it — including the small things. You do not need to know the technical name for what went wrong.

It helps if you can tell us the page you were on, what you were trying to do, what happened instead, and — if you know it — the browser, device, or assistive technology you were using. If you cannot describe it easily, telephone and describe it in your own words; that works just as well.

Our commitment: an acknowledgement from a person within one business day, a plain answer about whether it can be fixed and roughly when, and — in the meantime — whatever you were trying to do, done for you by hand.

If the website will not do it, a person will

Nothing on this site is the only route to the service behind it. If a page, a form, or a document is not usable for you, telephone (386) 866-3406 and it will be handled directly. That includes:

• Searching for property to your criteria and reading the results — condition, layout, fees, flood zone, and what the photographs actually show — over the phone.
• Taking any enquiry, valuation request, or appointment by telephone instead of through a form, with no difference in how quickly it is dealt with.
• Sending disclosures, association documents, and contracts in a format that works for you, or reading them to you and explaining what each clause commits you to.
• Arranging showings and closings with the access, timing, or support arrangements you need — say what would help and it will be organized.
• Talking through the whole process from first showing to closing table without you having to read anything at all.

Requests for reasonable accommodation in a housing transaction are also covered by fair housing law, which we take seriously — see the fair housing statement in our Terms of Use.

---

Related: our Privacy Policy explains what this site collects and where it goes. The Terms of Use cover how the site may be used and when a brokerage relationship begins. To reach Scott Lee about a property rather than about this page, use the contact page.