Accessibility Statement
Our WCAG 2.2 Level AA target, what the site already does for keyboard and screen-reader users, the limitations we know about with fix dates, and how to reach us.
Updated: September 3, 2026 · Author: Clothoff AI Editorial Team · Not legal advice
Summary
- Clothoff AI aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA for every page of this website, including the age gate, navigation, review tables, and the FAQ blocks.
- The site is a static, script-light publication: semantic landmarks, one H1 per page, visible focus outlines, native disclosure elements for FAQs, labeled tables, and text alternatives for every image.
- Known limitations as of September 3, 2026: sample video loops start automatically when scrolled into view and do not yet respect the reduced-motion preference; the age-gate dialog does not trap focus; the mobile menu button's label after opening is not yet in English.
- Keyboard access: the age gate's "I'm 18+" button and "Exit" link, the menu button, breadcrumbs, and every FAQ item can be reached and operated with Tab, Enter, and Space.
- Feedback: accessibility@clothoff.ai. We acknowledge messages within 5 business days and aim to fix blocking issues within 30 days.
- A plain Markdown version of every page is served at the same URL when a client requests text/markdown, which some reading tools can use as a simplified layout.
1. Standard and scope
Our target is WCAG 2.2, Level AA, the current W3C Recommendation for web content accessibility. WCAG 2.2 was published as a Recommendation in October 2023 and republished with errata on December 12, 2024; conforming content also conforms to WCAG 2.0 and 2.1 (W3C, WCAG 2.2, accessed September 3, 2026). The statement covers all pages of this website, including the Markdown variant served for text/markdown requests. It does not cover the websites of the reviewed third-party tools, which we link to but do not control.
Clothoff AI is a US-based publication. The Department of Justice's guidance explains that Title III of the Americans with Disabilities Act applies to "businesses that are open to the public" and points to the Web Content Accessibility Guidelines and the Section 508 Standards as existing technical standards that provide helpful guidance (ADA.gov, Guidance on Web Accessibility and the ADA, accessed September 3, 2026). Whether a specific site falls under Title III is a legal question we do not answer here; we follow the guidance as a matter of editorial policy. This statement is not legal advice, as the disclaimer explains.
2. What the site does today
The list below reflects the templates in production on September 3, 2026, as read from the site's HTML, CSS, and JavaScript.
- Structure. Each page declares its language (en-US), uses header, navigation, main, and footer landmarks, a single H1, and a logical H2–H3 order. Breadcrumb navigation is labeled and marks the current page.
- Keyboard and focus. All interactive controls are native links, buttons, or summary elements. A visible 2 px focus outline with offset is applied on keyboard focus. The mobile menu button exposes its expanded state to assistive technology and controls a labeled navigation region.
- Age gate. The 18+ confirmation is a dialog with a programmatic name and a modal flag. It contains a native "I'm 18+" button and an "Exit" link, both reachable with Tab and operable with Enter or Space. The choice is stored locally so the dialog does not reappear on every page.
- Images and video. Every image has descriptive alternative text that states when the image is AI-generated and that no real person is depicted (see the AI Content Policy). Video loops are muted, have no audio track, carry a text label, and use a poster image; they contain no information that is not also in text.
- Tables and FAQs. Data tables use header cells with scope attributes and scroll horizontally on narrow screens instead of truncating. FAQ items use native details/summary elements that work with keyboard and screen readers without custom scripts.
- Target size and zoom. Buttons meet a 44 px minimum height; layouts reflow at 400% zoom without horizontal scrolling of body text.
- Text alternative for the whole page. A Markdown version of each page is served at the same URL to clients that request text/markdown, providing a linear, style-free reading order.
3. Known limitations and planned fixes
We list issues we know about rather than claim full conformance. Each has an owner in the editorial team and a target window.
| Issue | WCAG criterion | Workaround today | Target |
|---|---|---|---|
| Sample video loops start automatically when they come within 250 px of the viewport and offer no pause control; the reduced-motion preference is not yet honored. | 2.2.2 Pause, Stop, Hide; 2.3.3 Animation from Interactions (AAA, advisory) | Browser settings that block autoplay stop the loops; the poster image and text label remain. | Within 30 days: honor prefers-reduced-motion and add a pause control. |
| The age-gate dialog does not move focus into itself on load and does not trap focus, so Tab can reach page content behind it. | 2.4.3 Focus Order; 2.4.11 Focus Not Obscured | The dialog is the first focusable region; Tab once reaches "Exit", twice reaches "I'm 18+". | Within 30 days: initial focus and focus containment. |
| After opening, the mobile menu button's accessible name is not yet in English. | 3.1.2 Language of Parts; 4.1.2 Name, Role, Value | The expanded state is announced correctly; the menu itself is in English. | Within 30 days. |
| Smooth scrolling for in-page links is always on and does not respect the reduced-motion preference. | 2.3.3 Animation from Interactions (AAA, advisory) | Browser reduced-motion settings that override page scrolling behavior. | Within 30 days. |
| No "skip to main content" link at the top of the page. | 2.4.1 Bypass Blocks | Landmark navigation with a screen reader; headings shortcuts; the header has 6 links before main content. | Within 30 days. |
| Color contrast of muted secondary text on dark panels has not yet been independently audited. | 1.4.3 Contrast (Minimum) | Browser high-contrast or forced-colors modes are supported by the native controls. | Audit within 90 days; report results here. |
Fixes are announced in the change log at the bottom of this page. If a limitation blocks you from using a page, write to accessibility@clothoff.ai and we will provide the content in an alternative format, normally the Markdown version or plain text by email, within 5 business days.
4. How we test
Every template change is checked before release with three methods: automated checks of the HTML for one H1, valid markup, alternative text, and labeled controls; a manual keyboard pass through the age gate, header, menu, breadcrumbs, tables, and FAQs at 375 px and 1280 px widths; and a screen-reader pass with a current desktop screen reader on the homepage and one review page. The editorial policy requires a dated note of each pass. A full-site audit against all WCAG 2.2 Level AA success criteria, including contrast measurement, is scheduled within 90 days of September 3, 2026 and will be summarized on this page.
5. Feedback and response targets
Tell us what did not work
Email accessibility@clothoff.ai with the page URL, what you tried to do, and your browser and assistive technology. Screenshots or recordings help but are optional.
Acknowledgment within 5 business days
We confirm receipt, assign the issue, and tell you whether a workaround or alternative format is available immediately.
Fix or written explanation within 30 days
Blocking issues are fixed within 30 days where technically feasible; otherwise we explain the constraint and the planned date, and we add the issue to the table above.
Accessibility feedback is counted in the transparency report under abuse and problem reports.
Contact
Accessibility: accessibility@clothoff.ai. General editorial matters: editorial@clothoff.ai. This statement was first published on September 3, 2026 and is reviewed whenever a template changes and at least every 6 months.
Change log
- September 3, 2026: first publication; 6 known limitations listed with target dates.
Related policies
- AI Content Policy — alt text and labeling of synthetic images
- Disclaimer — this statement is not legal advice
- Editorial Policy — release checks and dated test notes
- Report a problem — general issue form
- Transparency Report — counts of reports received
Frequently Asked Questions
Which accessibility standard does this website follow?
The target is WCAG 2.2 at Level AA, the current W3C Recommendation, republished with errata on December 12, 2024. Conformance is a goal, not a certified status: this page lists the criteria we know we do not yet meet, with target dates, and will be updated after the full audit planned within 90 days.
Can I pass the age gate with a keyboard?
Yes. The dialog contains a native Exit link and an I'm 18+ button; Tab reaches them and Enter or Space activates them. Focus is not yet moved into the dialog automatically or trapped inside it, which is listed as a known limitation with a fix targeted within 30 days.
Can I stop the sample videos from moving?
Not from the page itself yet. The loops are muted and start when scrolled into view; a pause control and support for the reduced-motion preference are targeted within 30 days. Until then, browser settings that block autoplay stop the loops, and the poster image and text label remain visible.
Is there a text-only version of the pages?
Yes. Every page is also served as Markdown at the same URL to clients that request text/markdown, giving a linear reading order without styling or scripts. If your reading software cannot request that format, email accessibility@clothoff.ai and we will send the page as plain text within 5 business days.
How do I report an accessibility problem?
Email accessibility@clothoff.ai with the page URL, what you tried to do, and your browser and assistive technology. We acknowledge within 5 business days, offer a workaround or alternative format where possible, and fix blocking issues within 30 days or explain the constraint and planned date.
Does the ADA require this website to be accessible?
The Department of Justice's guidance says Title III applies to businesses that are open to the public and names WCAG and the Section 508 Standards as technical standards that provide helpful guidance for websites. Whether a given site is covered is a legal question; we follow the guidance as editorial policy and do not give legal advice.