Przejdź do treści
Biblioteka skilli
Projektowanie i UX · Przegląd i audyt

accessibility

/accessibility

Sprawdza, czy wszyscy mogą korzystać z interfejsu: kontrast, czytelny tekst, etykiety dla czytników, fokus klawiatury i błędy prostym językiem.

Repozytorium
solid-vibes ↗
Licencja
MIT
Ostatnia zmiana repozytorium
05.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Sprawdza, czy wszyscy mogą korzystać z interfejsu: kontrast, czytelny tekst, etykiety dla czytników, fokus klawiatury i błędy prostym językiem.

Wyzwalacze z opisu

is it accessiblecan blind people use itmy dad canthe text is too smalldoes it work with a screen readeris the contrast okmake it work for everyone
Oryginalny opis (EN)

Make sure everyone can use what gets built, on any platform: contrast, text that grows, labels for screen readers, focus, motion, touch size, colour never alone, plain errors. Use when someone says "is it accessible", "can blind people use it", "my dad can't read it", "the text is too small", "does it work with a screen reader", "is the contrast ok", "make it work for everyone", or when a design system, a screen or anything people see and tap is being made or changed.

Jak działa

  1. The basics
  2. While building
  3. Checking it
  4. Visuals
Sekcje z nagłówków SKILL.md, w oryginale · 43 linii, 768 słów
Podgląd SKILL.md
---
name: accessibility
description: Make sure everyone can use what gets built, on any platform: contrast, text that grows, labels for screen readers, focus, motion, touch size, colour never alone, plain errors. Use when someone says "is it accessible", "can blind people use it", "my dad can't read it", "the text is too small", "does it work with a screen reader", "is the contrast ok", "make it work for everyone", or when a design system, a screen or anything people see and tap is being made or changed.
---

# Accessibility

The basics that let everyone use what gets built: people who see poorly, who use a screen reader, who can't use a mouse, who turn the text size up, who get dizzy from motion. They hold on every platform (phone, computer, web) and every stack. They are built in, never asked: nobody chooses to leave someone out.

Used by `design-system` (the look is built to them), by `brief`, `plan` and `go` whenever a change touches what people see or tap, and by `review` through its accessibility lens.

How you talk to the user:
- Never ask whether to follow a basic. Follow it and say so in one line when it changed something they picked ("I darkened the green a little so the text on it reads in sunlight").
- Explain a term the first time in one plain line ("Screen reader: the phone reads the screen out loud for people who can't see it").
- Show a fix as a before and after, side by side (see Visuals).

## The basics

Each one is a check with a pass or a fail. When one fails, change the design, never the rule.

1. **Contrast.** Text stands out from its background at least 4.5 to 1; large text (about 24 points, or 19 bold) and icons that carry meaning at least 3 to 1. Check every text and background pair in light and dark mode.
2. **Text that grows.** Body text at least 16 points. With the system text size turned up to double, nothing is cut off, overlaps or needs sideways scrolling; rows and buttons grow with it.
3. **Labels for screen readers.** Every button, icon, image and field has a name a screen reader says: what it does, not what it looks like ("Delete entry", not "trash icon"). Decorative pictures are hidden from it. Headings are marked as headings.
4. **Focus and keyboard.** Everything that can be tapped can be reached and used with a keyboard (and a switch or TV remote where the platform has one), in reading order, with a visible focus ring. Nothing traps the focus.
5. **Motion.** No flashing more than three times a second. Animation that moves across the screen is reduced or replaced by a fade when the system asks for less motion. Nothing important happens only through motion.
6. **Touch size.** Every tappable thing at least 48 by 48 points (44 on Apple platforms), with space between neighbours, including small icons and links in text.
7. **Colour never alone.** An error, a state or a chart series also has an icon, a word or a pattern. Links in text are underlined or otherwise marked.
8. **Plain errors.** An error says what happened and what to do next, next to where it happened, in words (see the `writing` skill). It keeps what the person typed. It is read out by a screen reader when it appears.

Also: every field has a visible label (a placeholder is not a label), the screen title says where you are, time limits can be extended, and nothing needs a gesture without a single-tap alternative.

## While building

- **A design system**: check basics 1, 2, 6 and 7 for every colour pair and part, and list the checked pairs in `docs/design/system.md` under `## Accessibility`.
- **A screen or a change people see**: check all eight on what changed. Name, in the commit or PR body, any basic that was hard to meet and how it was met.
- **Can't meet one** (an outside service's widget, a brand colour the owner insists on): say so in plain words, offer the closest fix, and record it in the plan's `## Decisions` or a decision file.

## Checking it

Cheapest first: read the code and the design values for each basic; compute contrast from the hex values; then, when the contract's `run` can launch the app, turn up the text size, turn on the screen reader or the keyboard, and look. Report each basic as pass, fail or not checked, with why.

With Pro: the `ui` pack adds an accessibility checklist run over every changed screen and state, and the `flutter` pack wires the basics into the app's code.

## Visuals

"Show a visual" means: make the page with the `visual` skill and show it as `.solidvibes/agents.md` says for the agent in use. If that file is missing, write a local HTML file and tell the user where it is. A failed basic is shown as the screen before and after the fix, side by side, with the contrast numbers or the sizes written under each.

Wersje

RepozytoriumWynikLicencja
Ta strona · solidvibes/solid-vibes100MIT
ericrisco/rsc-harness100MIT
Sanit-mann/The-Insectoids100MIT
evanca/flutter-ai-rules100MIT
yonatangross/orchestkit100MIT
yonatangross/orchestkit100MIT
xobotyi/cc-foundry100MIT
krzysztofsurdy/code-virtuoso100MIT
andreibesleaga/gabbe100CC-BY-4.0

Migawka bazy z 13.11.2026 · wersja paczki da437af424c6 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90accessibility-review
    Audytuje projekt lub stronę pod kątem WCAG 2.1 AA: kontrast, klawiaturę, fokus, etykiety, rozmiar elementów dotykowych i zachowanie czytnika ekranu.
  • 90a11y-audit
    Sprawdza i naprawia dostępność stron WCAG 2.2 AA: semantykę, klawiaturę, fokus, etykiety, kontrast i czytniki ekranowe.
  • 90frontend-a11y
    Prowadzi pracę nad dostępnością interfejsu do WCAG 2.2 AA: nawigacja klawiaturą, etykiety dla czytników ekranu, zarządzanie fokusem, kontrast kolorów, rozmiar celów dotyku i obsługa ograniczonego ruchu.
  • 100accessible-by-default
    Ustala minimalne zasady dostępności dla każdego interfejsu, który buduje agent: kontrast, fokus, cele dotyku, ruch i semantykę.
  • 87ui-accessibility
    Sprawdza i buduje interfejsy Laravel, Livewire i Flux zgodne z WCAG 2.1 AA, z obsługą klawiatury i czytników ekranu.
  • 100accessibility-expert
    Buduje dostępne UI i audytuje problemy dostępności pod WCAG 2.2 AA: semantyczny HTML, ARIA, klawiatura, czytniki ekranu, fokus i kontrast.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.