PROBLEM Innovation theme's template generates HTML5 warnings

[Maribe]

validations != bug

I agree that the validation doesn't show an error/bug but a warning, so nothing fatal, but it still indicates that some of the code doesn't comply with the W3C standards.

validation is bullshit for the most part.

I definitely don't agree that validation is "bullshit for the most part":
if validation is bullshit then what's the reference? Where/how to check standard's compliance?
Standards are what everybody can and must rely on and comply with in the world of "open standards" and validation engines are very valuable indicators of (non)compliance, even if some of them perform/check better than others.
If validator.nu engine is not the best one to use, could you suggest a better validator?

granted fixing it would be nice.

Thanks. I agree and I'm working on it.
Having read different comments on the <article> and <section> sectioning elements, the <main> grouping element and on sectioning/outlining in general, my general idea is that a solution might be to alter template.php by replacing:

Code:

<article>
                        <section>
                                
                                <!-- title and content -->
                                <h1><?php get_page_title(); ?></h1>
                                <?php get_page_content(); ?>
          
                        </section>
</article>

by:

Code:

<main>
                        <article>
                                
                                <!-- title and content -->
                                <h1><?php get_page_title(); ?></h1>
                                <?php get_page_content(); ?>

                        </article>
</main>

where <main> is used to group the content as well as to indicate that this is indeed the main content
and <article> is used for sectioning & outlining.
This looks like it would be a correct way to handle a page consisting of just a single block of page content with a single matching page title wrapped in a top-level <h1> heading.
I also think that it might be consistent with the original author's intententions...

I'll put this to the test and report back.

Handy links:
- Editor's Draft (W3C, 10 July 2014): http://www.w3.org/html/wg/drafts/html/CR/
headings and sections, outlining: http://www.w3.org/html/wg/drafts/html/CR...d-sections
<article> : http://www.w3.org/html/wg/drafts/html/CR...le-element
<section> : http://www.w3.org/html/wg/drafts/html/CR...on-element
<main> : http://www.w3.org/html/wg/drafts/html/CR...in-element

- Living standard (WHATWG, 8 July 2014): definitions and nice examples:
headings and sections, outlining: http://www.whatwg.org/specs/web-apps/cur...sections-2
<article> : http://www.whatwg.org/specs/web-apps/cur...-element-2
<section>: http://www.whatwg.org/specs/web-apps/cur...-element-2
<main>: http://www.whatwg.org/specs/web-apps/cur...-element-2