Accessibility Statement

Our accessibility target: WCAG 2.2 Level AA

Arcesso aims for arcesso.ai to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG is the international standard for accessible web content, published by the World Wide Web Consortium (W3C). Level AA is the level most laws and policies point to.

We want everyone to be able to read about our work, compare options and contact us, whether they use a keyboard, a screen reader, voice control, magnification or a small phone screen. Accessibility is part of how we build the site, not a fix we add afterward.

This statement is our own description of our approach. It is not a certification, and no third party has certified the site as conforming. We test against the standard ourselves and fix what we find.

How we build and test arcesso.ai for accessibility

Arcesso builds accessibility into the site's code and checks it on every release. The site is server-rendered HTML, so content is available without waiting for scripts, and it works with assistive technology people already use.

• One H1 per page and a logical heading order, with landmarks and a skip link.
• Real buttons and links, labeled form fields and errors announced to screen readers.
• Full keyboard access with a visible focus indicator that is never hidden.
• Text contrast of at least 4.5:1, and pages that reflow at 320 pixels wide.
• Touch targets of at least 24 by 24 pixels, and reduced motion honored.
• No CAPTCHA puzzles, and a contact form that never asks for the same data twice.
• Automated checks with axe-core and Lighthouse, plus manual keyboard and screen reader tests.

No accessibility overlay widgets

Arcesso does not use accessibility overlay widgets or toolbars on arcesso.ai. Overlays are scripts that claim to fix accessibility automatically by changing a page after it loads. Many disabled users and accessibility experts report that overlays interfere with the screen readers and settings people already rely on, and they do not make a site conform to WCAG.

Instead, we fix accessibility at the source: in the HTML, the design and the content. Your own browser, operating system and assistive technology settings, such as zoom, high contrast, larger text and screen readers, should work on the site as you expect.

If something about the site gets in the way of the tools you use, please tell us, and we will treat it as a bug to fix.

Known limitations

There are no known accessibility limitations on arcesso.ai at launch. We tested the site's page templates, navigation, contact form and footer before publishing, and fixed the issues we found.

Some content comes from third parties. The call booking tool is provided by Calendly, and links go to other sites such as LinkedIn and the sources behind statistics we cite. We check that these are usable, but we do not control their code. If a third-party tool blocks you, contact us and we will book your call or send the information another way.

If you find a barrier, please report it to info@arcesso.ai. We will add confirmed issues to this section, with the date found and the planned fix, until they are resolved.

How to report a barrier and when we will respond

If any part of arcesso.ai is hard to use, tell us and we will fix it or give you the content another way. Email info@arcesso.ai with the subject "Accessibility", or call +1 (754) 423-0349 during US Eastern or Central business hours.

Arcesso responds to accessibility reports within 5 business days. The response will confirm the issue, say what we will do and give a target date for the fix. If you need information from the site in the meantime, we will send it in a format that works for you, such as plain text by email, or talk it through by phone.

• The page address (URL) where you found the problem.
• What you were trying to do, and what happened.
• The browser, device and assistive technology you use, if you are comfortable sharing.

Review history and ongoing testing

This statement was last reviewed on 2026-10-13, when arcesso.ai launched. We review it, and retest the site, at least every quarter and after any major change to the site's design or templates.

Automated accessibility checks run on every release, and a release that introduces a critical issue does not ship. Manual testing with a keyboard and with screen readers such as VoiceOver and NVDA happens before launch and at each quarterly review. Third-party embeds are included in that review.

When we change this statement, we update the review date above and in the page header, and note any new known limitations. We build client software to the same WCAG 2.2 AA target when a project calls for it.