From 84160a0574bb8db6d48954e48112c3e4e1ae1083 Mon Sep 17 00:00:00 2001 From: Lee Cattarin Date: Wed, 30 Sep 2026 16:51:12 -0700 Subject: [PATCH] update squarespace --- src/posts/2026/2026-08-05-visual-site-builders-accessibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/posts/2026/2026-08-05-visual-site-builders-accessibility.md b/src/posts/2026/2026-08-05-visual-site-builders-accessibility.md index d10ddc7c..950afdbb 100644 --- a/src/posts/2026/2026-08-05-visual-site-builders-accessibility.md +++ b/src/posts/2026/2026-08-05-visual-site-builders-accessibility.md @@ -138,7 +138,7 @@ I have written [further thoughts on Framer accessibility](/framer-accessibility) |---|---|---| | Semantic HTML | Template tested uses somewhat reasonable semantic HTML. Choice of what is considered a heading is a bit curious | 2 | | Keyboard navigation | Template tested has custom tab focus styling. Cannot be further edited, but custom that fits the theme is pretty standout. Skip link included in at least some templates. | 3 | -| Reading order | Imperfect and can't be edited by user. Block-based layout is a little too freeform to ensure proper reading order, so the user should be careful where they add things. Early testing indicates that reading order is determined by the *first* place a block is placed, and is never re-assessed by the builder. | 1 | +| Reading order | Imperfect and can't be edited by user. Block-based layout is a little too freeform to ensure proper reading order, so the user should be careful where they add things. It's a little unclear where the reading order follows from, because it doesn't always map to the blocks. | 1 | | Text alternatives | Supported. | 3 | | Color | Dark mode requires custom code or a plugin and seems *extremely* painful to accomplish. | 1 | | Other | This isn't an accessibility consideration, but *christ* is Squarespace a pain to work with. | 1 |