should Qwik & Qwik Router come with accessibility pre-built into it?

[Shane-Donlon]

What is it about?

No response

What's the motivation for this proposal?

Any other context or information you want to share:

High level question:
Should Qwik and Qwik Router (Version 2 +) come with accessibility pre-built into it?

The reason that I ask for Version 2 is that this would be a fundamental change in how the frameworks operates and a major Change seems like a good place to start this change in direction (if it is going to happen)

While the example is a low-level question this is only to further the conversion and is not specific to this event,
The question is of a high level nature.

Example:
The view transition event is fired under 1 circumstance,
does the browser support it.

My question:
Should this event fire / trigger if I have prefers reduced motion enabled?
In other words -
is it the responsibility of the framework to promote accessibility best practices?
or
is it the responsibility of the individual Developer to ensure that their work is done following accessibility best practices.

    
      if (document.startViewTransition) {
        const transition = document.startViewTransition(() => {
          executeDOMRender(ctx);
          restoreScroll();
        });
        const event = new CustomEvent('q:viewTransition', {
          detail: transition,
        });
        document.dispatchEvent(event);
    

Proposed Solution / Feature

Code examples

Not relevant this is a high level question.

if (document.startViewTransition && !window.matchMedia(
    "(prefers-reduced-motion: reduce)"
  ).matches) {
        const transition = document.startViewTransition(() => {
          executeDOMRender(ctx);
          restoreScroll();
        });
        const event = new CustomEvent('q:viewTransition', {
          detail: transition,
        });
        document.dispatchEvent(event);


### Links / References

_No response_