search

ebeshero / newtFire-webDev

for development of the newtFire website at http://newtfire.org
GNU Affero General Public License v3.0
3 stars 7 forks source link

W3C Validator Alternatives #93

Open RJP43 opened 7 years ago

RJP43 commented 7 years ago

Just learned about Code Sniffer and WAVE in the DHSI 2017 Accessibility Course -- two good alternatives to W3C validator that seems easier and more detailed error messages.

djbpitt commented 7 years ago

This gives accessibility reports, but unless I've overlooked something, it doesn't do plain ol' HTML/CSS validation. Not that it needs to, but it seems to address a different task.

On Wed, Jun 7, 2017 at 4:37 PM, Rebecca Parker notifications@github.com wrote:

Just learned about this http://squizlabs.github.io/HTML_CodeSniffer/ in DHSI 2017 Accessibility Course -- seems like a good alternative to W3C validator that seems easier and more detailed error messages.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ebeshero/newtFire-webDev/issues/93, or mute the thread https://github.com/notifications/unsubscribe-auth/AF8b3Oq0NBwMdz9mGgcBwIbYbOeJ5S9_ks5sBwoRgaJpZM4NzP7L .

RJP43 commented 7 years ago

I was under the impression that these two tools give both standards and accessibility (when Code Sniffer identifies an 'error' it does link out to W3C); whereas, W3C only checks standards (which poses just as much of an issue if these other tools only check for accessibility). Thanks for weighing in @djbpitt

Be great if we could find a validator for our students to check standards and accessibility.

Here is the conversation happening here at DHSI where we are discussing and testing these tools with regards to accessibility in particular.

djbpitt commented 7 years ago

So perhaps I didn't see a validation report because the page was valid? W00t!

On Wed, Jun 7, 2017 at 6:40 PM, Rebecca Parker notifications@github.com wrote:

I was under the impression that these two tools give both standards and accessibility (when Code Sniffer identifies an 'error' it does link out to W3C); whereas, W3C only checks standards (which poses just as much of an issue if these other tools only check for accessibility). Thanks for weighing in @djbpitt https://github.com/djbpitt

Be great if we could find a validator for our students to check standards and accessibility.

Here is the conversation happening here at DHSI where we are discussing these tools with regards to accessibility in particular https://docs.google.com/document/d/11gcpO06WwPdinAV_qG-lu9va_bpwr8PsYwZwY4FBFQo/edit#heading=h.je0ul72tyw38 .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ebeshero/newtFire-webDev/issues/93#issuecomment-306945630, or mute the thread https://github.com/notifications/unsubscribe-auth/AF8b3L5NPuGWWNgl_QObmoOTd5iM65qsks5sByb6gaJpZM4NzP7L .