Accessibility

D&D Portal prioritises readable content, predictable spacing, clear page structure, and usable navigation.

No claim is made that every page, feature, or third-party resource is completely free from accessibility barriers.

• Present information in a clear and predictable structure.
• Support navigation by keyboard.
• Use readable fonts and comfortable line spacing.
• Maintain sufficient contrast between text and backgrounds.
• Provide visible focus indicators for interactive elements.
• Use meaningful headings and semantic HTML.
• Provide text alternatives for meaningful images.
• Avoid unnecessary animation and visual movement.
• Support visitors who prefer reduced motion.
• Ensure layouts remain usable on smaller screens.
• Avoid relying on colour alone to communicate important information.
• Use clear labels for buttons, links, inputs, and navigation controls.

Reading is the main purpose of the Wiki. Typography should make long rules text comfortable to scan and understand.

• Clearly distinguishable letters and numbers.
• Readable paragraph widths.
• Comfortable line height.
• Visible heading hierarchy.
• Consistent spacing between sections.
• Reduced visual clutter around dense reference text.

Interactive elements should be reachable and operable without a mouse.

• Move between links and controls using Tab.
• Activate links and buttons using Enter or Space where appropriate.
• Keep focus indicators visible.
• Avoid keyboard traps.
• Use semantic buttons for actions and links for navigation.

The interface should remain usable across desktop, tablet, and mobile layouts.

• Navigation should adapt between sidebar and smaller-screen layouts.
• Tables and card grids should remain readable on narrow screens.
• Text should not overlap images, controls, sidebars, or following content.
• Page headers should remain readable even when artwork is present.

Some pages are still being migrated to structured reusable components, and older content may need additional review.

Large tables, complex filters, visual cards, generated images, and third-party links require continued testing on different devices and assistive technologies.

Accessibility reports should include the affected URL, the browser or device, assistive technology details when relevant, and a short description of what could not be completed.

Reports can be sent through GitHub issues ↗ GitHub - Report a Problem Create a new issue Report a technical problem, incorrect page, broken feature, or other issue with the D&D Portal Wiki. Full link: https://github.com/toon-van-berkel/dnd-wiki/issues/new or email Email - Contact Toon van Berkel Send an email to Toon van Berkel regarding the D&D Portal Wiki, its content, or other related enquiries. Full link: mailto:toonvanberkel.public@gmail.com.