Skip to content

Markdown Syntax: Common Pitfalls and Accessibility

Have you ever asked an AI to “put this in a table” and gotten back text littered with pipes (|) and dashes (-)? It looked like a clean table right there in the chat window — but the moment you copied it into a messaging app, it turned into a mess of symbols. Those symbols are Markdown. These days you run into it everywhere — GitHub READMEs, technical blogs, note-taking apps like Notion, even the replies an AI chatbot sends you. ...

Published date: 2026-08-15 · Reading time: 8 min · Word count: 3630 words · Author: Isaac

The Traps in AI-Made Code — Missing Accessibility and Edge Cases

This is Part 21 of the “Frontend Testing, Done Right” series. Browse the full series · Glossary AI-written code is fast, it runs, and the screen looks good. The problem is that it’s wrong in plausible ways. Two spots go empty especially often. One is accessibility — the things people who use the web without looking at a screen need. The other is what happens in moments that rarely come up — an empty search box submitted, a server returning a 500. We call these edge cases. Both fall into “nobody covers it unless you ask” territory. ...

Published date: 2026-08-07 · Reading time: 6 min · Word count: 2831 words · Author: Isaac

Popover, Anchor Positioning, Dialog: Are They Accessible Enough to Use Yet?

A green support table doesn't mean everyone can use it. Here's a 2026 accessibility check on popover, anchor positioning, dialog, and view transitions — and what you still have to do yourself for each.

Published date: 2026-08-05 · Updated 2026-10-24 · Reading time: 28 min · Word count: 5738 words · Author: Isaac

Building Test and Accessibility Gates with GitHub Actions

This is Part 17 of the “Frontend Testing, Done Right” series. Browse the full series · Glossary Tests have no power while they’re “something you run locally, sometimes.” They protect a team only once they become a checkpoint that runs on every PR. This article builds that checkpoint with GitHub Actions — a merge gate where unit tests, E2E, and accessibility checks must pass before code can merge — from a single workflow file. Never touched CI? Fine. Three minutes of vocabulary first. ...

Published date: 2026-08-03 · Reading time: 6 min · Word count: 1250 words · Author: Isaac

The EU AI Act Is Now in Force — Where Accessibility Hooks In

AI regulation news usually sounds like someone else’s problem. Banned use cases, fines as a percentage of revenue — that reads like legal’s department, not ours. But a provision that takes effect on August 2 contains this sentence: Ensure that high-risk AI systems comply with the accessibility requirements in accordance with Directives (EU) 2016/2102 and (EU) 2019/882 Those two directives are the Web Accessibility Directive and the European Accessibility Act (EAA). In other words, an AI regulation has pulled accessibility standards into itself. Whether you’re building an AI system or deploying one, once it’s classified as high-risk, accessibility stops being “nice to have” and becomes a conformity assessment item. ...

Published date: 2026-07-30 · Reading time: 4 min · Word count: 1964 words · Author: Isaac

The World Works Better With Us — July Is Disability Pride Month

There’s a month that doesn’t show up on most calendars, yet is observed all over the world. July — Disability Pride Month. The pairing of “disability” and “pride” can feel unfamiliar at first. The emotional register we’re used to around disability observances tends to be “consideration” or “overcoming.” Pride Month tells a different story: disability isn’t something to overcome or to hide — it’s a natural part of who a person is. ...

Published date: 2026-07-28 · Reading time: 6 min · Word count: 1116 words · Author: Isaac

The Web Is Less Accessible Than a Year Ago — The WebAIM Million 2026 Report

WebAIM Million 2026 scanned the top million home pages: errors per page rose to 56.1, up 10.1% in a year, reversing years of progress. Covers the top 6 recurring errors and the ARIA paradox.

Published date: 2026-07-28 · Updated 2026-09-23 · Reading time: 8 min · Word count: 1618 words · Author: Isaac

Which Pages Do You Audit Out of Thousands?

Say you run an accessibility checker. You feed it a site’s URL, and the checker has to decide: which pages should it actually look at? Is the homepage enough? If so, you don’t have much basis for saying “this site is accessible” or “this site isn’t.” But checking every page isn’t realistic either — forums, blogs, and shopping sites can have hundreds or thousands of posts. Auditing all of them blows the time and cost budget. ...

Published date: 2026-07-28 · Reading time: 8 min · Word count: 3678 words · Author: Isaac

Accessibility E2E — Scanning with @axe-core/playwright

This is Part 15 of the “Frontend Testing, Done Right” series. Browse the full series · Glossary Whether a button has a name, you can tell by looking at that button. But whether its text contrasts enough with the background, whether the page declares a language, whether an id is duplicated — you can’t tell from one element. You have to look at the whole screen, and at the state it’s actually rendered in. That’s tiring to do by eye every time, which is exactly why you want an automated checking engine. ...

Published date: 2026-07-27 · Reading time: 11 min · Word count: 2248 words · Author: Isaac

Accessibility Evaluation Has a Standard Too — WCAG-EM 2.0, Twelve Years Later

W3C has published WCAG-EM 2.0, its accessibility evaluation methodology, twelve years after 1.0. What changed — from websites to apps, e-books and kiosks — the five-step procedure, sampling and random checks, and how it maps to Korea's certification.

Published date: 2026-07-24 · Updated 2026-08-12 · Reading time: 15 min · Word count: 2986 words · Author: Isaac
맨 위로