Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Accessibility goals + public statement & contact

Abierto
#416 2 comentarios 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
accessibility, documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
36
Forks
25
Merge medio
3 d 16 h
PR fusionados (30 d)
2

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ProjectPythia/projectpythia.github.io

Todos los issues de ProjectPythia/projectpythia.github.io

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.