Time-based content extensions

Time-based content extensions is the removal of time barriers per WCAG: for content and functions with a time limit we give the user control — pause, stop, hide or extend the limit. This concerns auto-scrolling sliders/carousels, popup messages that disappear by themselves, countdowns, auto-refresh, and session/form timeouts. Honestly about the essence: a time limit is a barrier for people who need more time (motor/cognitive specifics, a screen reader, the elderly): they do not have time to read, click, fill in. We give them control over time. Honestly about non-removable limits, this matters: NOT every timer can simply be removed. For example, a session timeout is often needed for security (a bank, a personal account). For such cases the correct WCAG solution is not to disable it, but to WARN in advance and give the ability to extend with one action (rather than silently logging out with data loss). We will honestly say where a limit can be removed and where it can only be softened. Honestly about auto-motion: auto-sliders/carousels must have a pause — moving content interferes with many (not only people with disabilities). Honestly about coverage: this is about time barriers, not all of accessibility. Honestly about dependency: the scope depends on what exactly on the site has timers. Honestly about the effect: less data loss and fewer 'drop-outs' for users; we do not guarantee direct sales growth. Honestly about access: access to the code is needed. An important boundary: this is time limits; reduce-motion for animations is 826. Picture this: instead of 'did not have time to read/fill in — the message disappeared, the session dropped' — time control in the user's hands. The base price starts from 10,000 ₽ (depends on the number of timers/functions).

• An auto-slider scrolls by itself — no time to read.
• A message disappears by itself, you do not have time to see it.
• The session drops on timeout with loss of filled-in data.
• A countdown pressures and prevents calm action.

• Pause/stop of auto-scroll and moving content
• Control of disappearing messages (they do not vanish too fast)
• A session timeout warning + extension with one action
• The ability to extend/disable the limit where allowed
• An honest distinction: where we remove the limit, where we only soften it (security)
• Indicating boundaries (not every timer can be removed)
• Checking scenarios
• Handover and review with you

• The user controls time: pause/extend/disable
• Data is not lost due to timeout (warning + extension)
• Moving content can be stopped
• Time barriers removed (where safe — removed, where not — softened)

• We find everything with a time limit on the site; collect access
• We give control/pause/extension; for security limits — warning+extension
• We check scenarios, honestly distinguish removable and non-removable

• Can all time limits just be removed?

  Not all. Some timers can be removed (an auto-slider, disappearing messages). But some limits are needed for a reason — e.g. a session timeout for security (a bank, a personal account). For those the correct solution is not to disable it, but to warn in advance and allow extension with one action so as not to lose data. We will honestly say which is which.

• Why this, if most people manage in time?

  Because 'most' is not everyone. People with motor or cognitive specifics, screen-reader users, the elderly need more time: they do not have time to read, click, fill in — and lose data or drop out of the process. Control over time removes this barrier, and is also more convenient for everyone (moving content annoys many).

• Does this cover animations and motion?

  It partly overlaps, but 'disabling excess animation/motion' in general is a separate reduce-motion service (826), useful for people with vestibular disorders. Here the focus is on TIME limits (timers, timeouts, auto-change). We will honestly say whether you need both.