This statement explains how we approach accessibility on our website, the standard we build to, what we know is not solved yet, and how to reach a person if something does not work for you. It applies to our website at https://blugency.co and to our product application at https://app.blugency.co.
1. Our commitment
We build for founders, and founders are not a narrow group of people using a narrow set of devices. Someone reading our site may be using a screen reader, navigating entirely by keyboard, zooming to two hundred percent, using a browser in dark mode, or turning off animation because motion makes them ill. All of that is ordinary, and the site should work in every one of those cases.
Our commitment is straightforward. We treat an accessibility barrier as a defect in the site rather than a limitation of the person using it. When you tell us about one, we fix it or we give you another way to get the same thing done.
We also promise not to overstate where we are. This page tells you what we have actually built and what we have not yet verified. We would rather publish an honest statement with gaps in it than a confident claim we cannot stand behind.
2. Definitions
Blugency, we, us and our mean Blugency LLC, a New Mexico limited liability company.
Site means our website at https://blugency.co, including our blog.
Application means our product application at https://app.blugency.co. It runs on separate infrastructure from the Site, and this statement covers both.
WCAG means the Web Content Accessibility Guidelines, the international standard published by the World Wide Web Consortium that most organizations, courts and settlements use as the reference point for website accessibility.
Booking Widget means the Cal.com scheduling widget embedded on the Site, which you use to book a meeting with us.
3. The standard we are working toward
We work toward WCAG 2.2 Level AA, and we treat WCAG 2.1 Level AA as the floor beneath it, because 2.1 Level AA is the version most often used as the reference point in United States settlements and court decisions. That is our target, and we use it as the yardstick when we build a page and when we review one.
We want to be precise about what that sentence means and what it does not mean.
It means we treat WCAG 2.2 Level AA as the definition of done, and that when we find something on the Site that falls short of it, we treat that as a bug.
It does not mean we are claiming conformance. We do not describe the Site as fully accessible, as certified, as audited, or as compliant. No government body certifies private business websites as accessible in the United States, and a conformance claim is only worth as much as the audit standing behind it. When an independent audit supports a conformance claim, we will publish the claim, the date it was made, the scope it covered, and who carried it out.
We have not commissioned an independent accessibility audit. No outside firm has assessed the Site against WCAG 2.2 Level AA, and nothing on this page should be read as saying that one has. We would rather tell you that in one plain sentence than let a page of careful wording imply an audit that never happened. We have committed to engaging a specialist accessibility firm to carry one out within 12 months of launch, and when it is done we will publish what it covered, what it found, and what we changed because of it.
Nothing on this page limits any right you have under the Americans with Disabilities Act or under any state accessibility or consumer protection law.
We also do not use an accessibility overlay or plugin as a substitute for building the Site properly. Those tools do not make an inaccessible site accessible, and we will not present one as though it did.
4. How we build the Site
These are the things we build the Site to do. Each one is a requirement we hold a page to before it ships, and each one is something you can hold us to.
Keyboard navigation. You should be able to move through the Site and use its interactive elements with a keyboard, without needing a mouse or a trackpad.
Semantic structure. Pages use real headings in a sensible order rather than text that is merely styled to look like a heading, which is what lets a screen reader move through a page by section.
Labelled form controls. The fields in our forms carry proper labels, so that assistive technology can tell you what each field is for.
Color contrast. We hold text and interface elements to the contrast levels WCAG sets, and we do that in every color theme the Site offers rather than in only one.
Respect for your system settings. The Site follows your operating system's color scheme preference, so it opens in the mode you already chose. It also respects the reduced motion setting, so if you have asked your device to cut down animation, the Site does not override you.
Automated checks. Automated accessibility checks are part of how we build and review pages, and we treat what they flag as work to do rather than noise.
Two honest caveats. The first is that automated checks catch a real but limited portion of what matters, so we do not publish a score and we would not treat a perfect one as settling the question. A page can pass every automated check and still be painful to use with a screen reader. The second is that this list describes the standard we build to, and we are confirming feature by feature that the current deployment meets all of it before this page says anything stronger than that.
5. Known limitations
5.1 Content embedded from other companies
Some of what you see on the Site comes from another company and runs inside its own frame. The clearest example is the Booking Widget, which is provided by Cal.com and is how you schedule a meeting with us.
We do not control the markup, the behavior or the accessibility of embedded content of this kind. We can choose whether to use a provider and we can raise problems with it, but we cannot fix its code. If the Booking Widget does not work for you, you do not have to fight with it: email us at support@blugency.co and we will arrange the meeting with you directly.
5.2 What we have not verified yet
No independent audit. No outside firm has audited the Site against WCAG 2.2 Level AA. We have not commissioned one yet, we have committed to doing so within 12 months of launch, and that is why section 3 makes no conformance claim.
Assistive technology testing. We have not published the list of screen readers, browsers and operating systems the Site has been tested with. That list is worth more than a score, and we would rather name real combinations and real dates than describe our testing in general terms.
Content published over time. Our blog grows, and content added over months is where text alternatives for images and clear link text tend to slip. If you find an image without a useful description, a document you cannot read, or a link whose purpose is unclear, tell us and we will fix it or give you the content another way.
The Application. This statement covers the Application at https://app.blugency.co as well as the Site, and the commitments in sections 1, 6 and 7 apply there in full. What sections 3, 4 and 5 describe, though, is work we have done against the Site. We have not yet carried out the same review of the Application, so treat everything in this section as applying there with more force rather than less. If you hit a barrier in the Application, email us at the same address and we will fix it or get you to the same result another way.
6. How to report an accessibility problem
Email support@blugency.co and put "Accessibility" in the subject line.
It helps if you can tell us the address of the page, what you were trying to do, and what happened instead. If you are comfortable saying which browser, device or assistive technology you were using, that usually makes the fix faster. None of it is required, and we will never ask you to prove anything about yourself in order to be helped.
We acknowledge every accessibility report within 2 business days, and we send you a substantive response within 10 business days. A substantive response means telling you what we found, what we are doing about it and when, or giving you another way to complete what you were trying to do while we work on the fix. Accessibility reports are owned by our support team at support@blugency.co, and they are answered rather than logged and forgotten.
We publish no telephone number, for accessibility or for anything else, because we would rather commit to a channel we monitor properly than list a number nobody answers. Email reaches a person, and section 7 sets out the other ways we can deal with you if the Site is not usable for you.
7. Other ways to reach us
If any part of the Site is unusable for you, you do not need to use the Site to deal with us.
Email. Write to support@blugency.co. Our support team can take your question, arrange a meeting time with you directly instead of through the Booking Widget, and take you through buying a service from beginning to end, all by email. That is a real route rather than a courtesy sentence: an inquiry, a booking and a purchase can each be completed entirely by email for anyone who cannot use that part of the Site, and support owns it.
Post. Write to us at the address in the Contact section below, and tell us how you would like us to reply.
Nothing you can do on the Site is something we cannot do with you another way. If you run into a wall, that is our problem to solve, not a reason for you to give up on the transaction.
Canceling through the same channel you bought through. If you buy a service that renews and you bought it by email with us, you can cancel it the same way, by replying in that same email thread. There are no further steps, our support team processes it, and we treat it as received on the day you send it. We will not send you somewhere else to do it, we will not put a retention conversation in front of it, and we will not ask you to give notice in advance. Our Purchasing Terms set out how cancellation works generally.
8. How we review this statement
We review this statement when we make a significant change to the Site, when someone reports a barrier that changes what is true here, and at least once every 12 months, when we also re-test the Site, so that this page does not quietly go stale. Blugency owns that review, and the address for any question about it is support@blugency.co. The date this page was last updated is shown with the version number at the top of the page, and that date is the date of the last review.
You will find this page from our legal index at /legal, which lists every legal document we publish, and the footer of every page on the Site links to that index alongside our Terms of Service, Purchasing Terms, Privacy Policy and Legal Disclaimer.
Contact
Accessibility questions, reports and requests for help using any part of the Site:
Email: support@blugency.co
Post: Blugency LLC, 1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110, United States
Our Privacy Policy explains what we do with the information in a message you send us, and our Terms of Service covers your use of the Site generally.