Accessibility Statement

Core practices

The site includes semantic HTML, visible focus states, skip links, accessible dialogs, responsive layouts and reduced-motion support.

• Navigation is available by keyboard.
• Dialogs use focus handling and close controls.
• Text and controls are designed to remain readable on mobile.

Accessibility widget

Visitors can increase text size, enable high contrast, underline links, pause animation, switch to a readable font, increase line spacing and reset preferences.

• Active options are visually marked as active.
• Preferences are stored locally in the browser.
• Reset clears all accessibility preferences.

Content and media

SwiftTool pages should use clear headings, descriptive link text, meaningful image alternatives and enough spacing for touch interaction.

• Admin-uploaded images should include useful alt text.
• Buttons and links should describe the action they perform.
• Long tables and code samples should scroll inside their own containers.

Known limitations

Some generated media outputs, third-party embeds or future integrations may require additional accessibility review before production launch.

• Review new components before publishing.
• Test important workflows with keyboard and mobile screen sizes.
• Keep legal and support content easy to reach from the footer.

Feedback

Accessibility issues can be reported through the support page. Include the page URL, device, browser and a short description of the problem.