Skip to content
cccskills
FreePublished on GitHub

gnome-accessibility

Make a GTK4/libadwaita app accessible — accessible labels and roles, tooltips on icon-only buttons, keyboard navigation, contrast, and testing with Orca/Accerciser. Use when fixing a11y issues or running the accessibility category of a HIG audit.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Skill: Accessibility

GTK4 exposes UI over AT-SPI automatically — standard widgets with visible labels need nothing. Work is needed where the visual and semantic layers diverge.

The big five (cover ~90% of violations)

  1. Icon-only buttons need both tooltip and label:

    Button {
      icon-name: "user-trash-symbolic";
      tooltip-text: _("Delete");           // sighted users
      accessibility { label: _("Delete"); } // screen readers (GTK usually
    }                                        // derives it from tooltip, but be explicit)
    
  2. Images and custom drawing need roles:

    DrawingArea {
      accessibility { label: _("Waveform of the current recording"); }
    }
    

    Decorative images: Image { accessibility { role: presentation; } }

  3. Inputs without visible labels:

    SearchEntry { accessibility { label: _("Search contacts"); } }
    

    With a visible label elsewhere, relate them: accessibility { labelled-by: my_label; }

  4. Everything reachable by keyboard: Tab order follows widget order — restructure containers rather than fighting focus. Custom interactive widgets need focusable: true and key handling. Never remove focus outlines in CSS.

  5. Don't convey state by color alone: pair color with an icon, label, or style (e.g. error rows get error class AND an icon + text).

Additional rules

  • Respect system settings: never hard-code font sizes (use classes from tokens/typography.md); test at 200% text scaling and with High Contrast.
  • Announce dynamic changes: toasts are announced automatically; for custom live regions use Gtk.Accessible.announce() (GTK ≥ 4.14).
  • Contrast: 4.5:1 minimum for text — the Adwaita palette meets this; custom colors must be checked in both light and dark.
  • Touch targets ≥ 44×44 logical px for primary controls.

Audit greps

# icon-only buttons missing tooltips (review hits manually)
grep -rn 'icon-name' --include='*.blp' . | grep -v tooltip
# custom drawing without accessibility block
grep -rn 'DrawingArea' --include='*.blp' -A3 . | grep -v accessibility
# focus outline removal (should be empty)
grep -rn 'outline.*none' --include='*.css' .

Testing

  • Orca (Super+Alt+S): can every view be understood and operated eyes-free?
  • Keyboard only: unplug the mouse; complete the app's primary task.
  • Accerciser or GTK inspector (Ctrl+Shift+D → Accessibility tab): check the computed label/role of every interactive widget.
  • High contrast + large text: Settings → Accessibility.

Full guidance: reference/hig/accessibility.md.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Add a standard AdwAboutDialog wired to app metadata, plus the AppStream metainfo file it should share data with. Use when adding an About entry, release notes, credits, or preparing app metadata.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

Responsive GNOME layouts: AdwBreakpoint conditions, BreakpointBin, MultiLayoutView, BottomSheet, narrow/wide layout swaps. Use when making an app work on phones or narrow windows.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

Onboarding tour with AdwCarousel and navigation dots, skippable welcome screens. Use when adding a first-run tour or feature showcase to a GNOME app.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

Implement GNOME's 4-tier destructive-action pattern: undo toasts instead of confirmation dialogs, AdwAlertDialog for irreversible actions. Use when adding delete, remove, clear, or other destructive actions.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

Loading, empty, and error states with AdwStatusPage and AdwSpinner — placeholder icons, titles, action buttons. Use when an app view can be empty, loading, or failed.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

Package a GNOME app as a Flatpak — manifest for the GNOME runtime, sandbox permissions, build/run/test loop, and Flathub submission checklist. Use when packaging, distributing, or preparing a GNOME app for Flathub.

The English summary is being prepared. Showing the original description.

hanthor/gnome-gui-spec4Updated Oct 11, 2026

See all skills by hanthor

Report a problem with this skill