Accessibility Statement

🎯 Our target

3Tej aims to conform to Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. The standard covers four principles - perceivable, operable, understandable, robust - and we treat them as the baseline.

What we already do

⌨️ Keyboard navigation

Every interactive control (links, buttons, calculator inputs, dropdowns, search) is reachable and operable with the Tab key. Focus order follows the visual reading order. We use native HTML controls wherever possible so the browser's built-in keyboard behaviour (arrow keys in selects, space to toggle, etc.) works as expected. Focus indicators are visible with sufficient contrast.

🔊 Screen reader support

Pages use semantic HTML: <header>, <nav>, <main>, <section>, <article>, <footer>. Headings cascade from a single <h1>. Form labels are associated with inputs. Buttons and icon-only controls carry aria-label. Live result regions on calculators are marked with aria-live so screen readers announce updates.

🎨 Color and contrast

Body text and UI controls meet the 4.5:1 contrast ratio required by WCAG 2.1 AA against their backgrounds. Large text and graphical elements meet 3:1. We never rely on color alone to convey information - status messages, errors, and chart segments include text and/or shape cues.

🔠 Text and zoom

Text resizes up to 200% without loss of content or functionality. The page reflows for narrow viewports down to 320px. No element relies on a fixed pixel font size that breaks user zoom.

🖼️ Images and media

Decorative images carry empty alt="". Informative images carry descriptive alt text. Where a chart conveys data, a text equivalent (table or summary) is provided beside it. We don't autoplay video or audio; user-initiated playback only.

🌀 Motion and animation

Transitions are short (under 300ms typical) and avoid flashing. We honor the prefers-reduced-motion media query - if your OS sets it, decorative animation is suppressed.

📱 Touch and pointer

Interactive targets are at least 44×44 CSS pixels on mobile. We don't depend on hover-only behaviour for essential controls; mobile users always have a tap-equivalent path.

🌐 Language

The HTML lang attribute is set on every page. Body copy is written in plain English; we avoid jargon where the audience is general and define abbreviations on first use.

Known limitations

We're honest about what isn't perfect:

• Some games (Tetris, 2048, Wordle) have keyboard schemes that don't map cleanly to switch-control users. We're exploring alternative inputs.
• Some interactive charts generate visualisations on the fly; screen-reader access there relies on the adjacent data table.
• Third-party embedded ads (Google AdSense) are outside our DOM and may not match our accessibility level. We minimise their footprint.

If you hit one of these or something we haven't listed, tell us - that's how the list shrinks.

Our process

Accessibility checks are part of the build:

• Static linting flags missing alt text, label-less inputs, and similar.
• Automated axe-core runs on the main page templates.
• Manual keyboard-only sweeps when significant UI changes ship.
• Periodic screen-reader spot-checks with VoiceOver and NVDA.

Automated tooling catches roughly a third of issues. The rest comes from manual review and from people like you reporting things.

Report an issue

Email hi@3tej.com with "Accessibility" in the subject. Helpful detail:

• The page or tool URL.
• The assistive technology you're using (screen reader, switch, magnifier) and version.
• What you tried to do and what went wrong.
• A screenshot or short video, if visual.

We aim to acknowledge accessibility reports within 48 hours and to ship a fix or workaround within 30 days, sooner for blocking issues.

Conformance and standards

This statement is informed by:

• WCAG 2.1, W3C Recommendation.
• EN 301 549 for European public-sector references.
• Section 508 of the US Rehabilitation Act.

3Tej is partially conformant with WCAG 2.1 Level AA - we meet the criteria across the bulk of the site, with the noted limitations above. We aim for full conformance and treat any gap as a bug.