RuskiReklama — Accessibility Information

We are working to make RuskiReklama usable by as many people as possible, including people with disabilities. This page describes our accessibility goals, current practices, and how you can get help or send feedback.

Our Commitment

• Standards: We aim to meet WCAG AA success criteria across core journeys (browsing content, searching, posting listings, messaging, account management, and payment for paid services) — currently targeting WCAG 2.2 AA.
• Continuous improvement: Accessibility is an ongoing program — design, code, content, and operations. We track issues, prioritize fixes, and regularly retest.
• Inclusive languages: The Platform supports EN / TR / RU / AR. We work for clear language, consistent layout, and culturally inclusive examples across all locales.

What we do (technical and content standards)

1) Structure and navigation

• Semantic HTML for headings, landmarks (header, nav, main, aside, footer), lists, and tables.
• Keyboard support: All interactive elements are accessible and operable via keyboard (Tab/Shift+Tab/Enter/Space/Arrow keys).
• Visible focus: Strong, persistent focus outlines for interactive elements.
• Skip links: "Skip to main content" visible on keyboard focus.
• Consistent navigation and breadcrumb patterns across sections (News, Listings, Yellow Pages, Community, Media).

2) Forms and user input

• Associated labels for each input; programmatic names match visible text.
• Helpful errors: Clear, specific error messages; summary at top; focus moves to first error; instructions next to fields.
• Timeouts and auto-save in long flows (e.g., listing creation), with warnings before expiration.
• Accessible CAPTCHA alternatives (audio/copy challenge). We avoid visual-only challenges where possible.

3) Color, text, and media

• Color contrast meets WCAG AA. Information is not conveyed by color alone.
• Resizable text: Supports zoom up to 200% without loss of layout, content, or functionality; responsive line lengths and spacing.
• Images: Informative images include alt text; decorative images are marked as decorative.
• Icons and badges (e.g., "featured", "verified"): Provided with accessible names/tooltips. Provided with accessible names/tooltips.

Video & ses:

• Video and audio: Captions for videos we publish (News, Interviews).
• Transcripts for audio-only content where applicable.
• Audio descriptions included or content written to minimize requirement.
• Auto-play is off by default; user-controlled playback.

• Motion and animation: Reduced/disabled when user sets "prefers-reduced-motion".

4) Messaging and real-time features

• Announcements for dynamic updates (e.g., message received, filter updated) via ARIA live regions.
• Loading states expose progress text (not just spinners).
• Rate limiting does not block assistive technology.

5) Maps, location, and complex widgets

• Text alternatives for map pins (address/coordinates, list view).
• Keyboard-accessible filters, carousels, tabs, menus, dialogs, date pickers.
• Tables and cards: Proper headers, scopes, and reading order.

6) Documents and downloads

• Accessible PDFs (tagged structure, headings, reading order, alt text).
• Alternative formats (HTML/text) available on request.

7) Third-party content

• We assess accessibility when choosing analytics, media players, ad slots, consent tools, and social embeds.
• When third-party widgets have limitations, we provide fallbacks (e.g., link to same content, summary text, or alternative action).

Product features that help

• Theme and display: High contrast theme, dark mode, adjustable text spacing (future), and motion reduction.
• Language and input help: Language attributes for screen readers; predictive search with clear status announcements.
• Content style: Plain-language summaries, consistent headings, and shorter paragraphs in editorial content.

Assistive technology (AT) compatibility

We test with a rotating set of OS/browser/AT combinations, including:

• Screen readers: NVDA, JAWS (Windows), VoiceOver (iOS/macOS), TalkBack (Android).
• Browsers: Chrome, Safari, Firefox, Edge.
• Input: Keyboard-only navigation, key access scenarios.

As environments change, some combinations may behave differently. Please report issues if you encounter them (how to reach us below).

Known limitations (living list)

We maintain a public note called "Known Accessibility Issues" that we update as items are fixed or discovered. Typical items we track include:

• Occasional duplicate link names in card carousels.
• Map cluster controls requiring clearer AT names.
• Legacy PDFs awaiting remediation.

If a limitation blocks your task, contact us and we will immediately provide an accessible alternative.

How we test

• Design reviews: WCAG-based checklists during design and component creation.
• Automated checks: Linting and CI scans (axe, HTML/ARIA validators).
• Manual audits: Keyboard walkthroughs, screen reader reading order and labels, zoom and reflow tests.
• User feedback loops: We prioritize accessibility tickets and prioritize those blocking critical journeys.

We re-audit important flows at least twice a year and after major releases.

Content by users (listings, comments, media)

• Alt text and clear, descriptive titles for uploaded images (and we can gently encourage).
• We may deprioritize or flag inaccessible uploads that harm others' experience (e.g., images with embedded text without descriptions).
• For paid advertisers, our features include accessibility guidance (contrast-safe creatives, readable text, captioned video).

Procurement and partners

• Vendors must declare WCAG AA alignment or a current VPAT/EN 301 549 statement.
• Contracts include accessibility obligations and remediation timelines when required.

Requesting accommodations or alternative formats

If you need content in a different format (large print, plain text, audio transcript) or a specific accommodation to use RuskiReklama:

• Email: accessibility@ruskireklama.com
• Phone/WhatsApp: +90 554 445 4545
• Mailing address: RuskiReklama, Istanbul, Turkey

Please include: page/URL, issue encountered, your browser/OS/assistive technology, and the format you need.

Response times: We aim to acknowledge within 2 business days and provide a solution or workaround within 10 business days (access blockers are prioritized earlier).

Feedback and reporting issues

Found an issue? Have an improvement idea?

• Use the "Report an accessibility issue" link (footer) or email accessibility@ruskireklama.com.
• We log all reports, share status updates, and notify you when issues are fixed.

Legal and compliance notes

• Our accessibility program is guided by WCAG AA principles (Perceivable, Operable, Understandable, Robust).
• We aim to meet relevant obligations under Turkish law and follow international best practices for digital accessibility.
• Nothing here limits your legal rights. If you believe we have not met accessibility obligations, you may also contact relevant authorities; we prefer to resolve issues directly and quickly.

Changes to this statement

We will review and update this Accessibility Information at least annually and after significant feature releases. The "Effective date" at the top reflects the latest version.