At a Glance
- Builds and maintains Auric Artisan end to end — the colour engine, the tools, the site and the writing
- Author of the Learn library and the platform documentation
- Wrote the colour-science engine: CIE XYZ, L*a*b*, LCH, Oklab, sRGB and Display P3, with deltaE in CIE76, CIE94, CIEDE2000 and CMC, plus chromatic adaptation and gamut mapping
- Wrote the colour-vision simulation models, following Viénot (1999), Brettel (1997) and Machado (2009)
- Wrote the accessibility engine behind the analyzer — WCAG 2.2 and APCA contrast, ARIA 1.2, accessible-name computation and VPAT reporting
- Publishes the browser extension and the VS Code extensions
- Works in India; the platform bills in INR
1. Who writes this
+Chirag Bansal is the founder of Auric Artisan and the author of everything published here. The articles in the Learn library and the platform documentation are written by hand, not commissioned or syndicated.
The writing and the software are the same body of work. The articles on colour difference describe the same deltaE implementations that run in the tools; the pieces on colour-vision deficiency describe the same simulation models the vision lab uses; the accessibility writing describes the rule engine that powers the analyzer. Where an article states a formula or a threshold, it is the formula the code uses.
2. What that work is
+Colour science. The engine implements the CIE colour spaces — XYZ, L*a*b*, LCH — alongside Oklab, sRGB and Display P3, with colour-difference metrics in CIE76, CIE94, CIEDE2000 and CMC, chromatic adaptation transforms, gamut mapping with selectable rendering intents, and metamerism handling.
Colour vision. The vision simulation follows the published models — Viénot, Brettel and Mollon (1999), Brettel, Viénot and Mollon (1997), and Machado, Oliveira and Fernandes (2009) — for protan, deutan and tritan deficiencies across severity ranges. The Ishihara-style generator is a teaching and demonstration tool, and is not a medical device or a diagnostic instrument.
Accessibility. The analyzer runs a rule engine covering WCAG 2.2 success criteria and APCA contrast, ARIA 1.2 validation, accessible-name computation, screen-reader transcript modelling, colour-vision-deficiency checks and VPAT-style reporting.
Tooling. Alongside the site there is a cross-browser extension and a set of VS Code extensions covering colour and accessibility work in the editor.
3. How the articles are written
+Where an article rests on a specific published model, it names it in the text — the vision-deficiency papers above, the CIE colour spaces and difference formulae, and the W3C specifications behind the accessibility material. Most articles carry no formal bibliography; a references section is something the library is still missing rather than something it has.
Where an article makes a claim that can be demonstrated, it demonstrates it: the interactive figures in the Learn library compute their output live in the browser using the same engine the tools use, so a reader can change the inputs and check the result rather than take the number on trust.
Corrections are welcome and are made in place, with the revision date updated. Write to [email protected] if something here is wrong.
4. Contact
+For corrections, questions about the science, or anything published on this site: [email protected].
For support, billing and general enquiries: [email protected], or the contact form.