Validation error: heading ordering

For Genesis the WCAG 2.0 AA guidelines where followed.
With in those guidelines it is ok to use an H2 before an H1.
What validator did you use?

You can also ask these questions the Genesis Slack #accessibility channel.
You can apply here: https://genesis.community/slack

Hi Rian,

Thanks. I tried several. The one that reported it was Total Validator (free version). This was the message I got:

P883 [WCAG2 1.3.1 (A)] Nest headings properly (H1 > H2 > H3) Heading elements must be ordered properly. For example, H2 elements should follow H1 elements, H3 elements should follow H2 elements, etc. Developers should not skip levels or use headings for presentation effects. See https://www.w3.org/TR/WCAG20-TECHS/F43.html (displayed in new window)

new_B:
What you have to take into consideration is: against what guidelines am I testing.
If you use WAVE you can choose if you validate agains what level of accessibility you want to check. see: https://wave.webaim.org/toolbar/
WCAG 2 AA is worldwide regarded as the standard for web accessibility.

Thanks, Rian.

With Total Validator, it also uses WCAG 2.0 AA–perhaps it’s a bug in the validation as all validators implement their checkers differently.

Just for my own knowledge, is there an exception in relation to WCAG 2.0AA for H2 before H1, etc. in certain circumstances? (e.g., skiplinks)