Accessibility at Fameoria
Fameoria aims to make the storefront, free tools, account area, order tracking and support paths usable with keyboards, screen readers, zoom and right-to-left Arabic layouts. Accessibility is an ongoing engineering and content responsibility.
Last reviewed August 2026
- WCAG 2.2 Level AA is the working target
- Keyboard, focus and semantic-control checks
- Text alternatives and scalable layouts
- Arabic right-to-left rendering included
01Our accessibility target
We use the Web Content Accessibility Guidelines WCAG 2.2 Level AA as the current design and testing target. This is a working target, not a blanket certification that every route, state, document or third-party page has been independently audited.
We prioritise barriers that prevent navigation, understanding, account access, ordering, payment handoff, order tracking, support or use of a core free tool.
02Navigation and interaction
The site aims to provide semantic landmarks, a skip link, logical heading order, keyboard-operable controls, visible focus, understandable link text and controls whose purpose is available to assistive technology. We build interaction so it does not depend on hover, colour or pointer precision alone.
Dialogs, menus, forms and dynamic tools are built to move or return focus predictably and to announce state changes in a way screen-reader users can follow.
03Text, colour and responsive layouts
Content is designed to support browser zoom, text resizing and narrow mobile screens without requiring two-dimensional scrolling for ordinary reading. Colour contrast, focus contrast, text spacing and touch-target size are reviewed as components are built.
Long Turkish words, mixed Arabic and western numerals, URLs, package tables and order identifiers are tested for wrapping rather than being hidden or allowed to overlap.
04Forms, errors and checkout
Account, cart, contact and tool forms come with labels, instructions and errors that screen readers can read and that do not rely on colour alone. The cart presents the service, target, quantity, currency and total before payment. Error messages name the field and say how to correct it.
The hosted payment page is operated by an external provider. Fameoria can improve the handoff and report provider barriers, but cannot directly control that page's markup or assistive-technology support.
05Free tools and dynamic results
Tool submission, loading, validation, errors and results stay keyboard accessible and readable after each update. Public media returned from Instagram, TikTok or another platform can contain captions, images or video supplied by third parties, so the original media's accessibility can vary.
Where a tool shows a thumbnail or profile image, we label the result by its purpose, even when an exact description of the third-party image is not available.
06Language and Arabic support
English and Turkish pages use left-to-right layout. Arabic pages use right-to-left document direction, while URLs, order numbers, currency values and other technical tokens may retain their natural direction. Navigation and directional icons are mirrored where meaning requires it.
Localization review includes wording, heading structure, truncation, mobile wrapping and mixed-direction content rather than translation alone.
07Known limitations
Potential limitations include legacy presentation patterns, rapidly changing third-party media, external payment pages, platform embeds and unusual mixed-direction strings. Some status changes may be harder to announce consistently across every browser and assistive-technology combination.
A known limitation is not treated as a reason to ignore a barrier. Reproducible problems affecting a core task are prioritised for correction or an accessible alternative.
08Testing and maintenance
Accessibility review combines automated checks with keyboard use, focus inspection, responsive screenshots, semantic review and selected screen-reader testing. Content changes are also checked because a technically accessible component can still become confusing through poor headings, links or alternative text.
The statement is updated when the target standard, known limitations, core architecture or reporting route changes.
09Report a barrier
Use Reach Us and include the page URL, task you were trying to complete, what happened, and the browser, device or assistive technology if relevant. You do not need to disclose a disability. Do not include passwords or sensitive payment information.
We aim to acknowledge a useful report and investigate the affected task. Resolution time depends on severity, reproducibility and whether a third-party provider controls the failing page. Where a prompt fix is not possible, ask for an alternative way to complete the task.
Found an accessibility barrier?
Tell us the page and task so we can reproduce it.