Admin list filters: condition controls have no accessible names

Describe the Bug

Each condition row in the stock admin list filter builder renders four controls without accessible names:

• the field ReactSelect (.condition__field)
• the operator ReactSelect (.condition__operator)
• the icon-only remove button (.condition__actions-remove)
• the icon-only add-AND button (.condition__actions-add)

Screen-reader users encounter unnamed comboboxes and buttons, so they cannot tell which control chooses a field/operator or whether an icon adds or removes a condition. axe-core reports the resulting select-name / button-name findings as critical.

A downstream audit on Payload 3.85.1 observed this on 41 of 44 stock collection list views: 82 critical rule occurrences (41 list-route observations × the two rules; each occurrence contains the two affected nodes for that control type).

The controls are rendered without label props or text in Condition:

• field/operator selects: https://github.com/payloadcms/payload/blob/v3.85.1/packages/ui/src/elements/WhereBuilder/Condition/index.tsx#L140-L170
• remove/add buttons: https://github.com/payloadcms/payload/blob/v3.85.1/packages/ui/src/elements/WhereBuilder/Condition/index.tsx#L188-L216

Link to the code that reproduces this issue

https://github.com/payloadcms/payload/blob/v3.85.1/packages/ui/src/elements/WhereBuilder/Condition/index.tsx#L140-L216

This is stock admin markup, not application-specific code. A blank scaffold with any filterable collection renders the same WhereBuilder / Condition controls.

Reproduction Steps

1. Run pnpx create-payload-app@3.85.1 -t blank and create at least one document in a collection.
2. Open that collection's list view in the admin.
3. Open Filters and add one condition.
4. Inspect the two comboboxes and the plus / remove icon buttons, or run axe-core.
5. Observe that none of the four controls has an accessible name.

Which area(s) are affected?

area: ui

Environment Info

payload:         3.85.1
@payloadcms/ui:  3.85.1
Next.js:         16.2.10
Node:            24.20.0
Browser:         Chromium 152.0.7977.64 (agent-browser 0.35.1)
axe-core:        4.12.1

Possible fix

Give the field and operator ReactSelect controls localized labels (for example via aria-label / aria-labelledby) and give the two icon buttons localized add-condition / remove-condition accessible names. The icons can remain visual-only once the button names carry the meaning.

Start in packages/ui/src/elements/WhereBuilder/Condition/index.tsx around lines 140-216, where the field and operator ReactSelect controls and the add/remove buttons are rendered. Reproduce the issue with a blank Payload app and inspect the controls with axe-core. Done means all four controls have localized accessible names and the select-name and button-name findings are resolved.