Accessibility statement
AIRank.ro is committed to being usable by as many people as possible, regardless of technology or ability.
Conformance status
Partially conformant with the standard below. "Partially" means some parts of the content don't yet fully meet the standard — see "Known issues" below, and the assistive-technology testing status under "How we tested".
Reference standard
The target is WCAG 2.1, level AA — the harmonized standard of presumption of conformity for the European Accessibility Act (EN 301 549), applicable to EU digital services since June 2026.
What this statement covers
All content on airank.ro, both languages (Romanian, English) — service pages, pricing, blog, Lab, the mini-audit widget, and contact forms. It does not cover linked external content (e.g. Cal.com, the LinkedIn profile).
What we did
Concrete measures, verified in a real browser, not just inferred from code:
- Semantic HTML5 structure: exactly one <h1> per page, zero heading-level skips, named landmarks (nav, sections, footer)
- Full keyboard navigation: visible focus on every control, Escape closes menus/dropdowns, hidden content is removed from tab order (inert)
- Color contrast checked on text and on form-control borders (minimum 3:1/4.5:1, as applicable)
- Forms with real visible labels (not just placeholder text) and error state communicated to screen readers
- Motion fully suppressed when the browser requests prefers-reduced-motion
- Automated build guard: any new page missing <main>, missing a unique <h1>, with an unlabeled form control, or with suppressed focus blocks publishing
- Automated testing with axe-core (WCAG 2.1 A/AA + 2.2 AA rules) across every published page
Known issues
We list them explicitly instead of hiding them — that's the point of a real statement.
WhatsApp floating button — contrast below threshold
The white glyph on #25D366 green has ~1.98:1 contrast, below the 3:1 threshold WCAG 1.4.11 requires for UI components. Green is WhatsApp's universal visual identity — we chose to keep it unchanged, so instant recognition (essential for a contact channel) isn't traded away for a contrast point. The button remains fully operable by keyboard and screen reader (accessible name, visible focus).
How we tested
Automated
axe-core (via Playwright) runs against every published page, with WCAG 2.1 level A/AA and WCAG 2.2 level AA rules. Zero violations at the last run.
Manual, keyboard-only
Every interactive component (nav menu, dropdowns, forms, the audit widget, FAQ accordions) was tested directly in a browser: focus order, Escape, focus traps, real ARIA state on open/close.
Screen reader (NVDA)
Planned, not yet run. A test protocol is ready (which pages, what to listen for, what counts as "passed") — automation can't confirm what a screen reader actually announces or whether reading order is logical. This statement will be updated to "conformant" once the protocol runs and any findings are fixed.
Ran into a problem?
If you hit an accessibility barrier on this site, tell us — we respond personally, not through an automated system. Email dragos@airank.ro or use the contact page, describing the page and the issue you ran into.