E-mail List Archives
Thread: Few web accessibility related vialations:
Number of posts in this thread: 3 (In chronological order)
From: Ramakrishnan Subramanian
Date: Tue, Feb 13 2018 1:17PM
Subject: Few web accessibility related vialations:
No previous message | Next message →
Dear Members,
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">
mango 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 for your inputs,
Ramakrishnan
--
Thanks and Regards
Ramakrishnan
From: Joe Chidzik
Date: Wed, Feb 14 2018 1:51AM
Subject: Re: Few web accessibility related vialations:
← Previous message | Next message →
Hi Ramakrishnan,
Using headings out of sequence is not a strict WCAG 2 violation. e.g.
<h2>Articles</h2>
...
<h5>Story 1</h5>
What is important for headings is:
# if it looks like a heading, it should be a heading, using one of the defined HTML heading elements (or the appropriate ARIA heading markup)
# The visual structure is conveyed by the heading levels e.g. the main heading on the page, has a more important (lower HTML heading number) than sub headings, and so on.
It is generally bad practise to skip heading levels, purely because there may be some confusion for screenreader users who may think they have missed content if they hear a jump from heading level 2 to heading level 5. I say this anecdotally as it would carry greater weight coming from a screenreader user. So ensuring heading levels are sequential would be an enhancement.
Landmark regions with different content by the same aria-label. I've not come across this exact scenario, but would possibly log it under either 1.3.1 as it describes the relationship between the region, and the content. Or 2.4.6: Heading and labels, though this would be a stretch as this is more for visual headingslabels, but could see it being used here as the label does not sound like it is describing the content adequately.
Links which open in a new window.
I would not fail this against WCAG 2. If however there was a visual indicator that a link opened in a new window, but this was not conveyed to screenreader users (e.g. a new window icon without alt text), then I would fail this against 1.1.1 Non text content. Otherwise, all users get the same experience of no new window alert, so this would be more of a UX issue.
Cheers
Joe
. The visual
> -----Original Message-----
> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> Behalf Of Ramakrishnan Subramanian
> Sent: 13 February 2018 20:18
> To: = EMAIL ADDRESS REMOVED =
> Subject: [WebAIM] Few web accessibility related vialations:
>
> Dear Members,
> 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">
> mango 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 for your inputs,
> Ramakrishnan
>
>
> --
>
> Thanks and Regards
> Ramakrishnan
> > > http://webaim.org/discussion/archives
>
From: Lovely, Brian
Date: Wed, Feb 14 2018 7:02AM
Subject: Re: Few web accessibility related vialations:
← Previous message | No next message
Joe Chidzik said: " if it looks like a heading, it should be a heading"
I would amend this to: "if it functions like a heading, it should be a heading" In the same way that the functional heading with the largest size type may not function as the pages H1, a large font, bold text string may not actually function like a heading in the page structure.
The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.