Viewing 6 replies - 1 through 6 (of 6 total)
  • Fixing errors is always a good thing. So lets look at the first error.
    1) Go to your site and view the source of the page.
    2) Copy it and paste it into a text editor.

    so the first error says:

    Error: End tag aside seen, but there were open elements.
    From line 287, column 1; to line 287, column 8
    /a></div>?</aside> </d

    so go fine line 287 and find the beginning of the <aside> which is on line 285 – copy the block of code and paste it into a new text editor window and you will have;

    </div></aside><aside id="text-3" class="widget widget_text">			<div class="textwidget"><div style="text-align: center;">
    <a target="_blank" href="https://www.copyrighted.com/copyrights/view/kxdj-2y1c-1h4g-g6ot"><img src="https://res.cloudinary.com/angora/image/upload/v1456621666/Copyrighted_qys8q7.png" title="Bayu Angora ? All Rights Reserved" alt="Bayu Angora ? All Rights Reserved" width="150" height="40"/></a></div>
    </aside>			</div><!-- .widget-area -->

    Now lets make it pretty by putting each HTML element on its own line and get ride of anything before the <aside…> and you get:

    <aside id="text-3" class="widget widget_text">
    	<div class="textwidget">
    		<div style="text-align: center;">
    			<a target="_blank" href="https://www.copyrighted.com/copyrights/view/kxdj-2y1c-1h4g-g6ot">
    				<img src="https://res.cloudinary.com/angora/image/upload/v1456621666/Copyrighted_qys8q7.png" title="Bayu Angora ? All Rights Reserved" alt="Bayu Angora ? All Rights Reserved" width="150" height="40"/>
    			</a>
    		</div>
    </aside>

    If you look, you have a missing </div> in that text widget.

    If you go fix it, that error will be gone, now do the same investigation for the others.

    Hi,

    Most themes on markeplaces don’t pass, but html 3 is a bit oldated.

    That being said, unless you have specific issues, it’s easeier than ever to make a theme compliant.

    It will never be 100% compliant though, unless you plan to use 300 hours for blinds and deafs that won’t ever see any menu.

    Choices are yours. HTML5 is not a miracle, and giving an option to go text bigger always make me laaugh. A text engine to read menus, would be better.

    Thread Starter bayu-angora

    (@bayu-angora)

    Thanks for answer. I will try to fix it.

    Moderator James Huff

    (@macmanx)

    unless you plan to use 300 hours for blinds and deafs that won’t ever see any menu.

    @digico-paris If you could be less derogatory towards those with impairments, we’d really appreciate it. There are plenty of ways to make sites accessible so that everyone can “see” them without spending “300 hours.” (also, not sure where you got the idea that someone with a hearing impairment would never be able to see a menu)

    In fact, many recent themes already come as prepared for screen readers as possible, thanks to some amazing efforts from our own team of volunteers dedicated to building a fully accessible web through WordPress: https://make.www.ads-software.com/accessibility/

    @bayu-angora If you ever need help with that, please feel free to stop by our Accessibility support forum: https://www.ads-software.com/support/forum/accessibility

    Thread Starter bayu-angora

    (@bayu-angora)

    Thanks, Jeff.

    Moderator James Huff

    (@macmanx)

    You’re welcome!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Warning About Error Code and Validation on W3’ is closed to new replies.