WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXT]Noscript getting flagged

for

From: Vaibhav Saraf
Date: Aug 4, 2020 7:30AM

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 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 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
>>
>>
>> >> >> >> >>
>