Heads-up: accessibility scan results for Angular Tailwind #52

Hi, I'm Duncan from NgBracket. Each quarter we scan a set of open-source Angular apps and templates
with our open-source tool @ngbracket/a11y-devtools, check
every finding by hand, and write up the results. Angular Tailwind was in this quarter's set.

This is a heads-up about that write-up, which goes on ngbracket.com. We'd like to name Angular Tailwind
in it, and we'll only do that if you're happy for us to. Your results are below, as they would appear.

What we found

• 27 icon-only buttons in the header, sidebar and table rows have no accessible name. The row and header
  checkboxes in the table (9) and the filter, sort and page-size selects (3) have no label either.
• Collapsed sidebar submenus and closed top-bar dropdowns stay in the Tab order. About 35 of the first 52
  Tab stops land on items you can't see. (Keyboard check)
• There's no <main> landmark, so all content sits outside landmarks. This one fix clears most of the
  104 region findings.
• Colour contrast is too low on 59 elements, mostly the status badges and muted small text.
• Five table headers are empty and the Table page has no <h1>.

Pages scanned on https://at.lanno.dev: Dashboard (/dashboard/nfts), Sign in (/auth/sign-in), Table (/components/table). Scanned on 15 October 2026 with a11y-devtools 0.18.2
and axe-core 4.14.0.

Across all 9 projects

The same few patterns turn up in most of the projects we scanned:

How to read this

An automated scan covers roughly a third of WCAG, and only on the pages it visits, so this isn't a
conformance verdict. We checked every finding by hand. "Keyboard check" marks findings from
a11y-devtools' keyboard checks, each confirmed in a browser. Framework patterns and demo-site extras are
left out. If you'd like the element-level details for any finding, we can send them.

What we're asking

• Are you happy for Angular Tailwind to be named? A yes here is all we need. If we don't hear back by
  10 November 2026, we won't name it, and its results will only count in the totals without names, like
  the table above.
• If anything here is wrong or out of date, tell us and we'll correct it. If Angular Tailwind is named,
  anything you fix before we publish (the week of 16 November 2026) will be listed as fixed.
• We're happy to open a PR for any of these if that would help.

You can reply here or email support@ngbracket.com.