E-mail List Archives
Thread: Scripting Question: Content Not Appearing In Screen Reader View Of Page, But Can Tab To It
Number of posts in this thread: 7 (In chronological order)
From: Jim Homme
Date: Wed, Apr 29 2020 8:24AM
Subject: Scripting Question: Content Not Appearing In Screen Reader View Of Page, But Can Tab To It
No previous message | Next message →
Hi,
Since I am not a serious developer, but can examine code, I want to know what might cause content to be unreadable in the screen reader view of a page, but can be reachable, even using a screen reader. I can't show you a page for various reasons, but I can tab to some links on it, but cannot read to them with a screen reader. What should I look for in the source that could point me to what causes this?
Thanks.
Jim
==========
Jim Homme
Digital Accessibility
Bender Consulting Services
412-787-8567
https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
From: jeffgutsell
Date: Wed, Apr 29 2020 10:29AM
Subject: Re: Scripting Question: Content Not Appearing In Screen Reader View Of Page, But Can Tab To It
← Previous message | Next message →
It would help to know whether the content is generated after the page loads
or whether the content is interactive
Perhaps this content has its CSS display property set to none.
Jeff Gutsell
From: Amber Holladay
Date: Wed, Apr 29 2020 11:27AM
Subject: Re: Scripting Question: Content Not Appearing In Screen Reader View Of Page, But Can Tab To It
← Previous message | Next message →
Aria-hidden is the first thing I would look for. It will hide content from
the screen reader, but still be visible and allow TAB focus. If you have
already ruled that out, you may need to give more details on the type of
experience to get specific answers.
On Wed, Apr 29, 2020 at 10:29 AM < = EMAIL ADDRESS REMOVED = > wrote:
> It would help to know whether the content is generated after the page loads
> or whether the content is interactive
> Perhaps this content has its CSS display property set to none.
> Jeff Gutsell
>
>
>
From: glen walker
Date: Wed, Apr 29 2020 11:33AM
Subject: Re: Scripting Question: Content Not Appearing In Screen Reader View Of Page, But Can Tab To It
← Previous message | Next message →
Agree with Amber. It's often not an obvious thing, such as the link itself
having aria-hidden. It usually happens because a parent element (<div>)
has it set and it propagates down to all the child DOM elements.
On Wed, Apr 29, 2020 at 11:27 AM Amber Holladay <
= EMAIL ADDRESS REMOVED = > wrote:
> Aria-hidden is the first thing I would look for. It will hide content from
> the screen reader, but still be visible and allow TAB focus. If you have
> already ruled that out, you may need to give more details on the type of
> experience to get specific answers.
>
>
From: Mallory
Date: Wed, Apr 29 2020 3:00PM
Subject: Re: Scripting Question: Content Not Appearing In Screen Reader View Of Page, But Can Tab To It
← Previous message | Next message →
I recently was inspecting a page (but not with a screen reader), checking out what the chromes were spewing into their a11y tree. Hidden things are labelled as "Ignored". I found a star-rating system which had hidden text inside spans with the usual Itemprop attributes... but even after playing with CSS styles and removing class names until I could visually see the text, I could not figure out what was triggering that content as being labelled Ignored.
*most* of the time it's easy enough to find, but in browser devtools where you can see the a11y tree, you may have to move "up" to ancestors to find who is the culprit. But rarely, there are instances where it's difficult to determine.
cheers,
_mallory
On Wed, Apr 29, 2020, at 7:33 PM, glen walker wrote:
> Agree with Amber. It's often not an obvious thing, such as the link itself
> having aria-hidden. It usually happens because a parent element (<div>)
> has it set and it propagates down to all the child DOM elements.
>
> On Wed, Apr 29, 2020 at 11:27 AM Amber Holladay <
> = EMAIL ADDRESS REMOVED = > wrote:
>
> > Aria-hidden is the first thing I would look for. It will hide content from
> > the screen reader, but still be visible and allow TAB focus. If you have
> > already ruled that out, you may need to give more details on the type of
> > experience to get specific answers.
> >
> >
> > > > >
From: Patrick H. Lauke
Date: Thu, Apr 30 2020 6:32AM
Subject: Re: Scripting Question: Content Not Appearing In Screen Reader View Of Page, But Can Tab To It
← Previous message | Next message →
On 29/04/2020 22:00, Mallory wrote:
> I recently was inspecting a page (but not with a screen reader), checking out what the chromes were spewing into their a11y tree. Hidden things are labelled as "Ignored". I found a star-rating system which had hidden text inside spans with the usual Itemprop attributes... but even after playing with CSS styles and removing class names until I could visually see the text, I could not figure out what was triggering that content as being labelled Ignored.
>
> *most* of the time it's easy enough to find, but in browser devtools where you can see the a11y tree, you may have to move "up" to ancestors to find who is the culprit. But rarely, there are instances where it's difficult to determine.
In Chrome's Accessibility panel, beyond the a11y tree showing "Ignored",
you should also be able to see in the "Computed properties" when an
ancestor was set to hidden, and get a clickable reference to that ancestor
(along lines of Accessibility node not exposed / aria-hidden is true on
ancestor: div#info.style-scope.blah ...)
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: Mallory
Date: Sun, May 03 2020 7:43AM
Subject: Re: Scripting Question: Content Not Appearing In Screen Reader View Of Page, But Can Tab To It
← Previous message | No next message
Pat,
Not in this case (nothing is computed as hidden). If I can make a small reproduceable test case, I may have a chromium bug to file.
So additional advice for looking at hidden stuff, whether in devtools or via a screen reader: test multiple engines. When they don't agree with each other, it makes it easier to decide if something's a bug (or, sometimes, not a bug but still an issue of browser engines not agreeing on the same behaviour).
cheers,
_mallory
On Thu, Apr 30, 2020, at 2:32 PM, Patrick H. Lauke wrote:
...
> In Chrome's Accessibility panel, beyond the a11y tree showing "Ignored",
> you should also be able to see in the "Computed properties" when an
> ancestor was set to hidden, and get a clickable reference to that ancestor
>
> (along lines of Accessibility node not exposed / aria-hidden is true on
> ancestor: div#info.style-scope.blah ...)
>
> P
>
> --
> Patrick H. Lauke