Heads-up: Drupal.org issues and updates planned from AS-OACR-001

[AlexU-A]

Purpose

@mgifford, I plan to post the Drupal.org issue reports and updates below from
AS-OACR-001. I wanted to give you a heads-up and a chance to flag duplicate,
scope, component, or wording concerns first.

I will handle the Drupal.org filings and comments. I am not asking you to post
them or assigning you an evaluation, issue-maintainer, or approval role.
Nothing listed below had been posted when I opened this issue.

The complete review context is in
PR #59, including the exact
Drupal 11.4.4 test target, sample limits, outcome map, and evidence-custody
boundary.

Current status

@mgifford merged PR #59 into main on August 26, 2026, as
e097dea.
The public review package
is therefore now in the upstream repository. This issue remains the active
tracker for the later Drupal.org filings and comments; no final Drupal.org
links are recorded here yet.

Evidence and replication

The canonical evidence and replication section in PR #59
links the immutable evaluation report, outcome map, finding records, OpenACR
artifacts, and render-verification receipt. AS-OACR-001 used the
Zivtech accessibility-skills repository,
which is public and open source under the
GNU GPL v3.
The PR links its pinned workflow and evidence contracts for teams that want to
conduct a new, independently performed evaluation using the same method. The
repository does not contain the private AS-OACR-001 evidence corpus.

The public record supports review of the documented mapping and regeneration
checks; it does not independently verify or enable re-performance of the
historical observations. A new evaluation creates its own evidence and outcomes
against a separately frozen target; it does not confirm AS-OACR-001.

Six new Drupal.org issues I intend to file

1. Block Layout Configure Links Do Not Include Their Visible Label in the Accessible Name
   — finding a11y_claro_configure_label_not_in_name; no exact existing issue
   was found.
2. Claro Block Layout Empty-Region Text Fails Minimum Contrast
   — finding a11y_claro_empty_region_contrast; closed issue
   #3293469 recorded the
   same detector result but did not track the surviving visual defect as a
   dedicated issue.
3. Navigation Top Bar Completely Obscures Focused Breadcrumb Links
   — finding a11y_navigation_breadcrumb_focus_obscured; related issue
   #3491044 covers
   Navigation top-bar rendering but not complete keyboard-focus obstruction.
4. Navigation Focus Tooltips Cannot Be Dismissed With Escape
   — finding a11y_navigation_focus_tooltip_not_dismissible; related issues
   #3197758 and
   #3541728 do not
   record this focus-triggered tooltip defect.
5. Navigation Home Logo Has No Visible Keyboard-Focus Indicator
   — finding a11y_navigation_logo_focus_not_visible; a prior observation
   appears in
   #3443571 comment 29,
   but that closed issue addressed the mobile focus trap rather than this
   surviving defect.
6. Olivero Mobile Local-Tabs Trigger Uses an Insufficient Focus Indicator
   — finding a11y_olivero_tabs_trigger_focus_indicator; related issues
   #3153260 and
   Olivero #3125062 do
   not record the current .tabs__trigger result.

Three existing Drupal.org issues I intend to update

• Drupal core #3587668:
  add the
  current Claro bulk-action contrast reproduction
  from Drupal 11.4.4.
• Drupal core #3577361:
  add the
  current Navigation content-edit reflow reproduction.
• Drupal core #2280035:
  add the
  current Status report reflow reproduction.

What I would like Mike to check

Please flag any item that should use an existing Drupal.org issue instead of a
new filing, belongs in a different component or project, or overstates what the
bounded evidence supports. I will post the final issue reports and comments,
then update this tracker with their Drupal.org links.

These reports are remediation records and traceability links. Their status,
discussion, or eventual resolution cannot change the frozen AS-OACR-001
criterion outcomes or OpenACR adherence terms. The evaluation covers one local
Drupal 11.4.4 Standard installation and does not establish a Drupal-wide
conformance result.

[mgifford]

These look good. I've comment in Slack. Probably should bring those over here.