SEMANTIC html about static-code-scan

[dmethvin]

We've discussed trying to add some sort of accessibility tool. The Webaim.org site is an interesting scan, but it does generate a pretty scary display for most non-trivial pages. But would it be better to send people there, rather than trying to re-implement it in this scan?

[dmethvin]

See also #35 and #37 for proposed accessibility additions.

[alexandre-works]

Hi,
Probably I didn't explain myself properly. I agree with you that for a proper accessibility scan, users should go for instance Webaim.org. Accessibility scan is quite complicated and it would be confuse to implement that here.
My point was an example of something that we could get some ideas. We would not be looking for specifics regarding accessibility. The idea was to show somehow how the html was writing, and if had any semantic meaning.
EX:

are a block element but no semantic meaning! to have a

instead of a

is diferente, and a screen reader (at least the old ones) would read it differently. and the way that may be translated to an image that somehow shows that if you are or aren't using semantic html.

1- http://take.ms/XfVy9
In here i can have showing in the browser exactly the same design. No problem at all... but they are totally deferent in a semantic way.

2- http://take.ms/flzzb
this is more or less what a screen reader would reed it. Just showing the non semantic way with no spaces, all in the same line, would show that this is not ok.

I hope I did explain better this time. I am not suggesting at all accessible testing, but I used a specific thing to suggest this idea
Cheers

[dmethvin]

I think this goes beyond the scope of this particular scanner. Again I think all of these are good ideas and agree completely with your comments about semantic markup. We just want to avoid creating too many judgmental tests.