Accessibility statement.
Floburn Inc wants floburn.com to work for everyone who uses it, including people who use assistive technology: a screen reader, screen magnification, voice control, or a keyboard in place of a mouse. We measure the site against the Web Content Accessibility Guidelines (WCAG) 2.2, a standard for making web pages usable by people with disabilities, at Level AA, the middle of its three levels. The site partially conforms: Some parts do not yet fully meet the standard. This page says which parts we know about, and how to reach us when something on the site gets in your way.
- Standard
- WCAG 2.2 Level AA
- Status
- Partially conforms
- Evaluated
- September 26, 2026
- Last reviewed
- September 26, 2026
To report a problem or ask for help, email hello@floburn.com or call (425) 952-9128. Relay calls are welcome: If you are deaf, hard of hearing or deaf-blind, or have a speech disability, you can dial 711 in the United States, and a communications assistant will connect the call and pass on what each side says.
The standard: We measure the site against WCAG 2.2 Level AA.
WCAG, the Web Content Accessibility Guidelines, is a technical standard for making web pages usable by people with disabilities. It is published by the World Wide Web Consortium (W3C), the international organization that develops standards for the web. We use version 2.2, in the edition W3C published on December 12, 2024.
WCAG sets three levels: A, AA and AAA. Level AA includes every Level A requirement and adds more, such as a minimum color contrast for text and a visible highlight on whichever link or button the keyboard is on.
Status: Floburn.com partially conforms to WCAG 2.2 Level AA.
Partially conforms means that some parts of the site do not yet fully meet the standard. The parts we know about are listed below, under known problems.
How we checked: We evaluated the site ourselves, most recently on September 26, 2026.
No one outside Floburn has audited the site. We ran automated accessibility tests on the site’s public pages, at a phone width and at a desktop width, including measurements of color contrast. We also tested the pages using a keyboard alone, at 200% zoom, and in a window 320 pixels wide, where text should rewrap with no sideways scrolling.
This statement covers the public pages of floburn.com. The private pages we share with individual clients and counsel were not part of the evaluation.
Known problems: What we know does not work yet.
The booking calendar on the contact page
The calendar for booking a free 30-minute call with us is provided by Cal.com, a scheduling service, and runs inside our contact page. We cannot change its code, and it does not meet WCAG 2.2 Level AA. We found five problems in it.
- A screen reader is not told which day you have selected.
- A screen reader is not told which weekday a date falls on: The calendar shows the weekday only by the column a date sits in, and names each day only by its number.
- When a required field on its booking form is left empty, the error message is not marked for a screen reader to announce.
- The highlight on a time slot that has keyboard focus is faint.
- At desktop width, the last visible line of the text describing the call, beside the calendar, is faded until you scroll that text. We wrote that text, and we will shorten it so that none of it is faded.
Because the calendar is part of the contact page, the contact page does not conform to WCAG 2.2 Level AA.
If the calendar gets in your way, send us two or three times that suit you and we will book the call for you. Use the form further down the contact page, email hello@floburn.com, or call (425) 952-9128.
Six problems in our own pages
- Some section titles are not marked up as headings, so a screen reader’s list of headings leaves them out, or places a section under the wrong one.
- Where a page lists the steps of how we work with you, the text a screen reader is given runs each step’s name straight into the short note beside it, with no space between them.
- The photo at the top of the home page has no text description, although the caption over it refers to it.
- One journal post quotes a sentence in Spanish that is not marked as Spanish, so a screen reader may pronounce it with English rules.
- In some paragraphs, a link is marked only by a faint underline, so it can be hard to tell apart from the text around it.
- On the page about producing the record for a lawyer’s letter, a two-row comparison is laid out like a table but not marked up as one, so a screen reader does not tie each value to its column heading.
These six are in our own code, and we will fix them.
Other ways to reach us: Email us, call us, or write to us with the contact form.
Email hello@floburn.com, call (425) 952-9128, or write to us with the form on the contact page.
Relay calls are welcome. A relay service lets someone who is deaf, hard of hearing or deaf-blind, or who has a speech disability, make a phone call through a communications assistant. In the United States, dialing 711 reaches a relay service.
Documents and calls: Accessible documents and captioned calls, on request.
Any document we send you, such as a report, a proposal or an agreement, is available in an accessible format on request. Tell us which format works for you.
You can take the free 30-minute call by phone or video (Google Meet). On video, Meet shows live captions to anyone who turns them on, and we can help you turn them on at the start if you ask. On the phone, relay (711) calls are welcome. Or we can take your questions in writing instead. Ask when you book, or at any time before the call.
How fast we respond: A reply within two business days. A fix, or another way to get the same thing done, within 45 days.
When you tell us that something on the site gets in your way, we reply within two business days. Within 45 days of your message, we fix the problem, or we offer you another way to get the same thing done.
It helps to tell us which page you were on and what you were trying to do.
Privacy: We use what you send to answer you and fix the problem.
When you contact us about accessibility, we use what you send to answer you and to fix the problem, and we keep it as our privacy policy describes. You do not need to tell us anything about a disability to get help.
Google Analytics, which we use to count visits to our other public pages, does not record visits to this page. The privacy policy covers everything else.