Accessibility Statement

1. The commitment, and what it is not

The accessibility target for World of Bidders is WCAG 2.2 Level AA.

This statement does not claim conformance with that standard. Testing is ongoing, it has not covered every page and every assistive technology, and the known gaps are listed further down. Saying "fully accessible" without having tested it would be the least useful thing this page could do.

2. Keyboard support

Every interactive control can be reached and operated from the keyboard: Tab and Shift+Tab to move, Enter or Space to activate, Escape to close a dialog or a disclosure, and arrow keys inside grouped controls.

There are no keyboard traps in the interface: anything you can Tab into, you can Tab out of. A skip link at the top of every page jumps straight to the main content, and a second one jumps to the map on pages that have one.

3. Visible focus

The keyboard focus indicator is never removed. It is drawn with an offset so it stays visible against both the light and the dark theme, including on controls that sit on coloured surfaces.

If focus moves because you opened a dialog or a disclosure, it moves into the thing you opened, and it returns to the control you activated when you close it.

4. Reduced motion

The interface honours the operating system setting for reduced motion. When it is on, decorative transitions, hover rotations and camera animations are removed rather than merely shortened, and the map moves to a new position instead of flying to it.

Nothing in the product depends on motion to convey meaning, so removing it never removes information.

5. The text alternative to the map

The map is not the only way to use this service. Every territory has a page that works without any map at all, and it carries the same information: the name, the level, the parent hierarchy, the current Boss, the current price, the starting price, the reign duration, the minimum next target and the recent events.

Territories can be found through search and through the hierarchy links on those pages, and a claim can be made entirely from the territory page. Leaderboards and the activity feed are ordinary tables and lists, sortable from the keyboard.

6. Known limitations of the map

The interactive map is the least accessible part of this product, and these are its real limits rather than a general disclaimer:

• It requires WebGL. Browsers and devices without WebGL, or with it disabled, cannot render the map at all. Those visitors are shown the text alternative described above instead of a broken canvas.
• Polygon hover does not exist on touch. Highlighting a territory by pointing at it is a mouse behaviour. On touch devices a territory must be tapped, which selects it rather than previewing it.
• Small territories are hard to hit. Neighborhood-level polygons can be smaller than a comfortable touch target at low zoom. Search and the hierarchy links are the reliable route to them.
• The map canvas is a single element to a screen reader. Its contents are not exposed as an accessible tree. The territory pages, not the canvas, are where the information lives.

7. Colour and contrast

The product ships a light and a dark theme, both built from the same token set, and the theme follows your operating system preference until you choose one explicitly.

Text is intended to meet the WCAG 2.2 AA contrast ratios in both themes. Colour is never the only way something is communicated: claimed and unclaimed territories, sortable columns and status indicators all carry text or shape as well as colour.

8. Screen readers and structure

Pages use one main landmark, a single first-level heading, and headings in order. Long documents such as this one have a table of contents built from their own headings, with anchors that stay the same in Turkish and English.

Live updates to territory prices are announced through a polite live region, so they do not interrupt what you are reading. Tables have proper headers, and sort controls say which column they sort.

9. Forms, errors and payments

Every field has a visible label, not just a placeholder. Errors are announced, described in words rather than by colour alone, and focus moves to the first field that needs attention.

The payment step takes place on Stripe Checkout, which is outside this service. Its accessibility is Stripe's, not ours. Everything up to and after that step, including the acceptance checkboxes and the receipt, is part of this product and is covered by this statement.

10. Language

Every page declares its language, so a screen reader pronounces Turkish content with Turkish rules and English content with English rules. Switching language keeps you on the same page, and inside a policy document it keeps you at the same section.

11. Known issues being worked on

Beyond the map limitations above, these are the gaps currently known:

• Screen reader testing has focused on one combination and has not yet covered every browser and assistive technology pairing.
• Some dense data tables need horizontal scrolling at small window sizes.
• Automated checks are run, but they cannot find every issue, and a full manual audit of every page has not been completed.

This list is updated as issues are fixed and as new ones are found. It is not a complete inventory of every problem that exists.

12. Telling us about a barrier

If something here blocked you, please say so. Write to buzzicra@gmail.com and, if you can, include the page, what you were trying to do, and the browser and assistive technology you were using.

Reports about a barrier are treated as bugs, not as feature requests. If a fix will take time, you will be told what the workaround is in the meantime.

13. Review status

This statement is versioned like every other policy here, and the date it was last reviewed is the last-updated date shown at the top of this page.

It is reviewed when the interface changes materially and when a barrier is reported. Operator: Stimilon LLC, at 30 N Gould St, #54165, Sheridan, WY 82801, USA.