[EuiDualRangeSliders] Slider handles need accessible labels in popovers and two-handle sliders

[1Copenut]

Describe the problem, pt. 1 - dual range sliders in popovers
The inputs with range in dropdown dual range sliders have two range slider handles that need accessible labels. Screenshot attached below.

These dropdowns are not keyboard accessible by design. Keyboard users (and screen reader users who navigate with a keyboard) interact with the ranges by changing values of the number inputs. However, users who use a mouse with screen reader would have a harder time using this interface because they could still use the unlabeled range slider controls.

Describe the problem, pt. 2- dual range sliders
The dual range sliders not in popovers have an accessible aria-label but it's being inherited from the EuiRange and it's not as meaningful as labeling the sliders individually. This doesn't feel as critical for single elem[role="slider"] range sliders, but moreso when there are two.

Steps to reproduce

1. Make sure you have the axe browser plugin installed on Chrome, FF, or Edge
2. Load https://eui.elastic.co/#/forms/range-sliders#inputs-with-range-in-a-dropdown in your favorite browser
3. Click to open the single or double range slider in a dropdown
4. Open your dev tools and run an axe check
5. Verify two errors "Ensures every ARIA input field has an accessible name"

Possible code change

# src/components/form/range/dual_range.tsx#712
# Minimum EuiRangeThumb

const minThumbAccessibleLabel = (
  <EuiI18n
    token="euiRange.minimumThumbAccessibleLabel"
    default="Minimum range slider"
  />
);

<EuiRangeThumb
  min={Number(this.lowerValue)}
  ...
  aria-label={minThumbAccessibleLabel}
/>

# src/components/form/range/dual_range.tsx#731
# Maximum EuiRangeThumb

const maxThumbAccessibleLabel = (
  <EuiI18n
    token="euiRange.minimumThumbAccessibleLabel"
    default="Maximum range slider"
  />
);

<EuiRangeThumb
  min={Number(this.lowerValue)}
  ...
  aria-label={maxThumbAccessibleLabel}
/>

Environment

• MacOS Monterey latest
• Chrome latest
• Production docs site

WCAG or Vendor Guidance (optional)

• Understanding SC 4.1.2: Name, Role, Value (Level A)
• ARIA input fields must have an accessible name
  

Screenshots or Trace Logs

[github-actions]

👋 Hi there - this issue hasn't had any activity in 6 months. If the EUI team has not explicitly expressed that this is something on our roadmap, it's unlikely that we'll pick this issue up. We would sincerely appreciate a PR/community contribution if this is something that matters to you! If not, and there is no further activity on this issue for another 6 months (i.e. it's stale for over a year), the issue will be auto-closed.

[github-actions]

❌ Per our previous message, this issue is auto-closing after having been open and inactive for a year. If you strongly feel this is still a high-priority issue, or are interested in contributing, please leave a comment or open a new issue linking to this one for context.