From 846ef7538f732fc3c099a72d52d84148583652c0 Mon Sep 17 00:00:00 2001 From: Lee Cattarin Date: Thu, 17 Sep 2026 17:57:33 -0700 Subject: [PATCH] note re dropdowns in framer --- src/posts/2026/2026-09-08-framer-accessibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/posts/2026/2026-09-08-framer-accessibility.md b/src/posts/2026/2026-09-08-framer-accessibility.md index 182d4c42..ba26f8ab 100644 --- a/src/posts/2026/2026-09-08-framer-accessibility.md +++ b/src/posts/2026/2026-09-08-framer-accessibility.md @@ -62,7 +62,7 @@ Links, buttons, and form controls are tabbable by default. When tagged as the co [Framer supports adding the tabindex attribute](https://www.framer.com/help/articles/tab-order-customization/). If you *must* do this for some reason, make sure to set its value to 0 - Framer defaults to 1. 0 will maintain the reading order established by layout and the left-hand sidebar; 1 will place the tabbable element first in the tabbing order. -I really recommend avoiding complex keyboard navigation like dropdowns. They seem pretty impossible to remediate. If possible, it requires *extensive* custom code. +I really recommend avoiding complex keyboard navigation like dropdowns (really not that complex, but... basically anything that doesn't just use the tab key suffers). They seem pretty impossible to remediate. If possible, it requires *extensive* custom code. ## Keyboard focus