Accessibility Statement
We believe the web should work for everyone. This statement explains how we strive to make takumiwebdev.com accessible, the standards we follow, and what to do if you encounter a barrier.
Effective January 1, 1970 · Last updated January 1, 1970
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our minimum standard. We test for keyboard navigation, screen-reader compatibility, color contrast, and readable text size. If you need help using any part of this site, or have a suggestion for improvement, please contact us at takumiwebsolutions@gmail.com — we will respond within one business day.
1. Our commitment
Takumi Web Development is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone, and applying the relevant accessibility standards to make our website usable by the widest possible audience, regardless of ability or technology.
Accessibility is part of our design and development process, not an afterthought. We design with sufficient color contrast, clear focus indicators, semantic HTML, and responsive layouts so content remains usable on large screens, small screens, and when magnified.
2. Standards we follow
We design and test our site to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA success criteria published by the World Wide Web Consortium (W3C). This includes:
- ◆Perceivable — text alternatives for images, captions and transcripts for video, resizable text, and sufficient contrast between text and background.
- ◆Operable — full keyboard navigation, visible focus indicators, no keyboard traps, and consistent navigation across pages.
- ◆Understandable — plain-language content, clear labels on forms, predictable behavior, and readable font sizing.
- ◆Robust — semantic HTML, valid ARIA where helpful, and compatibility with modern browsers and assistive technologies.
3. Accessibility features on this site
Practical features we have built in include:
- ◆Keyboard navigation — every interactive element (links, buttons, forms, modals) can be reached and operated using only the Tab, Enter, Space, and Escape keys.
- ◆Semantic HTML — we use proper headings, landmarks (main, nav, footer, article), lists, labels, and form associations so screen readers can navigate the page structure.
- ◆Alt text — meaningful images include descriptive alt text; decorative images use empty alt attributes so they are skipped by screen readers.
- ◆Color contrast — body text and UI elements meet at least WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text and UI components).
- ◆Focus management — focusable controls show clear focus rings, and modals/dialogs trap focus and return it to the triggering element when closed.
- ◆Responsive design — text and layout adapt to the user's device and zoom settings, supporting up to 200% browser zoom without loss of content or function.
- ◆ARIA labels — icon-only buttons and other controls without visible text use aria-label or aria-labelledby so screen-reader users know their purpose.
- ◆Reduced motion — decorative animations respect the user's prefers-reduced-motion setting, and essential content is never hidden behind motion effects.
4. Assistive technology compatibility
We test our site with modern assistive technologies and browsers, including but not limited to:
- ◆NVDA and JAWS screen readers on Windows.
- ◆VoiceOver on macOS and iOS.
- ◆Chrome, Firefox, Safari, and Edge with keyboard-only navigation.
- ◆Browser zoom and OS-level text scaling.
5. Known limitations and ongoing work
Some content or third-party integrations may not yet meet the same accessibility standard as the rest of the site. We are actively working to address these:
- ◆Third-party embeds — payment forms, maps, and video players provided by partners may have their own accessibility controls. We select providers that support accessibility and pass through their available settings.
- ◆Automated chat assistant — the floating assistant is keyboard-accessible and includes an aria-label, but we continue to improve focus handling and announcement timing.
- ◆PDFs and downloads — if we provide downloadable files, we aim to provide them in accessible formats or alongside HTML alternatives.
We conduct regular manual reviews and automated scans to catch regressions. If you find an issue not listed here, we want to hear about it.
6. How to give feedback or request help
We welcome your feedback on the accessibility of this site. If you encounter a barrier, need information in a different format, or have suggestions, please contact us:
- ◆Email: takumiwebsolutions@gmail.com
- ◆Contact form: takumiwebdev.com/contact
Please include the page URL, the assistive technology or browser you were using, and a brief description of the issue. We will acknowledge your message within one business day and work to resolve the issue promptly.
7. Formal complaints
If you are not satisfied with our response, you have the right to file a complaint with the relevant enforcement body. In the United States, you may contact the U.S. Department of Justice, Civil Rights Division. We are always willing to work directly with you first to find a practical solution.
8. Accessibility in the work we deliver
Accessibility is also built into the websites and apps we create for clients. We follow the same WCAG 2.2 Level AA target in our client work, provide semantic markup, keyboard-friendly navigation, and clear design-system tokens for contrast and focus. If you hire us, we can discuss accessibility scope, testing, and documentation as part of your project.
This statement was prepared by Takumi Web Development and is reviewed regularly. It is not a legal guarantee of conformance, but it reflects our genuine commitment to accessible design and our willingness to correct any issues that are brought to our attention.
