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

Does 3.2.6 Consistent Help allow for content that is under disclosure widget on one page in a set but not another? #2303

Closed
mraccess77 opened this issue Apr 7, 2022 · 6 comments · Fixed by #2612

Comments

@mraccess77
Copy link

Does 3.2.6 Consistent Help allow for content that is under disclosure widget on one page in a set but not another in the same set?

For example, the relative order is the same but on one page you must expand a section for contacting us and on another page it's in the same order but there is no disclosure control - it's just visible.

@alastc alastc added this to To do in WCAG 2.2 via automation Apr 20, 2022
@alastc
Copy link
Contributor

alastc commented Apr 20, 2022

Hi Jon,

The SC doesn't mention default visibility, so if it's in the same order I think it would pass. I'm not sure I'd want to raise that as an idea for people in the understanding doc!

@mraccess77
Copy link
Author

I'm only asking for clarification as these came up in real world sites - so I'm just looking for whatever the group agrees on as an answer rather than trying to argue for a specific outcome.

@alastc
Copy link
Contributor

alastc commented Jun 9, 2022

Like the other issue, I emailed the group, and no-one disagreed.

I don't think there's an understanding doc update to do, are you happy to close this?

@mraccess77
Copy link
Author

I'd prefer an understanding document update - but we do have this thread to refer back to as needed if you need to close the issue.

@alastc
Copy link
Contributor

alastc commented Jun 9, 2022

Hi Jon,

I'd like to keep normative and understanding updates separate, but we can keep this open if there is a useful update for the understanding doc.

Personally, I'd rather not include something about hiding the link as that undermines the aim. What would the benefit of including an example be?

@mraccess77
Copy link
Author

Just trying to create testing consistency - so perhaps it could go into a technique's test steps.

fstrr added a commit that referenced this issue Aug 12, 2022
1. Edited punctuation that is possibly the cause of the <a href="https://w3c.github.io/wcag/techniques/general/G220">current rendered version of this page</a> ending after Example 2.
2. Removed reference to single-page apps.
3. Added an example that hopefully addresses comments in #2303

Closes #2303
WCAG 2.2 automation moved this from To do to Done Nov 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
WCAG 2.2
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants