We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http://clecompte.com/getting-started-508-compliance/
http://www.espn.com/core/toolkit/page/webAccessibilityGuide
https://www.smashingmagazine.com/2017/11/building-accessible-menu-systems/
Not sure if it's useful, but want to leave this here so it doesn't disappear in free Slack
The text was updated successfully, but these errors were encountered:
If there is any help wanted for a11y, I have a few people who may be interested in helping out with that part.
Sorry, something went wrong.
Thanks @LukePettway , point them this way
I'm quite keen on helping out with accessibility. What needs doing?
Hi @andrewtanner1987. Please review the accessibility document, feel free to subit PRs for changes or additions you think may be useful: https://github.com/web-matters/industry-issues/tree/master/accessibility
No branches or pull requests
http://clecompte.com/getting-started-508-compliance/
http://www.espn.com/core/toolkit/page/webAccessibilityGuide
https://www.smashingmagazine.com/2017/11/building-accessible-menu-systems/
Not sure if it's useful, but want to leave this here so it doesn't disappear in free Slack
The text was updated successfully, but these errors were encountered: