Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#267 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
28/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c
Ambito
accessibility, desktop

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
C
Stelle
10
Fork
8
Merge medio
21m
PR unite (30g)
1

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di FriendsofECCE/ECCE

Tutte le issue di FriendsofECCE/ECCE

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.