For educational reasons I've decided to create my own CA. Here is what I learned.
Lets get some context first.
marcysutton
/ chrome-a11y-experiment-instructions.md
Last active
January 31, 2023 22:07
Enable Chrome Accessibility Experiment
NOTE: This is no longer an experiment! You can use the accessibility inspector in Chrome Devtools now, including a fantastic color contrast inspection tool. Read more: https://developers.google.com/web/updates/2018/01/devtools#a11y
Just like any good element inspector helps you debug styles, accessibility inspection in the browser can help you debug HTML and ARIA exposed for assistive technologies such as screen readers. There's a similar tool in Safari (and reportedly one in Edge) but I like the Chrome one best.
As an internal Chrome experiment, this tool differs from the Accessibility Developer Tools extension in that it has privileged Accessibility API access and reports more information as a result. You can still use the audit feature in the Chrome Accessibility Developer Tools, or you could use the aXe Chrome extension. :)
To enable the accessibility inspector in Chrome stable:
robertpainsi
/ commit-message-guidelines.md
Last active
July 27, 2024 06:17
Commit message guidelines
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages
aleclarson
/ rollup-typescript.md
Last active
June 21, 2024 03:25
The best Rollup config for TypeScript libraries