AX: VoiceOver does not announce proper descriptive information of time over 'seek slider' while navigating via swipe gestures.

• Component: Accessibility
• Status: RESOLVED MOVED

Created attachment 423385 [details]
Video

Note: Same issue occurs for all the similar video players present in scope URL's.


PWD Impact:

Screen reader dependent user will be impacted as VoiceOver does not announce proper descriptive information of time over 'seek slider' while navigating via swipe gestures. This issue will confuse the end user.
 

Test Environment:


OS: iOS(14.3)
Browser: Safari
Screen Readers: VoiceOver

URL:

https://www.microsoft.com/en-sg/p/surface-studio-2/8sbjxm0m58t4?Invisibiliarevelare=true&activetab=Overview


Repro Steps:

Step 1:  Enable VoiceOver and Open the above URL in Safari browser. 
Step 2:  "Rise above the ordinary" page will appear on the screen.
Step 3: Navigate to video player present inside "Overview" tab 
Step 4: Activate "Full screen" button. The screen will turn to full screen mode.
Step 5: Navigate to "seek slider' control using swipe gestures.
Step 6: Observe whether VoiceOver announce proper descriptive information of time over 'seek slider' while navigating via swipe gestures or not.

 

Actual Result:

VoiceOver does not announce proper descriptive information of time over 'seek slider' while navigating via swipe gestures.
VoiceOver announces as "Current position, zero, thirty- two , adjustable, swipe up/down with one finger to adjust the value"

Expected Result:

VoiceOver should announce proper descriptive information of time over 'seek slider' while navigating via swipe gestures.
VoiceOver should announce as "Seek slider, Current position, thirty-two seconds of 1 minutes 6 seconds, adjustable, swipe up/down with one finger to adjust the value"


Note:

Same issue does not replicate for Android+Talkback.



MAS reference:
MAS 1.3.1 – Info and Relationships
 
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html

[Radar WebKit Bug Importer]

<rdar://problem/75490540>

Created attachment 423386 [details]
Screenshot

[Brent Fulgham]

The fix for this issue was needed outside the WebKit project, therefore this is being resolved as 'Moved'.

The relevant team was unable to reproduce the issue.