W3C home > Mailing lists > Public > public-apa@w3.org > June 2016

RE: scrolling and scroll bars

From: Matt King <a11ythinker@gmail.com>
Date: Wed, 8 Jun 2016 15:33:33 -0700
To: "'Fred Esch'" <fesch@us.ibm.com>, "'Bryan Garaventa'" <bryan.garaventa@ssbbartgroup.com>
Cc: "'Accessible Platform Architectures Working Group'" <public-apa@w3.org>
Message-ID: <010601d1c1d5$cb569920$6203cb60$@Gmail.com>
Screen readers read all content that is in the DOM but not explicitly hidden
from the AX tree, i.e., display:none, visibility:hidden, aria-hidden=true.

 

Screen readers (unlike magnifiers) do not care about visual scrolling as
long as scrolling is not adding to or removing from the DOM or changing
whether content is explicitly hidden. 

 

Matt

 

From: Fred Esch [mailto:fesch@us.ibm.com] 
Sent: Tuesday, June 7, 2016 11:06 AM
To: Matthew King <mattking@us.ibm.com>; Bryan Garaventa
<bryan.garaventa@ssbbartgroup.com>
Cc: Accessible Platform Architectures Working Group <public-apa@w3.org>
Subject: scrolling and scroll bars

 

Matt and Bryan,

For APA I have a task to review CSS Overflow Module Level 3
<https://www.w3.org/TR/css-overflow-3/> . A main feature of this doc is
defining and handling of scrollable areas. How does AT report scrollbars and
is it important for a non-sighted user to know whether an area is scrollable
or not? Another issue is do AT's report info that is visually clipped, that
is does the AT read the data as if it weren't visually clipped or does it
somehow try to represent only what is visible?






Regards, 

Fred Esch 
Watson, IBM, W3C Accessibility




Watson Release Management and Quality 

 





image001.png
(image/png attachment: image001.png)

Received on Wednesday, 8 June 2016 22:34:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 June 2016 22:34:05 UTC