WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Few web accessibility related vialations:

for

From: Joe Chidzik
Date: Feb 14, 2018 1:51AM

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

>