Accessibility
We want everyone to be able to use this site, including people who browse with a screen reader, a keyboard, magnification, or voice control. If any part of it gets in your way, we want to hear about it, and we will fix it.
The standard we build to
We work toward the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is the target for this site and for the rebuild that follows it.
We are not claiming we have arrived. Saying “this site is fully compliant” would be easy, and it would not be true. What we can tell you is what we have already fixed, what we know is still rough, and how to reach a person.
What we have already fixed
Pinch-zoom works again. The site was telling every phone and tablet not to allow zooming, on every page. If you needed to make the text bigger to read it, you could not. That restriction is gone.
The play button on the homepage has a real name. It was a link with nothing in it but an icon, so a screen reader announced it as nothing at all. It now announces what it does.
Heading levels run in order. The homepage jumped from a level 2 heading straight to level 4, which breaks the outline people use to navigate a page by headings. Fixed.
Everything in the gallery has a name now. Forty-six links in our gallery announced nothing at all to a screen reader. Every one of them now says what it opens.
The booth pages describe their images. Fourteen photos on the exhibit booths page had no description. The seven before-and-after sliders had no name either, and no instructions for anyone using a keyboard instead of a mouse. All of it is labelled.
The next and previous buttons on our news pages say what they do. They were arrows with nothing behind them.
The share buttons on our articles say what they do. Every article carried three share links that were an icon and nothing else, so a screen reader announced three links with no names. That is fifty-four links across eighteen articles. Each one now names the network it shares to.
The logo link has a name, and on four pages the logo is visible again. The logo at the top and bottom of every page is a link home, and it announced nothing. On our terms of service, do not sell, ads reporting and page-not-found pages the logo image was not loading at all, so there was nothing to see and nothing to announce. Both are fixed.
The “how did you find us” menu on our quote form works with a keyboard. That form swaps the standard dropdown for a custom one, and the custom version could not be reached by tabbing at all. If you do not use a mouse, that field was shut to you. It now takes keyboard focus and opens, moves and selects with the arrow and enter keys.
Each of those is a real change with a date behind it, not a claim. They landed on September 8, 9 and 10, 2026.
What we know is still rough
Not all of our page content sits inside proper landmark regions yet, so jumping straight to the main content is harder than it should be on some pages.
Several of our older page templates still skip a heading level, which makes the page outline harder to navigate by headings than it should be.
We use tools from other companies, including the spam protection on our contact form and embedded video. We do not control their markup, and some of it is not accessible.
We test with automated tools. As of September 10, 2026 we have checked all 42 pages in our sitemap that way, plus a page-not-found page and our quote form with its pop-up open, and all 43 come back with zero violations against the WCAG 2.0 and 2.1 Level A and AA rules those tools cover. That is the whole sitemap now, not a sample of it. It is still not the whole story: automated tools only catch part of what matters, and we have not yet done a full manual review or sat with someone using a screen reader to work through the site end to end. Until we do, treat our testing as partial, because it is.
We would rather list those than pretend they are not there.
Tell us about a barrier, or skip the site entirely
If something here stops you, call 702-331-9977, or use our contact page, or email hello@jettheagency.com. Tell us the page and what happened, and we will look into it and come back to you.
We list three routes on purpose. Any one of them reaches a person, and none of them needs JavaScript turned on.
If it is easier, do not fight the website at all. Call or email, and a person will take your event details and put a quote together with you. That option is always open, and it is not a lesser version of the service.
What happens next
We are not going to give you a date, because we do not want to hand you one and miss it. What we will do is keep fixing what we find and what you tell us, and hold the same WCAG 2.1 AA target through the rebuild of this site that is already underway.
This statement was last reviewed on September 10, 2026.