G201: referenced in 3.2.1 On focus and 3.2.2 On input but does it really make sense?

[juliemoynat]

Hi,

I do not understand why G201 is referenced in 3.2.1 On focus and 3.2.2 On input.

• G201 is only about links opening in a new window.
• 3.2.1 is about user interface component receiving focus. (I saw G200: why is 3.2.1 On Focus referenced? #4043 where it was already discussed with G200.)
• 3.2.2 is about forms.

Does it make sense in any way?

[vartikapandey53]

I agree that G201 is not directly related to 3.2.1 (On Focus) and 3.2.2 (On Input)

Also, I believe

• It is better suited as a best practice for external links opening in a new window.
• The G201 advisory could benefit from further clarification, particularly for links opening in new tabs within web applications.
• Currently, G201 does not distinguish between external links and internal links (same domain) that align with user workflows.
• As CodersBlock points out, while notifying users about new tabs is essential for accessibility, excessive notifications can overwhelm users, especially those relying on screen readers.

[juliemoynat]

Actually, I think that G201 should be a sufficient technique for SC 3.2.5 Change on Request because it is.

And I think that G201 is very similar to H83 (sufficient technique for SC 3.2.5) and that both could be merged into one technique. H83 and G201 use different arguments and examples but they are fundamentally the same.

Warning users of links opening in a new window is not dedicated to external links. It's for all links which opens in a new window.

You can have an internal link opening in a new window: for example, a privacy policy link before the submit button of a form.