AF

ai-for-accessibility-collective/ai-for-accessibility-toolkit

Developer tools

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る

14 stars 品質 59 トレンド 40Apache-2.0

The browser extensions built on this toolkit are in the extension repository, with an install guide that needs no coding. There's also a plain-language overview in docs/TLDR.md.

概要

The browser extensions built on this toolkit are in the extension repository, with an install guide that needs no coding. There's also a plain-language overview in docs/TLDR.md. The toolkit is a set of parts a developer can use to make an app adapt to a person. It can: - learn what a person needs, e.g., larger text or fewer animations, - keep those needs in a profile on the person's device, - and turn the profile into skills, which are sets of adaptations that change the app for that person. You choose which parts to use and how your app uses them. A person says what they need, the profile picks skills that fit, your app applies the adaptations, and the person can approve, correct or undo each one. The profile learns from those choices. The same profile works across platforms. For example, a profile with larger text (textSize 1.

README

以下は原文 README の抜粋です。原文を見る。

AI for Accessibility Toolkit

An open toolkit for building apps that adapt to each person’s accessibility needs.

What it is · Key terms · Who it’s for · Try it · Contributing · Docs


Not a developer? The browser extensions built on this toolkit are in the extension repository, with an install guide that needs no coding. There’s also a plain-language overview in docs/TLDR.md.

What it is

The toolkit is a set of parts a developer can use to make an app adapt to a person. It can:

  • learn what a person needs, e.g., larger text or fewer animations,
  • keep those needs in a profile on the person’s device,
  • and turn the profile into skills, which are sets of adaptations that change the app for that person.

You choose which parts to use and how your app uses them.

flowchart LR
  accTitle: How the toolkit fits
  accDescr: A person says what they need. Inside the toolkit, a profile stores those needs and a skill says which adaptations fit. The host application applies the adaptation on its own surface. The person approves, corrects or undoes it, and the profile learns from that. A developer takes whichever toolkit components suit their application.
  subgraph T[The toolkit: take the components that fit your application]
    direction LR
    A[Profilethe person's own, shared onlywith their permission] --> S[Skillwhich adaptations, at what settings]
  end
  P[A personsays what they need] --> A
  S --> D[Adaptationthe host application applies it,on its own surface]
  D --> V[The person approves,corrects or undoes]
  V -- the profile learns --> A

A person says what they need, the profile picks skills that fit, your app applies the adaptations, and the person can approve, correct or undo each one. The profile learns from those choices.

The same profile works across platforms. For example, a profile with larger text (textSize 1.5), a dark theme and reduced motion becomes these settings in the renderers in toolkit/surfaces/:

Surface What the host receives
web.js { "fontScale": 150, "darkMode": true, "motionReducer": true }
mobile.js { "text": { "scalePercent": 150, ... }, "display": { "darkMode": true, ... }, "motion": { "reduceMotion": true }, "touch": { "minTargetPt": 44 }, ... }
xr.js { "text": { "angularSizeDeg": 0.525, "worldHeightM": 0.014 }, "ui": { "maxEccentricityDeg": 20, "darkEnvironmentPreferred": true }, "motion": { "reduced": true, "comfortVignette": true, "snapTurning": true }, ... }

The mobile settings use the same names as the accessibility settings in iOS and Android. The XR renderer gives text size as an angle at the eye, since a

GitHub で README 全文を見る

推奨ツール

別のキーワードを試すか、フィルタを外してください。

インストール

npx skillfish add ai-for-accessibility-collective/ai-for-accessibility-toolkit
MCP 初心者?mcpskill.org のガイドから始めましょう →