Overview

Open Accessible groups visual, reading, navigation, and motion-related controls so visitors can adjust the experience to their needs.

This article is written as a practical reference for what accessibility tools are included?. Follow the steps in order the first time, then use the headings and screenshots as landmarks when you return later. The screenshots reflect the current Open Accessible Cloud layout shown in September 2026, so labels may move slightly as the dashboard evolves.

Before you begin

Confirm that you are signed in to the correct account and, when applicable, that the organization selector in the upper-right corner shows the organization you intend to manage. If you work with multiple websites, verify the domain before changing settings.

For changes that can affect a live site, take note of the current configuration first. A screenshot, copied setting value, or short change note makes rollback much easier. Avoid changing unrelated options at the same time; smaller changes are easier to verify and troubleshoot.

How to use this answer in practice

Use this article as a starting point rather than a substitute for testing your own site. Accessibility depends on the page structure, content, components, browser, assistive technology, and the way visitors interact with the experience.

When a question affects a specific implementation, verify the result with keyboard navigation, zoom, responsive layouts, and the assistive technologies that matter to your audience. Document any site-specific behavior so your team has a repeatable reference.

Step-by-step workflow

  1. Start with the exact question you need to answer. Identify whether it concerns the widget, the host website, the browser, or the Open Accessible Cloud account.
  2. Reproduce the behavior in a clean session. A private browser window helps separate saved preferences and cached files from the underlying behavior.
  3. Test the important interaction path. Include keyboard access, zoom, and mobile layout when relevant.
  4. Compare the result with the explanation in this article. Site-specific scripts, styles, or security policies may explain differences.
  5. Keep a short reproducible example. Include the page, browser, steps, and expected result if you need support.

How to verify the result

Do not stop at the saved confirmation. Reload the relevant page and confirm the visible state matches what you intended. If the change affects authentication, open a fresh browser session. If it affects a website, test the public page as a visitor rather than only the dashboard.

For user-facing changes, check with keyboard input, browser zoom, and a narrow mobile viewport. Watch for overlapping fixed controls, clipped dialogs, focus that disappears off-screen, or settings that reset unexpectedly after navigation.

Troubleshooting

If the dashboard does not match these screenshots, first confirm you are in the correct organization and account. UI labels can also change over time, so look for the same concepts—Websites, API Keys, Secrets, organization settings, or Profile & 2FA—even if the exact placement has moved.

For website problems, check the browser developer console and network panel. Look for blocked scripts, 404 responses, Content Security Policy errors, or requests being stopped by a consent manager or extension. For account problems, try a private window and verify that the email address and organization membership are correct before resetting credentials.

Use descriptive names for websites, keys, tokens, secrets, and team roles. Clear names reduce the chance of editing the wrong resource and make audits easier months later. Avoid putting sensitive values into screenshots, tickets, documentation, or public source repositories.

Review access periodically. Remove old sessions, unused credentials, and team members who no longer need access. For production integrations, document where each credential is used and who is responsible for rotating it.

Next steps

After completing what accessibility tools are included?, return to the documentation home page and use search to find the next related workflow. Search accepts normal phrases, so queries such as “website branding,” “2FA,” “API token,” or “installation” will surface related guides.

If you are troubleshooting, keep the page URL, browser name, approximate time, and a concise set of reproduction steps. Those details make it much easier to distinguish an account configuration issue from a website integration issue.