wcag
codeq
Our great sponsors
| wcag | codeq | |
|---|---|---|
| 8 | 3 | |
| 1,014 | 537 | |
| 2.7% | 0.6% | |
| 9.6 | 0.0 | |
| 6 days ago | about 10 years ago | |
| HTML | Clojure | |
| GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wcag
-
Low-contrast font color and unreadable texts? To hell with them!
> This isn't subjective or aesthetics, it's an objective measurement.
I’m going to push back against this slightly (I’m not disagreeing that the HN contrast is bad, but I am challenging the WCAG ratios). It’s objective, but it’s not a good measurement. WCAG computes contrast in sRGB, which is not perceptually uniform. As such there are cases where WCAG will give better scores to worse contrast.
https://github.com/w3c/wcag/issues/695
It’s the biggest thing I wish would be changed in WCAG.
-
APCA (WCGA 3.0) does not allow for 14px font to be used as a regular base
The APCA color calculator is still in progress and WCAG 3.0 is still a working draft, so its guidelines are not in place. The purpose of the changes are so that color contrast will focus on perceived color instead of a more simple algorithm that can mess up in some cases: https://github.com/w3c/wcag/issues/695
- The pain of UX/UI and accessibility
- WCAG exceptions?
- Starting to design for better accessibility
- Contrast Ratio Math and Related Visual Issues
-
Does anyone follow WCAG's typography guidelines to the letter?
This came up in my work recently. Here’s a possibly helpful thread if you’re looking at a mobile app: https://github.com/w3c/wcag/issues/1510
-
The Database Inside Your Codebase
Just because you find it readable does not mean others can; also, color contrast is not the only thing that affects readability. In this case, the issue is font weight.
Here's some discussion on the issue: https://github.com/w3c/wcag/issues/665
codeq
-
Codebase as Database: Turning the IDE Inside Out with Datalog
This is a well composed idea. This reminds me slightly of (Rich's?) (Codeq)[https://github.com/Datomic/codeq] although this is really outlining code and scm logic and not syntax trees etc. I think I was always codeq would add something like this (for doing what you are doing to validate forms) but the input mechanism probably needed more hammock time
- The Database Inside Your Codebase
-
What comes after Git? It's been 15 years since it was created
He is referring to codeq: https://github.com/Datomic/codeq which has a last commit on 2014. But there have been recent rumours (https://medium.com/@sfyire/can-codeq-2-solve-clojures-weakne...) that Hickey is working in a new version of it. Fingers crossed!
What are some alternatives?
jedi - Awesome autocompletion, static analysis and refactoring library for python
semgrep - Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.
guide - Aiming to be a fully transparent company. All information about source{d} and what it's like to work here.
Sourcetrail - Sourcetrail - free and open-source interactive source explorer
dupver - Deduplicating VCS for large binary files in Go
Glean - System for collecting, deriving and working with facts about source code.