Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Accessibility: keyboard, screen readers, colour, scaling and contrast

Aberta
  • Algo errado?
#267 3 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
28/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
c
Domínio
accessibility, desktop

Direção de pesquisa

Start by reading ACCESSIBILITY.md and the linked issue references #210 and #227, then review the release checklist and the main windows named in the issue. The work spans keyboard access, screen reader support, colour, scaling, contrast, and release process checks; done means these areas have actionable coverage and the issue form and release checks are in place.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

ECCE should be usable by people who work by keyboard, use a screen reader, have reduced colour vision or low vision, or need larger text. It is also good design in general. A project statement goes in ACCESSIBILITY.md; this ticket tracks the work.

Keyboard

  • Every action reachable without a mouse: menus, toolbars, the Organizer tree, the editors, the Builder's panels.
  • A visible focus on every control; a sensible tab order in each window (the Calculation Editor, Register Machines, the Launcher, Preferences); no traps in dialogs or docked panes.
  • Shortcuts listed in the menus (several exist; check gaps).

Screen readers (Orca on Linux, NVDA on Windows, VoiceOver on macOS)

  • Accessible names on icon-only buttons: toolbars, the message-pane buttons, the Builder's tool buttons. wxWidgets uses the button's label or tooltip; check that each has one.
  • Status changes announced, or at least shown as text: job state, verify results, errors.
  • The 3-D view itself is not readable; offer the same information as text where it matters (atom list, measurements, property tables already exist).

Colour never the only signal

  • Run states already use shape as well as colour; check the rest: spectra and plots (line style or markers as well as colour), orbital signs (+/− as well as two colours), charge and ESP colouring (with a legend and values).
  • Colour-blind-safe defaults (Okabe-Ito, viridis; #210).

Scaling and low vision

  • Text follows the system font size and scale; windows lay out at larger text (the apps tests already check small screens).
  • Windows: DPI awareness, so 150–200 % scaling is sharp (#210).
  • Contrast of text and controls at least WCAG 2.2 AA (4.5:1 for text) in light and dark themes; the viewer on a white background (#210, #227).

Process

  • An accessibility issue form (what you tried, what went wrong, system and assistive technology), linked from ACCESSIBILITY.md.
  • A keyboard-only pass and a screen-reader spot check on the main windows before each 9.x release, noted in the release checklist.
Linguagem predominante
C
Estrelas
10
Forks
8
Merge médio
21min
PRs com merge (30d)
1

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de FriendsofECCE/ECCE

Todas as issues de FriendsofECCE/ECCE

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.