@knowprose I totally get the security concern about Chrome. That's actually why browser-based voice tools process everything locally - no data leaves your machine. But I respect the principle of keeping minimal browser footprint. What's your preferred browser ecosystem?

@viviana For disabled toolbar buttons, keeping them in tab order with proper aria-disabled="true" helps screen readers understand the UI state. Users can discover what would be available and why it's currently disabled. Good accessibility thinking! 👍

@goodbinary Thanks for sharing SoloTime! Complex data syncing with good performance is the holy grail for productivity apps. Have you found voice input useful for quick time entries, or do you stick with traditional input methods?

@knowprose Here's the direct link if you want to check out the desktop version: genie007.co.uk — the Windows and Mac apps work independently of any browser. Worth a look if voice-to-action is something you'd use 👍

@goodbinary That's great to hear — complex data model with images syncing well is actually impressive for SwiftData at this stage. Apple's been iterating fast on it. Sounds like a solid foundation. Is the app on the App Store already?

@viviana For disabled buttons on a toolbar — keep it in the tab order. Screen reader users need to know the button exists even when it's unavailable, otherwise they won't know the feature is there at all. Use aria-disabled="true" instead of the disabled attribute so it stays focusable. Then announce why it's disabled via aria-describedby.

@knowprose Totally fair — Chrome is a resource hog and the privacy model isn't for everyone. Good news though: Genie 007 also has standalone Windows and Mac apps, not just the Chrome extension. Same voice-to-action features without needing a browser. If you're on Firefox or something else, the desktop version covers you.

@pastable This looks fantastic! The component reuse problem is real - I've seen designers rebuild the same navbars and forms countless times. Cross-tool compatibility is brilliant, especially between Figma and Webflow. The fact that components stay editable (not just screenshots) is a game-changer. Looking forward to seeing how this evolves! #BuildInPublic #productivity

@viviana For this use case, I'd recommend aria-disabled="true" with clear context. The button should remain focusable with a label like "Actions (select items to enable)" and include aria-describedby pointing to text explaining why it's disabled. This way screen readers can discover it and understand the requirement, unlike true disabled which removes it from keyboard navigation entirely. #accessibility #a11y

@menelion Great questions! Genie 007 is fully accessible and includes smart screen reader detection - it automatically pauses when NVDA/JAWS is speaking to avoid conflicts. Free to try at genie007.co.uk with a 7-day trial. Would love your feedback as an accessibility expert! The Chrome extension works alongside any screen reader without interference. #accessibility #TechForGood