-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
separator is not output #237
Comments
Can reproduce in JAWS 2024, Chrome Version 119.0.6045.200 (Official Build) (64-bit), Firefox 120.0.1 (64-bit). Note: NVDA does announce |
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 <hr role=”presentation”>
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 <hr> 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 GitHub<#237 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKX5QZVIETKVUQEUJLFOWMLZLMFTHAVCNFSM6AAAAABKRVGXPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJVGQ2DGMJRG4>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
|
ARIA spec:
|
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)
@davidengebretson<https://github.com/davidengebretson>
ARIA spec:
Authors MAY make a separator focusable to create a widget<https://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 GitHub<#237 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKX5QZVWTNE2I7B7RQLSHBDZLNMHXAVCNFSM6AAAAABKRVGXPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJWGM3TCNRRG4>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Summary
separator is not output
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
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
The text was updated successfully, but these errors were encountered: