Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
#267 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
28/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
c

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
C
スター
10
フォーク
8
平均マージ
21分
マージ済み PR(30日)
1

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

FriendsofECCE/ECCE のほかの issue

FriendsofECCE/ECCE の issue をすべて見る

似ている issue

C の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。