Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#267 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
28/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
c
Bereich
accessibility, desktop

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
C
Sterne
10
Forks
8
Ø Merge
21 Min.
Gemergte PRs (30 T.)
1

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus FriendsofECCE/ECCE

Alle Issues in FriendsofECCE/ECCE

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.