Choosing hardware should not require a mouse, perfect eyesight or a steady hand. We build toward WCAG 2.1 level AA, test with a keyboard and a screen reader as part of ordinary work, and treat an accessibility report as a bug with priority rather than as a feature request. This statement describes what is in place today, what is still imperfect, and exactly how to reach a person about it.
Standard we work to
The target is WCAG 2.1 level AA across the whole site, in both Hebrew and English, on desktop and on mobile. Accessibility is treated as part of the definition of a finished feature, not as a later pass.
This statement reflects our own ongoing review of the site rather than an external audit, and it is updated as parts of the interface are reworked.
Keyboard and focus
Every interactive element · links, buttons, the questionnaire, sliders, selection lists, tabs, comparison controls and the newsletter form · can be reached and operated from the keyboard, in a logical order that follows the visual layout.
Focus is always visible, with a clear outline that holds up against both the light and the dark theme. Custom selection lists support arrow keys, Enter to choose and Escape to close, and they return focus to the control you opened them from.
Dialogs and expanded panels keep focus inside while they are open, and nothing steals focus or moves it unexpectedly while you are typing.
Screen readers and structure
Pages use real headings in order, landmark regions, lists and tables with header cells, so a screen reader can move through a page by structure instead of reading it top to bottom.
Every form field has a visible label that is programmatically connected to it, and error messages are tied to the field they describe rather than floating on their own.
Results that change without a page reload · newsletter status, price refreshes, forecast updates, compatibility warnings · are announced through live regions, so you learn about them without having to hunt for the change.
Icons that carry meaning have text alternatives; icons that are pure decoration are hidden from assistive technology so they do not add noise.
Vision, contrast and text
Light and dark themes both meet the AA contrast ratio for body text and interface controls, and a system-matching option follows whatever your device is set to.
Text scales with browser zoom up to 200 percent without content being cut off or trapped, and the layout reflows on narrow screens instead of forcing horizontal scrolling of the whole page.
Information is never carried by colour alone: a status, a warning or a best-price marker always has a word or an icon alongside the colour.
Images, part photos and game artwork carry alternative text that describes what matters about them in context.
Motion and timing
Animations are short and functional. If your device asks for reduced motion, transitions and entrance animations are toned down or removed.
Nothing flashes rapidly, nothing auto-plays sound, and no task is on a timer, so you can take as long as you need with the questionnaire.
Hebrew and right-to-left
The interface exists fully in Hebrew with a correct right-to-left layout: direction, alignment, icon mirroring, list order, form order and breadcrumbs all follow the language rather than being flipped by hand.
Numbers, prices, model names and units stay readable in both directions, and switching language keeps you on the same page instead of returning you to the home page.
Known limits we are working on
The 3D case view is visual by nature. The same information · dimensions, clearance, port layout, fit warnings · is always available as text in the part list beside it.
Wide comparison tables scroll horizontally on small screens. They remain keyboard scrollable and have header cells, but a narrow screen is still the hardest place to read them.
Some charts convey a trend visually first. Each one is accompanied by the underlying figures as text.
A small number of older catalogue entries still carry short alternative text, and we are rewriting them as those entries are revised.
Telling us about a problem
Write to hello@pcoptimizer.co.il with the page address, what you were trying to do, what happened instead, and the assistive technology, browser and device you used if you know them. That is usually enough for us to reproduce it.
We answer accessibility messages first, and if a fix will take time we will tell you how to get the same information in the meantime.
If you prefer not to write in English, Hebrew is entirely welcome, and a short description of the problem is far more useful than a technical one.
Questions about this document: hello@pcoptimizer.co.il
Privacy policyTerms of useCookies and storageDisclaimerHow ranking works