Software Engineering Blog, page 12
Notes on software engineering from the Atyantik practice.
Latest posts
Kalpesh Patel
Tailwind vs Bootstrap in 2026: Tailwind CSS v4 and Bootstrap 5.3 built on the same page
Tailwind vs Bootstrap at current versions: one page built in Tailwind CSS v4 and Bootstrap 5.3, bytes measured, and which one fits your team.
Read the postTirth Bodawala
Ecofyre low-carbon design theme for Figma: what each design choice costs in bytes, grams and access
The Ecofyre low-carbon design theme, measured choice by choice: image and font bytes, grams of CO2e per view, dark surfaces and the WCAG 2.2 floors.
Read the postAjay Patel
WCAG UI UX design: the share of WCAG 2.2 a designer settles before code
WCAG UI UX design, split at the handoff: the WCAG 2.2 numbers a design file can check, what it must annotate, and what only code and testing can prove.
Read the postIshan Chavda
API types and architectures: what REST, GraphQL, gRPC, SOAP, webhooks and event streams cost to run and to change
API types and architectures compared by cost: measured bytes, caching, versioning and team skills for REST, GraphQL, gRPC, SOAP, webhooks and Kafka.
Read the postVishal Prajapati
Accessible single-page applications: what each router does on a route change, and how to fix the gap
Accessible single-page applications move focus and announce the new page on every route change. See what six routers do by default and how to patch them.
Read the postVishal Prajapati
ARIA live regions: how to make screen readers announce dynamic content
How ARIA live regions work: pick role status, alert or log, predict aria-live and aria-atomic, fix a silent region and size a screen reader test plan.
Read the postJanki Gandhi
Keyboard navigation focus management under WCAG 2.2: six stops, a test and a native fix for each
Keyboard navigation focus management under WCAG 2.2: tab order, visible and unobscured focus, widgets, modal dialogs and route changes, each with a test.
Read the postTirth Bodawala
Accessible multimedia under WCAG 2.2: captions, transcripts and audio description for every clip
Accessible multimedia under WCAG 2.2: what 1.2.1 to 1.2.5 ask of each clip at A and AA, with WebVTT captions, transcripts and audio description.
Read the postJanki Gandhi
Accessible forms in HTML and ARIA: the four things every field must expose for WCAG 2.2
Accessible forms give every field a name, a hint, a state and a linked error. See the HTML, ARIA and WCAG 2.2 rule behind each, plus how to test them.
Read the postTirth Bodawala
ARIA roles for developers: every role is a contract you must keep
ARIA roles for developers, read as contracts: the states, children and keys each role owes, tabs worked key by key, and an HTML5 tags list.
Read the postTirth Bodawala
Color contrast accessibility under WCAG 2.2 and the ADA: ratios, checks and dark mode
Color contrast accessibility explained: the WCAG 2.2 ratios, what ADA color compliance means, and how to check every color pair in light and dark mode.
Read the postTirth Bodawala
Screen reader compatibility testing: a five-check loop for NVDA, JAWS, VoiceOver and TalkBack
Screen reader compatibility testing as a loop per component: pick pairings from survey data, run five checks in four screen readers, record each result.
Read the post










