Re: WCAG vialations or accessibility enhancements

It's found in the advisory for 3.2.2 at G201: Giving users advanced warning
when opening a new window

On Feb 14, 2018 1:23 AM, "Ramakrishnan Subramanian" <ram.eict2013@gmail.com>
wrote:

> Dear Members,
> I hope it is appropriate to post this query here.
> I kindly request you to help me understand few of the accessibility
> related issues mentioned below.
> Whether these are treated as accessibility enhancement which would be
> helpful for the end user. Or accessibility violation.
> Heading order:
> Whether the following heading level is considered an accessibility
> violation? if yes, which criteria does this violate?
> The first heading level in the page is <h2> sample text </h2>
> The next heading level is <h5> sample text </h5>
>
> Landmark regions:
> When there are different content given inside two different aria
> region, with same aria label. Under which criteria this fails?
> <div role=”region” aria-label=”apple”>
> Apple related content goes here
> </div>
> <div role=”region” aria-label=”apple”>
> Bannana related content goes here
> </div>
> 3. Links which open in a new window:
> When there is no indication for the screen reader users for the link
> which opens in a new window, is that considered an accessibility
> violation? If yes, which criteria does this issue violate?
>
>
> --
>
> Thanks and Regards
> Ramakrishnan
>
>