5 ms·
This seemed like a cool idea at first glance, but it's actually quite useless. I ran it on one of my projects, which I've already tested for standards and acce
by akamaka 16y ago
This seemed like a cool idea at first glance, but it's actually quite useless.
I ran it on one of my projects, which I've already tested for standards and accessibility compliance, and it highlighted everything on the page. There's no messages explaining what is failing and where. A traditional validator would be more helpful here.
- bcrescimanno 16y agoI think it would be a huge improvement to implement tooltips when mousing over an outline that brings up a note saying WHY something was flagged. Otherwise, I think it's an interesting idea.
- weaksauce 16y agoIf you are a web designer you can just inspect each element in firebug. It will give you a list of the currently applied styles to that element and the top one is something of the form: .holmes-debug div:empty, .holmes-debug span:empty, .holmes-debug li:empty, .holmes-debug p:empty, .holmes-debug td:empty, .holmes-debug th:empty If you are on a div and it's empty then that's why, etc.... It would be a lot easier if there was a popup explaining but as a first pass it's pretty useful and not all that hard to get at the info you want.
- akamaka 16y agoGood tip. I went back and took a look at while my previously validated page was failing so badly. It turns out this test suite is really poorly designed! For example, it can't identify implicitly associated labels, so the whole concept behind this tool is quite flawed.
- weaksauce 16y agoYeah there is only so much that you can do solely with css but I prefer explicit labels anyway.