Accessibility Statement

Last updated: [LAST UPDATED DATE]

We want aslanconsulting.co to be usable by as many people as possible, including people who use a keyboard, a screen reader, magnification, or reduced-motion settings.

Our commitment

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. WCAG is the international standard for making web content usable by people with disabilities, and Level AA is the level most commonly referenced in law and policy. This is an ongoing effort rather than a finished state: as we change the site, we check the changes, and we fix what we find.

What we have done so far

• Semantic HTML. The page is built with real headings, lists, buttons and landmarks, in a logical reading order, so assistive technology can describe the structure instead of guessing at it.
• A keyboard-operable booking flow. The “Book a revenue diagnostic” dialog can be opened, filled in, navigated and closed with the keyboard alone. It is marked up as a dialog, focus moves into it when it opens and returns to the control you came from when it closes, the Escape key closes it from anywhere, and each answer option can be chosen with a letter key as well as a click.
• Visible focus states. Keyboard focus is shown with a high-contrast outline that we have not removed, so you can always see where you are on the page.
• Reduced motion is respected. If your operating system is set to reduce motion, the site honors the prefers-reduced-motion setting: the page intro, scroll animations, the headline reveal and the live feed motion are turned off or reduced rather than played.
• Attention to color contrast. We check text and background pairings for contrast, we avoid using color as the only way of conveying meaning, and we pair status colors with text labels.
• Resizable, reflowing text. The layout is responsive and uses relative units, so it holds up when text is enlarged or the window is narrow.
• Labelled controls and decorative graphics. Controls such as the close button, the verdict tabs and the question-and-answer accordion carry accessible names and announce their open or selected state. Purely decorative icons, dots and illustrations are hidden from screen readers so they do not add noise.

Known limitations

We would rather tell you about these than let you discover them:

• Motion-heavy sections. The home page uses scroll-driven effects, including a pinned hero and a stack of cards that move as you scroll. With reduced motion turned off, some people may find this uncomfortable. Turning on your system’s reduce-motion setting removes most of it.
• Focus is not trapped inside the booking dialog. While the dialog is open, pressing Tab enough times can move focus onto the page behind it, and that background content is not currently hidden from screen readers. Escape still closes the dialog and puts focus back where you left it. Fixing this properly is on our list.
• The live signal feed announces itself. The feed is decorative and repeats on a loop, and it is currently marked as a polite live region, which means a screen reader will read out each new row as it arrives. That can get noisy, and we are reviewing whether to silence it. Nothing on the site exists only inside the feed, so you are not missing information if you ignore it.
• Long single-page layout. The home page is long, and reaching a later section with a keyboard or screen reader can take a while. The navigation links jump directly to each section.
• We have not completed a full independent audit. Our checks so far are our own. We have not yet had a third-party accessibility audit or formal testing across the full range of assistive technologies, so there are almost certainly issues we have not found.
• Third-party content. Our typeface is loaded from an external provider. If that request is blocked or slow, text falls back to a system font, which can change the look of the page.

Tell us about a problem

If you hit a barrier on aslanconsulting.co, please email [CONTACT EMAIL]. It helps us a great deal if you can include:

• the page or section where it happened;
• what you were trying to do;
• what went wrong; and
• the browser, operating system and any assistive technology you were using.

We will acknowledge your message, tell you what we found, and fix what we can. Where a fix is going to take time, we will say so and give you a realistic sense of when, rather than going quiet.

Another way to get the same information

You should never have to fight the site to reach us or to learn what we do. If any part of this site does not work for you, email [CONTACT EMAIL] and we will send the same information in another format, such as plain text, a large-print document, or the body of an email. You can also start a revenue diagnostic conversation entirely by email, with no need to use the booking form at all.

Contact