> For the complete documentation index, see [llms.txt](https://www.information-architecture.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.information-architecture.world/wiad-organizer-guide/branding-marketing-+-promotion/updating-the-wiad-website/keep-accessibility-in-mind.md).

# Keep accessibility in mind

Accessibility helps more people participate in your event. Apply these practices to your GitBook content, local microsite, email, registration, and social posts.

Use [WCAG 2.2 Level AA](https://www.w3.org/WAI/WCAG22/quickref/) as a practical baseline.

### Write clear, structured content

Use headings in order. Use lists for related items. Give links meaningful names that describe their destination.

Keep essential information in text. Do not place dates, locations, registration links, or instructions only in images.

### Add useful alternative text

Add alt text to images that communicate information. Describe the image’s purpose in its context.

For example, use “A presenter speaks on stage at WIAD Tokyo” rather than “Event photo.” Include words shown in the image when they are important.

Leave decorative images without alt text. Do not repeat nearby text without adding context.

### Design for readability

Use sufficient contrast between text and its background. Do not use color as the only way to convey meaning.

Use readable text sizes and avoid placing long text over busy images. Provide captions or transcripts for video and audio content.

### Make registration and participation accessible

Choose registration tools that work with a keyboard and assistive technology. Label every form field clearly and explain errors in text.

Include venue access, parking, transit, seating, captions, interpretation, and contact details where relevant. Give attendees a simple way to request accommodations.

### Check before publishing

Review each page with a keyboard. Confirm that links, buttons, and forms have a visible focus state and work without a mouse.

Use an automated checker to identify common issues. Start with [WAVE](https://wave.webaim.org/) or [axe](https://www.deque.com/axe/). Automated tools do not replace manual testing.