Focus management

Focus management is setting up how 'focus' (the current active element) moves around the site during keyboard and screen-reader use: a visible focus indicator (so it is clear where you are), a logical and predictable focus order, keeping focus inside a modal while it is open (so you do not 'wander' to the background), returning focus to the original element after closing, moving focus to important changes/errors. Honestly about the role: focus is a critical part of accessibility, but NOT a standalone solution: it works together with keyboard navigation (806) and screen-reader accessibility (805). A single careful focus does not make an inaccessible site accessible — it is one of the layers. Honestly about dependency: the quality of focus management depends on how your interactive components are built (especially custom JS ones) — somewhere it is a fix, somewhere a rework of the component's logic. Honestly about the process: new modals/widgets again require correct focus — maintenance/discipline is needed. Honestly about the absolute: 'perfect for everyone' cannot be promised; honestly — 'significantly improves orientation for keyboard and screen readers'. Honestly about the effect: less 'lostness' and fewer errors for accessibility users; we do not guarantee direct sales growth. Honestly about access: access to the code/templates is needed. An important boundary: this is focus management; general keyboard navigation is 806, full modal accessibility is 819. Picture this: instead of 'it is unclear where focus is, and it wanders to the background with a modal open' — focus is visible, logical and not lost. The base price starts from 15,000 ₽ (depends on the number of components).

• It is unclear where focus is now — the indicator is invisible.
• Focus 'wanders' to the background with a modal open.
• After closing a window, focus does not return to place.
• The focus order is illogical, the user gets lost.

• A visible focus indicator across the whole site
• A logical and predictable focus order
• Keeping focus in modals (focus trap)
• Returning focus to the original element after closing
• Moving focus to important changes/errors
• Indicating boundaries (focus is a layer, not the whole solution; depends on components)
• A link with keyboard (806) and modals (819)
• Handover and review with you

• Focus is always visible and clear to the user
• A logical order without 'lostness'
• Focus is kept in modals and returned to place
• Better orientation for keyboard and screen readers

• We check focus behavior from keyboard/screen reader; collect access
• We set up visibility, order, trapping and return of focus
• We re-check, give a maintenance plan, review boundaries with you

• Is setting up focus enough to make the site accessible?

  No. Focus management is an important but one of the layers of accessibility. It works in combination with keyboard navigation (806) and screen-reader accessibility (805). Careful focus alone will not make an inaccessible site accessible — other measures are also needed. We will honestly advise what is needed as a whole.

• Why does the cost depend on components?

  Because the quality of focus depends on how your interactive elements are built. For standard ones it is a fix, for complex custom JS widgets it is sometimes a rework of the component's logic. So the scope and price depend on what exactly is on your site; we will estimate honestly by the facts.

• Does this need maintenance?

  Yes. New modals and widgets again require correct focus management, otherwise the same problems appear (focus wanders, does not return). Accessibility is a process: we will give recommendations so new components are made with correct focus from the start.