Accessibility | Meeting WCAG 2.0 and section 508 about dwyl-site HOT 18 CLOSED

I'll settle for running the site through wave.webaim.org and having it pass with no errors and minimal alerts 😊
We probably need to do some looking into how closely wave follows WCAG 2.0

Note: ngrok could again come in handy for this whilst you're testing locally (#244 (comment))

from dwyl-site.

@ZooeyMiller let's have underline as a link convention for all text links in page text (not nav and footer links etc)

from dwyl-site.

A great post from @Charlotteis to help with this, mentioned in #83.
https://github.com/dwyl/dwyl.github.io/issues

from dwyl-site.

@iteles -

• Would you be able to elaborate on what this issue means?
• Is it all covered in #83?
• Is this now out of date and ready to close?

from dwyl-site.

@iteles would you be able to provide a list of requirements (checkboxes) to close this issue?

from dwyl-site.

https://www.wuhcag.com/wcag-checklist/

Tools like https://www.powermapper.com/products/sortsite/checks/accessibility-checks/ and http://wave.webaim.org/ should help check this.

from dwyl-site.

• Have site meet all standards on https://www.wuhcag.com/wcag-checklist/
• Run site through http://wave.webaim.org/ and having it pass with no errors or alerts
• Run site through https://www.powermapper.com/products/sortsite/checks/accessibility-checks/ and having it pass with no errors or alerts

from dwyl-site.

This is going to throw up an error and needs to be fixed before we go live: 3aa6cf2#diff-d015ee2938b049b883af8932cc97a99bR58

from dwyl-site.

@iteles can you clarify what needs changing?

from dwyl-site.

@markwilliamfirth Yes, sorry, href="#" is what will throw an accessibility error.

from dwyl-site.

We can use pa11y to check the site for accessbility, it has WCAG2 standards built in, but has the different levels as well, are we looking for A, AA or AAA rating? More info on the differences between the levels in the stack overflow answer.

On AA we get errors for contrast ratios, on A we do not.

from dwyl-site.

@ZooeyMiller I just ran pa11y

npm install -g pa11y
pa11y http://dwyl.com

...and got this:

Do you get the same?

I think A is fine for now

from dwyl-site.

@markwilliamfirth as standard it with run with AA. run pa11y --ignore "warning;notice" --standard WCAG2A http://dwyl.com to run A and ignore warnings. Passes for me!

from dwyl-site.

@ZooeyMiller 👍

pa11y --ignore "warning;notice" --standard WCAG2A http://dwyl.com

This passes! 🎉

Running through wave (http://wave.webaim.org/) we get:

Running through powermapper (https://www.powermapper.com/products/sortsite/checks/accessibility-checks/) we get:

@iteles I think meeting WCAG2 A is fine for now - what do you think?

from dwyl-site.

I'm going to look into fixing the accessibility issues you've mentioned in #14 (comment) Mark.

from dwyl-site.

One issue from sortsite is:

Removing the underline from links makes it hard for color-blind users to see them.

Is this a compromise we want to make? It is listed as an "A" level error. Related to #394

from dwyl-site.

No red accessibility errors (red is for "A" standard, orange for "AA"). The other issues are worth looking into, but aren't accessibility so not strictly relevant for this issue.

from dwyl-site.

@iteles are you happy with this level of accessibility? We can keep going but I think this is good enough for now

from dwyl-site.