GOTHUI / DOCUMENTATION

Good structure comes first.

Names, focus, landmarks, feedback, and motion need deliberate care.

Semantic structure is the starting point

Use one main landmark, meaningful heading levels, explicit labels, real links for navigation, and buttons for actions. Decorative icons should be hidden from assistive technology; icon-only actions need accessible names.

Test the complete workflow

• Navigate with Tab, Shift+Tab, Enter, Space, and Escape. Focus must remain visible and return sensibly after an overlay closes.
• Check labels, validation messages, error-summary links, table captions, and status announcements with assistive technology.
• Use narrow screens and browser zoom. Long tables may scroll inside their region; the whole page should remain usable.
• Try light, dark, system, forced-color, reduced-motion, and print modes.

Native overlays and fallbacks

Dialog, Popover, and grouped disclosures depend on browser capabilities. Include ordinary-page or inline alternatives where needed. The interactions example demonstrates the native controls and fallback paths.

Motion without dependency

Entrances are short and finite. Reduced-motion preferences disable decoration without removing the content. Avoid using animation alone to communicate success, failure, or progress.

Evidence and limits

Go tests verify output contracts and source-color contrast. Browser automation checks representative flows and accessibility rules. Neither proves accessibility conformance or screen-reader usability for every application. Review your assembled interface with the assistive technologies you support.

Release review tracks keyboard, mobile layout, reduced motion, forced colors, print, and optional HTMX separately. See the current accessibility evidence for scope and outstanding checks.