Point Copilot at the accessibility failures a visual review would miss

Review the SavedSearchDropdown component on the /reports page for accessibility, grounded in the actual markup below, not a
general checklist recited without checking whether each item actually applies here.

MARKUP OR DIFF
The current render output of SavedSearchDropdown.tsx, pasted below, including its button and list markup.

INTERACTION PATTERN
a disclosure dropdown — a button that reveals a list of options and should close on Escape or an outside click

CONTRAST CONTEXT
Text color is var(--text-secondary) at #6b7280 on a white background in light theme.

EXISTING CONVENTIONS IN THIS CODEBASE
This codebase uses the useFocusTrap hook from lib/a11y/focus-trap.ts for every existing modal and dropdown.

CHECK EACH OF THESE AGAINST THE ACTUAL MARKUP, NOT IN THE ABSTRACT
1. Keyboard operability — every interactive element reachable and operable using Tab, Shift+Tab,
   Enter, and Escape where relevant, in an order that matches the visual reading order. For
   a disclosure dropdown — a button that reveals a list of options and should close on Escape or an outside click specifically, name the exact keyboard behavior expected — for example, a
   modal should trap focus inside itself while open and return focus to the element that opened it
   on close, not merely be reachable by Tab like a normal element on the page.
2. Screen-reader semantics — whether the actual elements used communicate their role and state
   correctly without a screen reader running, based purely on the markup: a clickable div with no
   role or button semantics is not a button to assistive technology no matter how it looks, and a
   toggle with no aria-pressed or aria-expanded state gives a screen-reader user no way to know
   whether it is currently on or off, open or closed.
3. Focus visibility — whether a visible focus indicator survives on every interactive element in
   this markup, specifically checking for any outline removal in the styles without a replacement
   focus style, which is one of the single most common and most damaging accessibility regressions
   in UI code.
4. Color contrast — using Text color is var(--text-secondary) at #6b7280 on a white background in light theme., state the actual contrast ratio for text against
   its background and against WCAG's 4.5:1 threshold for normal text and 3:1 for large text, rather
   than a subjective 'looks readable' judgment; if the exact colors are not resolvable from what is
   given, say so rather than estimating a ratio that sounds authoritative but is not actually
   computed.
5. Error and status messaging — if this pattern can show an error or a status change, confirm it is
   announced to a screen reader, not just rendered visually, since a validation error that only
   appears as a red border communicates nothing to someone who cannot see the border appear.

OUTPUT
For each of the five checks: PASS or a specific FINDING with the exact line or attribute at fault
and the concrete fix, not a general recommendation to add ARIA attributes. If a disclosure dropdown — a button that reveals a list of options and should close on Escape or an outside click
or This codebase uses the useFocusTrap hook from lib/a11y/focus-trap.ts for every existing modal and dropdown. makes a check inapplicable to this markup, say so explicitly
rather than silently omitting it.

Match any fix to This codebase uses the useFocusTrap hook from lib/a11y/focus-trap.ts for every existing modal and dropdown. already used elsewhere in this codebase rather than
introducing a second, differently styled way of solving the same accessibility requirement.