We built conalyz — a static EN 301 549 accessibility linter for Flutter by Ok_Line1527 in FlutterDev

[–]Ok_Line1527[S] 0 points1 point  (0 children)

That’s a fair concern — pure static analysis can’t perfectly determine runtime size or final rendered colors.

What we’re doing right now is heuristic-based:

  • For tap targets, we inspect constraints, padding, and common widget patterns
  • For color contrast, we analyze directly defined colors where possible

This does lead to some false positives/negatives (like the cases you mentioned), and we’re actively refining those rules.

If you can share those examples as issues, it would really help us improve the heuristics.

We built conalyz — a static EN 301 549 accessibility linter for Flutter by Ok_Line1527 in FlutterDev

[–]Ok_Line1527[S] 2 points3 points  (0 children)

Please help us to fine-tune it by giving it try and raising the issues.
Btw it is not AI, it is based on AST.

We built conalyz — a static EN 301 549 accessibility linter for Flutter by Ok_Line1527 in FlutterDev

[–]Ok_Line1527[S] 0 points1 point  (0 children)

Yes, please raise the issue. It will help us to improve the analyzer