Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of “session” in “In Brief” in Understanding SC 3.3.7: Redundant Entry (Level A) #4246

Open
yatil opened this issue Feb 25, 2025 · 0 comments · May be fixed by #4247
Open

Use of “session” in “In Brief” in Understanding SC 3.3.7: Redundant Entry (Level A) #4246

yatil opened this issue Feb 25, 2025 · 0 comments · May be fixed by #4247

Comments

@yatil
Copy link
Contributor

yatil commented Feb 25, 2025

In the Understanding for 3.3.7, the “In Brief” section postulates:

What to do: Don't ask for the same information twice in the same session.

The word session is not mentioned in the success criterion. It is part of the Understanding, but only in the context that information does not need to be preserved between sessions.

When you have multiple processes within a session, the success criterion permits re-entry, even within the same session.

Example:

A user places an order and enters a different shipping address. If they place another order right after that, the changed shipping address does not need to be preserved despite the user being in the same session.

Introducing the word session in “In Brief” is unnecessary and I would recommend using “process” instead.

yatil added a commit to yatil/wcag that referenced this issue Feb 25, 2025
@yatil yatil linked a pull request Feb 25, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant