Accessibility Statement

1. Who we are, and the words we use

1. "We", "us" means Pixel Glitch Studios, the operator of the Site. We do not currently publish a postal address; a business mailing address will appear here once the studio establishes one. Until then, contact us at support@islesofcalamity.com.
2. "The Game" has the meaning given to it in our Terms of Service. Our Terms do not presently define the other terms used here, so — so that this statement can be read on its own, and consistently with our other documents — "the Site" means the web pages described in clause 2.1; "Account" means the registered account through which you sign in to the Site and the Game; "Character" means a character created within an Account; and "Membership" means paid membership of the Game, sold as one-time duration credits and not currently offered for sale (see clause 10.2). "You" means the person reading this.
3. Contact for anything in this statement: support@islesofcalamity.com.

2. What this statement covers

1. This statement applies to the Site — the web pages served at islesofcalamity.com and its subdomains, including the public pages, the hiscores, player profiles, the Tideboard, news and articles, and the Account, registration, account-recovery, billing and status pages.
2. This statement does not cover the Game. The downloadable game client has not been assessed for accessibility, and we make no claim about it here — in either direction. The Game contains its own settings, and we are reviewing them; until that review is finished, we do not want a legal document to imply an assurance we have not earned.
3. This statement does not cover third-party content and services that we embed but do not control. See clause 7.

3. The standard we aim for

1. We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.1, Level AA.
2. We have chosen that standard because it is the benchmark most widely referenced by accessibility law in the places our players live, including the European standard EN 301 549 and guidance under the Americans with Disabilities Act.
3. Aiming at a standard is not the same as meeting it. Clause 4 states where we actually stand.

4. Conformance status — what we do and do not claim

1. We make no conformance claim. We do not claim that the Site is fully conformant, partially conformant, or conformant to any level of WCAG 2.1.
2. We cannot honestly claim a conformance level because the Site has never been audited by a third party, never been tested with assistive technology, and never been checked by an automated accessibility scanner. No accessibility test runs in our build or release process.
3. What follows in clause 5 is a self-assessment: a description, by the people who wrote the code, of accessibility features they deliberately built. It is a statement of intent and effort. It is not evidence of conformance, and it has not been verified by anyone independent of us.
4. Because nothing has been tested, you should assume there are accessibility barriers on the Site that we do not yet know about.

5. What we have built

The following are implemented across the Site. We describe them as things the code does, not as criteria we have passed.

5.1 Keyboard and navigation

1. A "Skip to main content" link is placed as the first focusable element on every page, so keyboard users can bypass the header and navigation. Every page carries a <main> landmark for it to jump to, and focus is moved into that landmark when the link is used. (Design intent: WCAG 2.4.1 Bypass Blocks.)
2. Pages use standard landmarks — header, navigation, main and footer.
3. Visible focus outlines are applied to links, buttons, navigation items and form fields, with a fallback for browsers that do not support :focus-visible. (Design intent: WCAG 2.4.7 Focus Visible; 2.4.11 Focus Appearance.)
4. The skill tables on the hiscores and the tabs on your Account are built as ARIA tab lists with arrow-key movement and a roving tab stop. The navigation's dropdown menus report their open or closed state to assistive technology.
5. The image gallery's larger-image view can be closed with the Escape key, moves focus to its close button when it opens, and returns focus to where you were when it closes.

5.2 Text, colour and motion

1. Body text is sized in relative units, so it respects the text size set in your browser or operating system and reflows when you zoom. (Design intent: WCAG 1.4.4 Resize Text.)
2. Colour choices in the shared theme were checked for contrast at specific points — the muted-ink text colour was darkened to clear 4.5:1 against the parchment background, form placeholder text is pinned to a 6.9:1 colour rather than the browser default of roughly 3.3:1, and the focus outline was changed to a colour clearing 3:1 after the original glow was measured at about 1.2:1. These were individual calculations during development, not a systematic audit of the whole palette.
3. The Site honours your operating system's "reduce motion" setting: animations and transitions are neutralised, and smooth scrolling is turned off, when you have that preference set. (Design intent: WCAG 2.3.3 Animation from Interactions.)
4. Every page declares its language as English. Every image carries an alternative-text attribute. (Design intent: WCAG 3.1.1 Language of Page; 1.1.1 Non-text Content.) We have not reviewed whether every one of those alternative texts is actually a good description.

5.3 Forms and messages

1. Form fields are labelled.
2. Error and confirmation messages are announced to screen readers — errors assertively, confirmations politely — through a single shared message component used by every form on every subdomain. (Design intent: WCAG 4.1.3 Status Messages.) This has been built, but never confirmed with a real screen reader.

6. Known limitations

We know about the following. Listing them is not an excuse — it is a record of work we owe you.

1. Nothing has been tested. No audit, no assistive-technology testing, no automated scan. This is the most significant limitation on this page, and every other statement here should be read in its light.
2. JavaScript is required. The navigation, the footer and the skip-to-content link are inserted by JavaScript. If JavaScript is unavailable or blocked, those elements do not exist on the page, and the skip link cannot help you. Much of the Site's content, including the hiscores and your Account, also loads through JavaScript.
3. The tab strips on our policy pages are not proper tabs. The hiscores and Account tabs are built with full ARIA tab semantics; the tab strip on the legal and policy pages is not, and is presented to assistive technology as an unlabelled row of buttons. We are aware this may make this very document harder to navigate than it should be.
4. Header and footer text sits on a background texture whose contrast with the text over it has not been measured.
5. Our palette has not been contrast-checked as a whole (see clause 5.2). Individual pairs were calculated; combinations we did not think about have not been.
6. We do not publish a target date for fixing these, because we would only be guessing. Clause 9 tells you how to hold us to a specific problem, which is more useful than a date we invented.

7. Third-party content we do not control

1. Some parts of the Site are provided by other companies. We do not control their code and cannot fix their accessibility:
   1. the anti-bot challenge shown when you register or recover an Account, provided by Cloudflare;
   2. payment checkout pages, if and when Membership is offered, hosted by Stripe or PayPal;
   3. video embeds from YouTube or Twitch, which appear only on news articles that include one.
2. We are not disclaiming responsibility for the outcome. If a third-party component stops you from completing something on the Site — registering, recovering your Account, or paying — contact us and we will find another way to get it done. Tell us what happened and we will also raise it with the provider.

8. Assistive technology

1. We have not tested the Site with any screen reader — not NVDA, JAWS, VoiceOver, TalkBack, or any other. We do not claim compatibility with any assistive technology, any browser, or any combination of the two.
2. The Site is built with standard HTML landmarks, ARIA roles and states in the places described in clause 5, which is the groundwork assistive technology relies on. Whether that groundwork actually delivers a good experience in your software is exactly what we have not verified.
3. The Site should work with browser zoom and with your own text-size, contrast and reduced-motion settings. It contains no audio or video that plays on our pages, so no captions or transcripts are required for our own content.
4. If you use assistive technology and something does not work, you are telling us something we do not know. Please do — see clause 9. We would rather hear it from you than not hear it at all.

9. Reporting an accessibility problem

1. Email support@islesofcalamity.com and say what you were trying to do, what happened, and — if you can — the page address, your browser, and any assistive technology you use. You can also contact us at support@islesofcalamity.com.
2. You can also use the support form on the Site. There is no dedicated "accessibility" category on that form today — please choose "General". We would rather tell you that than have your report sit in the wrong queue.
3. You do not need an Account, and you do not need to be signed in, to report an accessibility problem. Our support form accepts reports from people without an Account — which matters, because a barrier in registration or sign-in must not also be a barrier to telling us about it.
4. Our commitment: we aim to acknowledge your report within 14 days. We will tell you whether we can fix the problem, and if we can, what we intend to do. If we cannot fix it quickly, we will try to offer you another way to do the thing you were trying to do.
5. We are a very small team. We would rather commit to a response we can actually deliver than publish a service level we cannot meet.
6. If you are not satisfied with our response, clause 11 explains where else you can go.

10. The European Accessibility Act

1. The European Accessibility Act (Directive (EU) 2019/882) sets accessibility requirements for a range of products and services, and has applied to e-commerce services from 28 June 2025. It can apply to a business outside the EU that offers services to consumers in the EU.
2. Selling Membership to consumers in the EU would be an e-commerce service. Membership is not currently offered for sale, and no payment can currently be taken through the Site.
3. The Act exempts microenterprises that provide services from its accessibility requirements. A microenterprise is defined in the Act as a business employing fewer than 10 people and having either an annual turnover or an annual balance sheet total not exceeding €2 million.
4. We are not claiming that exemption in this statement. Whether it applies to us is a question of our size and turnover and is being confirmed; we would rather leave this clause open than assert an exemption we have not verified. This clause will be updated to state our position plainly once it is settled.
5. An exemption, if one applies, would remove a legal obligation. It would not remove a barrier, and it is not our reason for the state of clause 6. We intend to improve the Site's accessibility whether or not we are required to.

11. Your rights, and where to complain

1. Nothing in this statement limits your rights. This statement is a description of the Site's accessibility and a promise to respond. It is not a contract term, and it does not exclude or restrict any right or remedy you have under the law.
2. If you are a consumer in the European Union or the United Kingdom, you keep every right your national law gives you, regardless of anything said here or in any other document of ours. That includes rights that cannot be signed away by agreement. Where anything we publish conflicts with a mandatory rule of your national law, that rule wins.
3. In the EU, if you believe we are subject to the European Accessibility Act and are not meeting it, you may complain to the national authority responsible for enforcing that Act in the country where you live.
4. In the UK, the Equality Act 2010 may require service providers to make reasonable adjustments for disabled people. If you need an adjustment to use the Site, ask us — see clause 9.
5. In the United States, our home jurisdiction, the Americans with Disabilities Act and — because we are based in California — the Unruh Civil Rights Act may give you rights in respect of access to the Site.
6. You are always free to raise a concern with us first, and we would prefer that, but you are not required to do so before exercising any legal right.

12. How this statement was prepared, and when

1. This statement was prepared on 16 July 2026 and last reviewed on 16 July 2026.
2. It was prepared by self-assessment: a review of the Site's own source code by the people who wrote it, checking what accessibility features are actually implemented rather than what was intended. It was not prepared by an external accessibility specialist, and no user testing with disabled people informed it.
3. The self-assessment covered the Site's shared theme and shared page framework — the navigation, footer, skip link, focus styles, colour tokens, motion handling, form components and message announcements used across every page. It did not cover every page individually.
4. We will review this statement when we change the Site in a way that affects accessibility, when we test or audit it, and in any event when the facts it records stop being true. If you find a statement on this page that is no longer accurate, that is itself worth reporting under clause 9.