standards-support
standards-support copied to clipboard
separator is not output
Summary
separator is not output
- save as HTML file:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>separator</title>
</head>
<body>
<a href="#">test</a>
<div tabindex='0' role='separator' aria-valuemax=30 aria-valuemin=0 aria-valuenow=15 aria-label=separator aria-orientation=vertical>---</div>
</body>
</html>
- Navigate with Tab key, arrow keys, quick navigation
Expected result
Correct output of role, label and value (aria-valuemin, -max, -now), alignment (aria-orientation) for the different navigation methods (tab, linear reading, quick navigation (F)) and in the element overview (INS+F5). See: https://www.w3.org/TR/wai-aria-1.2/#separator
Actual result
- IE: tab: only output as "menu", reading with arrow keys: no output
- Chrome: tab: correct role, label, valuemin, valuemax, but also as "menu" and misleading operating instructions for menus, no output of valuenow; reading with arrow keys: no output of the values
- Firefox ESR: correct, but without valuenow
- Chrome, Firefox: INS+F5: wrong output of "activated not activated" due to aria-orientation
Additional Information
JAWS version and build number
JAWS 2019.1906.10
Operating System and version
Windows 10
Browser and version:
Internet Explorer 11.0.9600.19400 Chrome 75.0.3770.100 Firefox 60.8.0 ESR
Can reproduce in JAWS 2024, Chrome Version 119.0.6045.200 (Official Build) (64-bit), Firefox 120.0.1 (64-bit).
Test case
In chrome aria-valuenow is not announced, in firefox it is announced if the user presses enter when the separator has focus.
Note: NVDA does announce aria-valuenow but does not announce orientation/valuemin/valuemax
Imported into ADO as bug 89570
I’m curious; of what use is the proposed functionality to blind users? Personally separators are just a pain in my ears as I navigate web pages and emails. So much so that our design system at the university I work at has changed the default of html for HR’s to
And, why would you ever place a tabindex=0 on a semantic element? I don’t understand the code example nor why it would be important to “fix” the issue outlined.
The issue I see is that JAWS users should be able to remove the
element from all webpages and emails presented in the DOM. HR’s are scurvy on JAWS navigation efficiency. They are visual fluff that mean nothing to me as a blind screen reader user.
All my not so humble opinion, of course 😊, David
From: BrettLewisVispero @.> Sent: Monday, July 8, 2024 3:16 PM To: FreedomScientific/standards-support @.> Cc: Subscribed @.***> Subject: Re: [FreedomScientific/standards-support] separator is not output (#237)
Imported into ADO as bug 89570
— Reply to this email directly, view it on GitHubhttps://github.com/FreedomScientific/standards-support/issues/237#issuecomment-2215443117, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKX5QZVIETKVUQEUJLFOWMLZLMFTHAVCNFSM6AAAAABKRVGXPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJVGQ2DGMJRG4. You are receiving this because you are subscribed to this thread.Message ID: @.@.>>
@davidengebretson
ARIA spec:
Authors MAY make a separator focusable to create a widget that both provides a visible boundary between two sections of content and enables the user to change the relative size of the sections by changing the position of the separator. A variable separator widget can be moved continuously within a range, whereas a fixed separator widget supports only two discrete positions. Typically, a fixed separator widget is used to toggle one of the sections between expanded and collapsed states.
https://www.w3.org/TR/wai-aria-1.2/#separator
That’s wild. I never knew. Thanks for sharing!
Plus, the link you provided will give me all sorts of pleasure reading while I’m not working. 😊 There’s SO much information in the ARIA spec that I’ve never fully researched. I usually just dive into the spec every once in a while from an “as needed” perspective.
Again, much appreciated.
From: JAWS-test @.> Sent: Monday, July 8, 2024 8:46 PM To: FreedomScientific/standards-support @.> Cc: David Engebretson @.>; Mention @.> Subject: Re: [FreedomScientific/standards-support] separator is not output (#237)
@davidengebretsonhttps://github.com/davidengebretson
ARIA spec:
Authors MAY make a separator focusable to create a widgethttps://www.w3.org/TR/wai-aria-1.2/#widget that both provides a visible boundary between two sections of content and enables the user to change the relative size of the sections by changing the position of the separator. A variable separator widget can be moved continuously within a range, whereas a fixed separator widget supports only two discrete positions. Typically, a fixed separator widget is used to toggle one of the sections between expanded and collapsed states.
https://www.w3.org/TR/wai-aria-1.2/#separator
— Reply to this email directly, view it on GitHubhttps://github.com/FreedomScientific/standards-support/issues/237#issuecomment-2216371617, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKX5QZVWTNE2I7B7RQLSHBDZLNMHXAVCNFSM6AAAAABKRVGXPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJWGM3TCNRRG4. You are receiving this because you were mentioned.Message ID: @.@.>>