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.

Sign up for GitHub

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

Jump to bottom

Failure F50: settime-out should be setTimeout #4224

Open
dd8 opened this issue Feb 10, 2025 · 0 comments · May be fixed by #4238
Open

Failure F50: settime-out should be setTimeout #4224

dd8 opened this issue Feb 10, 2025 · 0 comments · May be fixed by #4238
Assignees
@fstrr
Labels
Editorial

Comments

@dd8
Copy link

dd8 commented Feb 10, 2025 •
edited
Loading

This looks like a long-standing typo in F50
https://www.w3.org/WAI/WCAG22/Techniques/failures/F50

settime-out in the following example should read setTimeout or window.setTimeout (both mean the same thing but the latter is easier to search for)

Edit: due to the typo the F50 example doesn't cause blinking, so isn't a failure of 2.2.2. The related technique SCR22 does use setTimeout

<script>
  // blink "on" state
  function show(){
      document.getElementById("blink1").style.visibility = "visible";
      settime-out("hide()", 450);
   }
    
   // blink "off" state
   function hide(){
      document.getElementById("blink1").style.visibility = "hidden";
      settime-out("show()", 450);
   }

   // kick it off
   show();
</script>
...
<span id="blink1">This content will blink</span>
fstrr added a commit that referenced this issue Feb 20, 2025
@fstrr
fix code sample bug
6819e5e 
Closes #4224
@fstrr fstrr linked a pull request Feb 20, 2025 that will close this issue
Open
@fstrr fstrr self-assigned this Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fstrr fstrr

Labels
Editorial
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix code sample bug w3c/wcag
2 participants
@dd8 @fstrr