E-mail List Archives
From: David Farough
Date: Aug 3, 2025 10:27AM
- Next message: Steve Green: "Re: Weird bug in both JAWS and NVDA (maybe)"
- Previous message: Laurence Lewis: "Re: WCAG 2.2 SC 4.1.3 Status Message – Error Handling Across Multi-Part Date Input"
- Next message in Thread: None
- Previous message in Thread: Sailesh Panchang: "Re: scrollable content accessibility"
- View all messages in this Thread
NON CLASSIFIÉ / UNCLASSIFIED
From: David Farough
Sent: Saturday, August 02, 2025 10:57 AM
To: Sailesh Panchang < <EMAIL REMOVED> >
Subject: RE: [WebAIM] scrollable content accessibility
Thanks so much for your response.
I have checked that option and it is on as expected.
I noticed in the Web aim newsletter that there was an article that seemed to address this issue.
Tabindex: What it is, how it works, and when to use it - Pope Tech Blog<https://blog.pope.tech/2025/07/01/tabindex-what-it-is-how-it-works-and-when-to-use-it/#scrollable-containters>
Check on the heading:
Add scrollable containers with CSS overflow property to tab order using tabindex=”0″
Any thoughts?
From: Sailesh Panchang < <EMAIL REMOVED> >
Sent: Friday, August 01, 2025 4:06 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Cc: David Farough < <EMAIL REMOVED> >
Subject: Re: [WebAIM] scrollable content accessibility
Hello David,
Specifically with JAWS, make sure this option is not accidently turned off:
Screen track virtual cursor:
"This option controls whether or not JAWS causes the screen to track the virtual cursor.
When JAWS does this, sighted users can more easily tell where you are on the Web page. Since Web pages do not have a cursor, like Microsoft Word does, this tracking feature works to keep the content you are viewing on screen. The default setting is on" (From JAWS Help).
Now given the myriad ways dynamic content gets coded, it is also likely the option does not work as expected in certain situations.
- Just my thought.
Sailesh Panchang
Email: <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
Deque Systems Inc | - Accessibility for Good | www.deque.com<http://www.deque.com/>
On Fri, Aug 1, 2025 at 3:23 PM David Farough via WebAIM-Forum < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >> wrote:
NON CLASSIFIÉ / UNCLASSIFIED
I am wondering if there is a good way to insure that content can be scrollable using the keyboard.
I like to be able to see the content as it is being read by my screenreader.
In our learning application, I often see content that is scrollable. When I get Jaws to read the content using the SayAll functionality all works well and I can see the content as Jaws is reading it.
When the focus gets to the end of the scrollable area I no longer can see the content as Jaws is reading it. The only way I can scroll the content is to use my mouse scroll wheel.
I have tried scrolling the page using Control + downarrow with no luck.
Is there a technique that can be used that will provide this functionality to keyboard and Access technology users?
I would like to be able to recommend something that would solve this issue to the content provider.
David Farough
Application Accessibility Coordinator
<EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
- Next message: Steve Green: "Re: Weird bug in both JAWS and NVDA (maybe)"
- Previous message: Laurence Lewis: "Re: WCAG 2.2 SC 4.1.3 Status Message – Error Handling Across Multi-Part Date Input"
- Next message in Thread: None
- Previous message in Thread: Sailesh Panchang: "Re: scrollable content accessibility"
- View all messages in this Thread