Accessibility
Accessibility is part of the product
HAAM wants haam.co to work for people with different bodies, senses, devices, languages, attention patterns, and ways of navigating. This statement explains the target, the current gaps, and how to report a barrier.
Commitment
The target is WCAG 2.2 Level AA
HAAM uses the Web Content Accessibility Guidelines as the main technical and editorial reference for this website. The four principles are perceivable, operable, understandable, and robust.
Perceivable
Content should remain understandable with zoom, high contrast, text alternatives, captions where needed, and without depending on colour alone.
Operable
Core navigation and controls should work with a keyboard, expose visible focus, avoid traps, and respect reduced-motion preferences where practical.
Understandable
Pages should use clear language, predictable navigation, descriptive headings, useful labels, and actionable error messages.
Robust
Semantic HTML, names, roles, values, and status messages should support modern browsers and assistive technologies.
Conformance status
This is a target, not a blanket certification
haam.co is a large and fast-changing site with production pages, archives, experiments, prototypes, generated content, and third-party integrations.
HAAM does not currently make a formal claim that every page and complete user journey fully conforms to WCAG 2.2 Level AA. The whole site has not yet completed an independent, page-by-page conformance audit.
New shared components and core journeys are designed with Level AA as the target. Accessibility issues are treated as product defects and improved as they are found, prioritising barriers that block access to information, contact, navigation, forms, services, and purchases.
Current approach
Accessibility is built into the shared system
- Semantic page landmarks and heading structures
- Keyboard-operable navigation and controls
- Visible focus treatment and logical focus order
- Text alternatives for meaningful images where available
- Responsive layouts that support zoom and reflow
- Colour contrast checks for shared interface components
- Reduced-motion support for compatible effects
- Accessible names, labels, validation, and status messages
- Clear page titles, descriptive links, and multiple discovery paths
- Ongoing automated checks plus manual review of important journeys
Known limitations
Some parts still need work
The following categories are the most likely to contain barriers. The exact issue can vary by page, browser, device, and assistive technology.
Experimental interfaces
Some labs, games, visual essays, prototypes, and older project pages use unusual interactions that may not yet provide an equally effective keyboard or screen-reader experience.
Motion and visual effects
Animated, cyberpunk, 3D, canvas, or seasonal design elements may create motion, density, contrast, or focus issues despite efforts to provide reduced-motion and simpler paths.
Media and archives
Some historical images, event media, video, documents, and reconstructed archive material may have incomplete text alternatives, captions, transcripts, or extended descriptions.
Third-party content
Embedded maps, social platforms, payment tools, external media, and linked services are partly controlled by their providers and may introduce barriers outside HAAM's direct control.
Feedback and assistance
Tell HAAM what blocked you
Accessibility feedback is useful even when the problem seems small or difficult to describe.
Email kris@haam.co with the page URL, what you were trying to do, what happened, and any relevant device, browser, keyboard, screen reader, voice control, zoom, or other assistive technology details.
You can also request information in a more accessible format or ask for another way to complete a website task. HAAM will try to acknowledge accessibility reports promptly and provide a practical response or workaround where possible.
Testing
Automated checks are only the first layer
The testing approach combines code review, automated accessibility checks, keyboard testing, zoom and reflow checks, contrast review, reduced-motion review, and assistive-technology spot checks on important journeys. Automated tools cannot establish full conformance on their own.
Core shared components are reviewed before individual experimental pages because improvements to navigation, typography, forms, focus behaviour, and layout can benefit the whole site at once.
Standards and law
The statement follows current web accessibility guidance
WCAG 2.2 is the primary technical target. Where applicable, HAAM also considers relevant European Union and Estonian accessibility requirements, including the European Accessibility Act. This statement does not assert that every HAAM page, product, or service falls within the Act's legal scope.
Statement history
Published with a clear review date
Statement published and last reviewed: . The statement will be updated when the conformance status, testing approach, known limitations, or contact process materially changes.