Fulfill requirements to meet Web Accessibility standards

[t0p0lin0]

Targetting WCAG level AA success criteria.

[kenman345]

Is there a guide? I think I can handle doing some of this since its Jekyll and we generate most of our on page content from the same set of code, but it would be nice if we can do this, preferably if you can take this on or think about as we build out the new pages.

[t0p0lin0]

You can actually issue an Accessibility audit through Chrome's devtools:

However it just seems to hang for me. There is a guideline linked to above in my original comment (WCAG level AA), but that's not too straight forward. Recommending we leave this open, in hopes that an expert will be willing to save the day...someday.

[kenman345]

is this something that can help?
https://github.com/marketplace/accesslint

[kenman345]

i tested it out and this is how it looks: https://github.com/kenman345/acceptbitcoincash/pull/22/files#diff-b893a2e076cee8dcb56202691f2881d2R9

I am thinking about wiping on my repo all the files and then reverting that and then committing it so I can get it to do the heavy lifting instead of using this simply as a maintenance tool for new code.

[kenman345]

so this tool is fine but it doesnt work on the compiled pages so it may miss things

[kenman345]

erm, HTML proofer has these checks: gjtorikian/html-proofer#382

I I ran it against some of our stuff and it found a few issues.

https://travis-ci.org/kenman345/acceptbitcoincash/jobs/337800948#L1095

I think we can quite easily accommodate these changes and I think it would be a worthwhile effort during a refactor for accessibility.

[kenman345]

Sp SRI tags can be generated on the fly by Jekyll. Someone even made a plugin we can use and wrote up why and how here: https://vcsjones.com/2016/11/02/sri-with-jekyll/

This would be good to implement during our Web Accessibility refactoring efforts. The Travis-CI tests indicate we only have about 10 links/script tags that would need this functionality added to.

As far as web accessibility, I have not found any particular tool that works extremely well. I think we need to refactor our partials first though so fixing these types of issues fixes it everywhere instead of making a fix and potentially losing that fix if we forgot we did it during refactoring the re-used sections of our site.

[kenman345]

would be nice if someone could help with this, i'm not too capable of getting to it, as is noticable by how long this has been open

[kenman345]

@t0p0lin0 Can we get on this? I feel that accessibility is more than a nice to have in this day and age, but a requirement. I would love to learn this stuff but I have little experience and your expertise can be very helpful.

[kenman345]

this tool seems to really help, so I'm just suggesting it if anyone is gonna pick up the torch on this one. https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh?hl=en-US