Explanation for Benefit nr.3 SC 3.2.5: Change on Request

[jake-abma]

https://www.w3.org/WAI/WCAG21/Understanding/change-on-request.html#benefits

The third benefit for 3.2.5 is:

Benefits

People with certain cognitive limitations do not get confused if automatic redirects are performed by the Web server instead of the browser.

Can someone explain this with a clear example? And is this always true, even with modern routing?

[jake-abma]

And is this only an issue because of the back button going back and forth? (Chrome will prevent this soon, or does already)

But, does this fall under "Change on Request?

[jake-abma]

Haha, need to read a bit further and got my answer... closing

[mraccess77]

Page redirects tend to show something and then it goes away -- making the user think they did something wrong or the page was hijacked or something. Server re-directs don't have this issue.

[jake-abma]

Benefit 3:

People with certain cognitive limitations do not get confused if automatic redirects are performed by the Web server instead of the browser.

Not per se, we even provide a sufficient technique via the browser:

Situation B: If automatic redirects are possible:
G110: Using an instant client-side redirect using one of the following techniques:
H76: Using meta refresh to create an instant client-side redirect

[jake-abma]

Since HTML5 it's possible to change the browser history, the following sentence must be changed as this is not correct:

People with certain cognitive limitations do not get confused if automatic redirects are performed by the Web server instead of the browser.

Redirects can be done client-side and the back button will work properly when setup this way.

[alastc]

Hi @jake-abma, can you suggest a change and add it to #754 please?