Accessibility goals + public statement & contact

Open
#416 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
accessibility, documentation

Research direction

No files, tests, or entry points are named. Start by narrowing the checklist into separately scoped work, beginning with the accessibility statement and dedicated communication channel. Done should be a published statement and a documented, working contact path, with the remaining audit, theme, translation, and screen-reader ideas handled separately.

Written by the indexing model from the issue text.

Description

community discussion

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:
  • Create an accessibility statement (e.g. UCAR's) describing out commitment
  • Include a dedicated communication channel for accessibility concerns and feedback
  • Implement theme configs (very useful read!), site maps, and other helpful considerations from other projects in our space
  • Automate auditing of the accessibility of our sites and Cookbooks
  • From @jukent: proactive language considerations, room for translation work, and non-English annotations to content
  • From @jukent: design considerations for screen readers, e.g. descriptive link text and meaningful alt text on images

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.

Dominant language
Python
Stars
36
Forks
25
Avg merge
3d 16h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ProjectPythia/projectpythia.github.io

All issues in ProjectPythia/projectpythia.github.io

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.