title: "[Spec] A11y CLI Proof of Concept" date: 2026-03-14 status: draft author: Umut Sirin tags:
- spec
- a11y
- poc notion: TBD
title: "[Spec] A11y CLI Proof of Concept" date: 2026-03-14 status: draft author: Umut Sirin tags:
| title | date | status | author | tags | |||
|---|---|---|---|---|---|---|---|
[RFC] rspack Module Graph Dump |
2026-03-14 |
draft |
Umut Sirin |
|
title: "[RFC] Property-Based Accessibility Testing" date: 2026-03-14 status: draft author: Umut Sirin tags:
PlusQA's accessibility audit has surfaced 382 [A11y] tickets (335 open) across iOS (31%), Android (36%), and web/desktop (22%). Fixing these manually requires engineers to navigate to hard-to-reach screens, understand WCAG criteria, make the fix, then verify with a screen reader. This doesn't scale — feature teams shouldn't be spending cycles on mechanical a11y prop additions when 70% of fixes are templatable.
Not a framework. Not a monolithic system. A set of composable primitives that:
Reimplement the current branch on a new branch with a clean, narrative-quality git commit history suitable for reviewer comprehension.
Validate the source branch
main.Analyze the diff
main.| { | |
| "description": "Colemak Mod-DHm (matrix / ortho keyboards)", | |
| "manipulators": [ | |
| { | |
| "from": { | |
| "key_code": "grave_accent_and_tilde", | |
| "modifiers": { "optional": ["caps_lock", "left_command", "left_control", "left_alt", "right_command", "right_control", "right_alt"] } | |
| }, | |
| "to": [{ "key_code": "grave_accent_and_tilde" }], | |
| "type": "basic" |
| { | |
| // Editor settings | |
| "editor.accessibilitySupport": "off", | |
| "editor.bracketPairColorization.enabled": false, | |
| "editor.codeActionsOnSave": { | |
| "source.organizeImports.biome": "explicit" | |
| }, | |
| "editor.codeLensFontFamily": "Iosevka", | |
| "editor.cursorBlinking": "solid", | |
| "editor.foldingImportsByDefault": false, |
You are an expert software engineer tasked with writing detailed Request for Comments (RFC) documents. Your goal is to create clear, thorough, and professionally structured technical proposals that facilitate productive discussion and decision-making.
When writing RFCs, follow these key principles:
| # vim:fileencoding=utf-8:foldmethod=marker | |
| #: Fonts {{{ | |
| #: kitty has very powerful font management. You can configure | |
| #: individual font faces and even specify special fonts for particular | |
| #: characters. | |
| # font_family IA Writer Mono S | |
| font_family InconsolataGo Nerd Font |
| # Address vim mode switching delay (http://superuser.com/a/252717/65504) | |
| set -s escape-time 0 | |
| set -g history-limit 50000 | |
| set -g display-time 4000 | |
| set -g status-interval 5 | |
| set -g status-keys emacs | |
| set -g focus-events on | |
| setw -g aggressive-resize on | |
| setw -g mouse |