(Accessibility) Ensures every ARIA input field has an accessible name error on range controls popover

[bhavyarm]

Kibana version: main

Browser version: chrome latest

Browser OS version: os x

Original install method (e.g. download page, yum, from source, etc.): from dev

Describe the bug: Range controls pop-over has a11y error for "Ensures every ARIA input field has an accessible name" and fails the test I am trying to add in #135085

Dashboard controls a11y tests
       Dashboard with options and range control panel popovers:

      Error: a11y report:
 
 VIOLATION
   [aria-input-field-name]: Ensures every ARIA input field has an accessible name
     Impact: serious
     Help: https://dequeuniversity.com/rules/axe/4.0/aria-input-field-name?application=axeAPI
     Elements:
       - <div class="euiRangeThumb euiRangeThumb--hasTicks" role="slider" aria-valuemin="101" aria-valuemax="1200" aria-valuenow="101" aria-disabled="false" tabindex="0" style="left: 0%;"></div>
       - <div class="euiRangeThumb euiRangeThumb--hasTicks" role="slider" aria-valuemin="101" aria-valuemax="1200" aria-valuenow="1200" aria-disabled="false" tabindex="0" style="left: 97.3109%;"></div>
       at AccessibilityService.assertValidAxeReport (/Users/bhavyarajumandya/Desktop/kibana_dev/kibana/test/accessibility/services/a11y/a11y.ts:76:13)
       at AccessibilityService.testAppSnapshot (/Users/bhavyarajumandya/Desktop/kibana_dev/kibana/test/accessibility/services/a11y/a11y.ts:49:10)
       at runMicrotasks (<anonymous>)
       at processTicksAndRejections (node:internal/process/task_queues:96:5)
       at Context.<anonymous> (test/accessibility/apps/dashboard_controls.ts:90:7)
       at Object.apply (/Users/bhavyarajumandya/Desktop/kibana_dev/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)
 
 

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[elasticmachine]

Pinging @elastic/kibana-accessibility (Project:Accessibility)

[Heenawter]

Closing in favour of #135466 because there are other related issues with the range slider component that are better handled all together :)