Sign In Register

Accessibility Statement

Last updated: 15 October 2026

Summary

  • Our target: WCAG 2.2 level AAA.
  • Current status: partially conformant. Eleven AAA criteria have been tested and are met; the rest are still in progress.
  • How we test: hands-on checks with the NVDA screen reader by someone who uses it every day, backed by technical measurements.
  • Found a barrier? Write to [email protected]. We handle every report as a defect to be fixed.

1. Our commitment

InfiArtt is a community in which many members are blind or have low vision. For us, accessibility is not an extra feature; it is the foundation that makes this site usable by the very people it was built for.

That is why we have written this statement plainly. It sets out what we have tested, what does not yet work well, and how to let us know if you run into difficulty. We would rather be open about our shortcomings than promise something we cannot yet demonstrate.

2. Standard and conformance status

We use the Web Content Accessibility Guidelines (WCAG) 2.2 as our reference, with level AAA as our target. That is one step above level AA, which many countries use as the legal minimum. We chose it because our users are the ones most affected if we stop at the minimum.

This site is currently partially conformant: some content and functions meet the standard, while others do not yet. We will not claim full conformance until every criterion has actually been tested. Section 4 lists the criteria that are met, and Section 5 lists those that are not.

3. Features available to you

Every page has an Accessibility Options menu. Your choices are saved in your browser, so they still apply when you return:

  • Large Text: enlarges all text without breaking the layout.
  • High Contrast: strengthens the difference between text and background colours.
  • Highlight Links: marks every link so it stands out from ordinary text.
  • Dyslexia-Friendly Font: switches to a typeface whose letters are easier to tell apart.
  • Comfortable Reading Mode: limits lines to about 77 characters, increases line spacing, and aligns text to the left.
  • Colour Scheme: several ready-made colour pairs, or a background and text colour of your own. The site tells you if your chosen pair has a contrast ratio below 7:1.

In addition:

  • The whole site can be used with a keyboard alone. A skip to main content link is always the first focus stop, and a list of keyboard shortcuts can be opened from the bottom of the page.
  • Breadcrumbs show where you are within the site.
  • Windows contrast themes are respected, so the site's colours follow your system settings.
  • Uploaded event recordings can be accompanied by a written transcript, which our team reviews before it appears on the event page.
  • Event certificates are produced as PDFs that screen readers can read.

4. Criteria tested and met

Our most recent testing took place on 13 September 2026 and covered the home page, the Knowledge Base and one of its articles, Posts, Projects, Events, the Forum, the Glossary, Announcements, Software, the Dev Center, Sign In, and Sign Up, each at screen widths of 1280 and 375 pixels. The following eleven AAA criteria are met on all of those pages:

  • 1.4.6 Contrast (Enhanced): text has a contrast ratio of at least 7:1.
  • 1.4.8 Visual Presentation: met through Comfortable Reading Mode and Colour Scheme.
  • 2.2.6 Timeouts: the time allowed for two-factor verification is stated up front, not after it has run out.
  • 2.3.3 Animation from Interactions: animation can be turned off.
  • 2.4.8 Location: breadcrumbs are provided.
  • 2.4.10 Section Headings: headings are complete and in order.
  • 2.4.12 Focus Not Obscured (Enhanced): the focused element is never hidden behind the navigation bar.
  • 2.4.13 Focus Appearance: the focus indicator is thick and high-contrast.
  • 2.5.5 Target Size (Enhanced): every touch target is at least 44×44 pixels.
  • 3.2.5 Change on Request: nothing changes unless you ask for it, and links that open a new tab say so in advance.
  • 3.3.9 Accessible Authentication (Enhanced): signing in never requires a cognitive function test.

Automated audit tools will always report two findings that the standard specifically exempts: the disabled letters in the Glossary's alphabetical browser (inactive components) and the Facebook logo circle among the social media links (a logotype).

5. Known limitations

We list these limitations as fully as we can. If you run into one of them, it is not because you did anything wrong; it is something we are still working on.

  • Some form error messages are still in English, even when the site is displayed in Indonesian. A full review of more than 25 forms is not yet complete (SC 3.3.6).
  • The Wall page does not yet have breadcrumbs like the other pages (SC 2.4.8).
  • Reading level has not yet been measured (SC 3.1.5).
  • Unusual words and abbreviations are not yet marked in body text. The mechanism exists and is connected to the Glossary, but has not yet been applied to content (SC 3.1.3 and 3.1.4).
  • Images of text have not yet been reviewed one by one (SC 1.4.9).
  • Media alternatives are incomplete. Transcripts are currently available only for uploaded event recordings that have been reviewed. Other videos, including those embedded from YouTube, do not yet have transcripts, and we do not yet provide audio description (SC 1.2.6, 1.2.8, and 1.2.9).

6. Third-party content

Some parts of the site are provided by third-party services, and their accessibility is outside our control:

  • Embedded videos play in the YouTube player.
  • The anti-bot check on the sign-in, sign-up, and forum forms uses Cloudflare Turnstile. It usually runs without asking anything of you; when needed, it shows a single checkbox that works with screen readers.
  • Fonts are loaded from Google Fonts.

If any of these services gets in your way, we would still like to know. We cannot change another provider's service, but we can almost always offer you another way to get done what you came to do.

7. How we test and maintain accessibility

Testing is carried out with the NVDA screen reader by someone who uses it day to day, not by switching it on briefly to check. Contrast ratios are calculated from the colours the browser actually displays, and touch target sizes are measured after animations finish so the results are accurate.

We use automated audit tools for initial screening, but never as the only basis for a judgement. Such tools can catch technical errors, but they cannot tell whether a page is comfortable to use.

To keep the site accessible as content grows, every article submitted for publication is checked automatically, including for images with missing or meaningless alternative text, skipped heading levels, unclear links, and tables without column headers. Editors review these results before an article is published.

8. Reporting a barrier

If you run into difficulty, please write to [email protected]. You do not need to know any technical terms or WCAG criterion numbers, and you do not need an account. Simply tell us:

  • which page you were on,
  • what you were trying to do, and
  • what happened.

If you use assistive technology, such as a screen reader or screen magnifier, mentioning its name and version is very helpful, but not required.

We handle every accessibility report as a defect to be fixed, not as a feature request. If a fix takes time, we will help you get done what you need in another way while we work on it.

9. About this statement

This statement was first prepared on 17 September 2026 and last updated on 15 October 2026. The assessment was carried out internally by the InfiArtt team. We update this statement whenever a criterion is completed or we discover a new limitation.