E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 5 (In chronological order)

From: Sumit Patel
Date: Mon, Oct 03 2022 1:06PM
Subject: Links open in new tab / window
No previous message | Next message →

Hai all,

We would always come across links which open in new tab / window in a webpages.
If there is visual clue to indicate it and no alternative for screen
readers, yes it is a violation of 1.1.1 Non-text content. But, what if
there is no visual indication ?
Still do we need to fail it and ask for both visual and alternative
that it opens in new tab / window ?
or a best practice ?


And another scenario I have is screen reader is reading clickable for
non-interactive elements. I think this is due to the presence of click
event in the code. Not sure any other reason.
Do we need to fail this ? or best practice
Because I have observed differences when we see it in different screen
readers and again in different browsers.


Thanks in advance
Sumit.

From: glen walker
Date: Mon, Oct 03 2022 1:44PM
Subject: Re: Links open in new tab / window
← Previous message | Next message →

If a link opens in a new window and there isn't a visual clue that it will
do so, then there isn't a WCAG requirement to specify it. It's generally a
good UX practice to do so but it's not strictly required.

NVDA will say clickable if the element (or a parent or other ancestor
element) has a mouse click event handler. It's a clue to the screen reader
user that the element is probably missing an appropriate role but is still
interactive. It's not always an automatic failure but there's a good
chance it's a problem. You'll have to inspect the code.

From: Sumit Patel
Date: Mon, Oct 03 2022 11:53PM
Subject: Re: Links open in new tab / window
← Previous message | Next message →

Thanks for your reply.

Yes, if NVDA says clickable and it is interactive, will fail by asking the role.
But, what if the element is non-interactive ? do we need to fail it ?



On 04/10/2022, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> If a link opens in a new window and there isn't a visual clue that it will
> do so, then there isn't a WCAG requirement to specify it. It's generally a
> good UX practice to do so but it's not strictly required.
>
> NVDA will say clickable if the element (or a parent or other ancestor
> element) has a mouse click event handler. It's a clue to the screen reader
> user that the element is probably missing an appropriate role but is still
> interactive. It's not always an automatic failure but there's a good
> chance it's a problem. You'll have to inspect the code.
> > > > >

From: wolfgang.berndorfer@zweiterblick.at
Date: Tue, Oct 04 2022 2:23AM
Subject: Re: Links open in new tab / window
← Previous message | Next message →

„changes of context“ are defined with the following note:
“Opening a new window … are examples of changes of context.”
https://www.w3.org/WAI/WCAG21/Understanding/on-focus.html#dfn-changes-of-context

So, target="_blank" should be a AAA violation according to SC 3.2.5 Change on Request, if there is no indication on screen (visual clue) and for SR (text clue) for the mechanism.
https://www.w3.org/TR/WCAG21/#change-on-request

Wolfgang

-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of glen walker
Sent: Monday, October 3, 2022 9:44 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Links open in new tab / window

If a link opens in a new window and there isn't a visual clue that it will do so, then there isn't a WCAG requirement to specify it. It's generally a good UX practice to do so but it's not strictly required.

NVDA will say clickable if the element (or a parent or other ancestor
element) has a mouse click event handler. It's a clue to the screen reader user that the element is probably missing an appropriate role but is still interactive. It's not always an automatic failure but there's a good chance it's a problem. You'll have to inspect the code.

From: Rheaume, Geneviève (CHRC/CCDP)
Date: Tue, Oct 04 2022 1:37PM
Subject: Re: Links open in new tab / window
← Previous message | No next message

Hi,

Here are the links to the WCAG techniques that actually mention the best way to open a page in a new browser window. This technique is related to the success criteria 3.2.1 and 3.2.5
Opening new windows and tabs from a link only when necessary : https://www.w3.org/WAI/WCAG21/Techniques/general/G200

Here is the proper way to apply this technique if you want to open a new tab or a new window :
Using the target attribute to open a new window on user requests and indicating this in link text : https://www.w3.org/WAI/WCAG21/Techniques/html/H83

Geneviève


-----Original Message-----
From: glen walker < = EMAIL ADDRESS REMOVED = >
Sent: Monday, October 3, 2022 3:44 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Links open in new tab / window

If a link opens in a new window and there isn't a visual clue that it will do so, then there isn't a WCAG requirement to specify it. It's generally a good UX practice to do so but it's not strictly required.

NVDA will say clickable if the element (or a parent or other ancestor
element) has a mouse click event handler. It's a clue to the screen reader user that the element is probably missing an appropriate role but is still interactive. It's not always an automatic failure but there's a good chance it's a problem. You'll have to inspect the code.