-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
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
Accessibility goals + public statement & contact #416
Comments
Perhaps you all just got an email through our team alias, I entered our site into Site Improve and we got an accessibility score of 81. It wasn't very informative on what we were marked down for. I might request a full report. Something that could work for screen reader improvement along with descriptive link text is making sure our images have descriptions. |
The UCAR's accessibility statement starts similar to, "Project Pythia takes the accessibility of our educational portal seriously and have implemented the following measures to improve accessibility of our websites:" So, what measures have we taken? We're committed to free and open source content, reducing the barrier to entry in the geosciences. We have open monthly community meetings. We partner with outreach efforts such as ScienceMatch to serve broad communities. |
We've had some fleeting discussions in the past about accessibility, but we need to capture some concrete goals (some of which may be important to get done before the Hackathon!)
What are the ways we can commit to improving accessibility to our website and build accessible design into our offerings? Suggestions:
This may be better represented as a Discourse discussion, but I wanted to capture at least the first two as action items we can cross off in issues to make sure to get done before the Hackathon.
The text was updated successfully, but these errors were encountered: