Cloud Console 2023.12 Accessibility Update: Focus Still Escapes the Cloud Shell Editor Modal

Answer to the Core Questions

1. Is the focus‑trap issue a documented known problem?

At present there is no public record of the Cloud Shell editor modal focus‑trap defect in the 2023.12 release notes or in the Google Issue Tracker. The behaviour you describe—Tab cycling that exits the modal and reaches background console elements—is a classic client‑side focus‑trap bug, not an intentional design change. It is therefore most likely a regression that has slipped through the 2023.12 accessibility updates.

2. Can restrictive IAM policies hide accessibility UI or live‑region announcements?

IAM controls access to GCP resources and APIs, not the rendering of ARIA attributes, focus management, or live‑region announcements in the Cloud Console front‑end. A policy that removes a user’s ability to view a page will simply block that page from loading; it does not selectively suppress screen‑reader announcements or keyboard focus behaviour on a page that does load.

3. How do I report and track this defect so it lands in a specific Console release?

Follow these steps to create a trackable bug report:

1. Open the Cloud Console in a browser that you use for daily work (e.g., Chrome, Edge, or Safari). Verify the footer shows 2023.12 or newer.
2. Open Cloud Shell and click Open editor to launch the modal.
3. Press Tab repeatedly and observe the focus leaving the modal. Note the exact element that receives focus next.
4. Open the Help menu (question mark icon) and choose Send feedback. In the feedback form, include:
   • Console channel (stable or preview)
   • Footer version string
   • Browser and OS details
   • Screen‑reader (if any) and its version
   • Exact reproduction steps (as above)
   • Screenshots or screen‑recording that show focus moving outside the modal
   • Any attempt to reproduce in an incognito window or a different browser
5. After submitting feedback, create a public issue in the Google Issue Tracker (issuetracker.google.com). Use the template for accessibility bugs, reference the feedback ID, and add the same reproduction details.
6. Tag the issue with cloud-console and accessibility, and set the component to UI – Cloud Console. This makes it visible to the product team and allows you to track its status across releases.

Once the issue is filed, you can monitor its progress in the Issue Tracker and receive updates when a fix is merged into the stable or preview channel.

Isolation Steps (Optional but Recommended)

To confirm that the problem is not caused by a custom IAM policy or a local configuration, repeat the reproduction in:

• Incognito/Private browsing mode to avoid cached UI state.
• A different browser (e.g., Firefox if you normally use Chrome).
• Both the stable and preview channels of the Console.

If the focus still escapes the modal in all environments, the defect is almost certainly a product bug rather than a side effect of IAM or user settings.

Next Diagnostic Detail Needed

To refine the recommendation, could you let us know which Console channel you are currently using (stable or preview) and whether you have tried reproducing the issue in an incognito window? This information will help determine whether the problem is channel‑specific or a broader regression.