E-mail List Archives
Thread: Noscript getting flagged
Number of posts in this thread: 5 (In chronological order)
From: Vaibhav Saraf
Date: Mon, Aug 03 2020 9:00AM
Subject: Noscript getting flagged
No previous message | Next message →
Hi Jared,
As an auditor how can we check we check the accessibility of <noscript>
content? Any directions?
Thanks,
Vaibhav
On Sat, 4 Jul 2020 at 03:02, Jared Smith < = EMAIL ADDRESS REMOVED = > wrote:
> Colleen -
>
> There's nothing inherently wrong with <noscript>, WAVE is simply alerting
> you to its presence with the prompt to ensure that any content presented
> via the script and via the noscript be accessible.
>
> Thanks,
>
> Jared
> > > > >
From: Jared Smith
Date: Mon, Aug 03 2020 9:56AM
Subject: Re: [EXT] Noscript getting flagged
← Previous message | Next message →
Vaibhav Saraf wrote:
As an auditor how can we check we check the accessibility of <noscript>
content? Any directions?
To test <noscript> content it is typically best to disable JavaScript in the browser. Disabling JavaScript is getting more difficult these days. This article describes how to do it in Chrome - https://developers.google.com/web/tools/chrome-devtools/javascript/disable The Web Developer Toolbar also (I believe) still provides an easy option to disable JavaScript.
Thanks,
Jared
From: Vaibhav Saraf
Date: Tue, Aug 04 2020 7:26AM
Subject: Re: [EXT]Noscript getting flagged
← Previous message | Next message →
Hi Jared,
In my case developer has written nothing between
<noscript> opening and closing tags. Probably they were following some
template which had the same thing or some automated code checkers complied
them to.
After disabling the JS the page looks the same. That'll pass our test right?
One thing which I am not able to understand is that why they have given
'aria-hidden=true' in the noscript tag. Will the noscript text or whatever
will bump into a screen reader navigation. And if yes then what will happen
when the user is using screen reader on a JS disabled browser (one like me
after disabling JS), will the user not miss out on the info given in the
noscript tag ?
Thanks,
Vaibhav
On Mon, 3 Aug 2020 at 21:26, Jared Smith < = EMAIL ADDRESS REMOVED = > wrote:
> Vaibhav Saraf wrote:
>
> As an auditor how can we check we check the accessibility of <noscript>
> content? Any directions?
>
> To test <noscript> content it is typically best to disable JavaScript in
> the browser. Disabling JavaScript is getting more difficult these days.
> This article describes how to do it in Chrome -
> https://developers.google.com/web/tools/chrome-devtools/javascript/disable
> The Web Developer Toolbar also (I believe) still provides an easy option to
> disable JavaScript.
>
> Thanks,
>
> Jared
>
>
> > > > >
From: Vaibhav Saraf
Date: Tue, Aug 04 2020 7:30AM
Subject: Re: [EXT]Noscript getting flagged
← Previous message | Next message →
I asked about the aria-hidden thing because over the net I came across many
pages where they were indicating to use <noscript aria-hidden=true> but
they weren't explaining the reason.
Also noscript tag was introduced long before aria so I believe we should
have a better way to implement the tag.
Thanks,
Vaibhav
On Tue, 4 Aug 2020 at 18:56, Vaibhav Saraf < = EMAIL ADDRESS REMOVED = > wrote:
> Hi Jared,
>
> In my case developer has written nothing between
> <noscript> opening and closing tags. Probably they were following some
> template which had the same thing or some automated code checkers complied
> them to.
>
> After disabling the JS the page looks the same. That'll pass our test
> right?
>
> One thing which I am not able to understand is that why they have given
> 'aria-hidden=true' in the noscript tag. Will the noscript text or whatever
> will bump into a screen reader navigation. And if yes then what will happen
> when the user is using screen reader on a JS disabled browser (one like me
> after disabling JS), will the user not miss out on the info given in the
> noscript tag ?
>
> Thanks,
> Vaibhav
>
>
> On Mon, 3 Aug 2020 at 21:26, Jared Smith < = EMAIL ADDRESS REMOVED = > wrote:
>
>> Vaibhav Saraf wrote:
>>
>> As an auditor how can we check we check the accessibility of
>> <noscript>
>> content? Any directions?
>>
>> To test <noscript> content it is typically best to disable JavaScript in
>> the browser. Disabling JavaScript is getting more difficult these days.
>> This article describes how to do it in Chrome -
>> https://developers.google.com/web/tools/chrome-devtools/javascript/disable
>> The Web Developer Toolbar also (I believe) still provides an easy option to
>> disable JavaScript.
>>
>> Thanks,
>>
>> Jared
>>
>>
>> >> >> >> >>
>
From: Jared Smith
Date: Tue, Aug 04 2020 7:48AM
Subject: Re: [EXT]Noscript getting flagged
← Previous message | No next message
Vaibhav Saraf wrote:
> After disabling the JS the page looks the same. That'll pass our test right?
<noscript> is not for accessibility purposes. It instead provides an alternative for when JavaScript is disabled. Learn more at https://webaim.org/techniques/javascript/alternatives#noscript It is a best practice to ensure that if JavaScript is not available that an alternative to any JavaScript-dependent content or functionality be provided - and that alternative also be accessible. If your page looks and functions that same with JavaScript disabled, then there would be no use for <noscript> at all.
> I asked about the aria-hidden thing because over the net I came across many pages where they were indicating to use <noscript aria-hidden=true> but they weren't explaining the reason.
I can think of no purpose for placing aria-hidden=true on <noscript>. This would hide the content within <noscript> from screen reader users that also have JavaScript disabled, which would occur somewhere around .7% of the time (https://webaim.org/projects/screenreadersurvey8/#javascript).
I'd strongly suggest that you and your team receive web accessibility training to provide you foundational accessibility knowledge.
Jared