Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

IAAP Exam CPACC Topic 1 Question 24 Discussion

Actual exam question for IAAP's CPACC exam
Question #: 24
Topic #: 1
[All CPACC Questions]

According to Web Content Accessibility Guidelines (WCAG) 2.0, when focus cannot be moved away from a web component using only a keyboard, this is known as a

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Katina
5 months ago
I remember reading about this in the guidelines. It's definitely B) keyboard trap because it describes the situation accurately.
upvoted 0 times
...
Percy
5 months ago
Keyboard tab doesn't sound right to me. Locked focus could work, but I still think keyboard trap fits better.
upvoted 0 times
...
Moon
5 months ago
I'm not sure about this one. What about the other options like A) keyboard tab or C) locked focus?
upvoted 0 times
...
Jina
5 months ago
I agree with Percy. The term 'keyboard trap' aligns with the idea of being unable to move focus away using just the keyboard.
upvoted 0 times
...
Percy
5 months ago
I think the answer is B) keyboard trap. It makes sense because it traps the focus within a single web component.
upvoted 0 times
...
Tonette
5 months ago
Ok, I see your point. I'll go with B) keyboard trap as well.
upvoted 0 times
...
Sue
6 months ago
I agree with A keyboard trap is when focus is stuck in one place.
upvoted 0 times
...
Phillip
6 months ago
I'm pretty sure it's B because a keyboard trap prevents focus from being moved away.
upvoted 0 times
...
Tonette
6 months ago
Really? I thought it was C) locked focus.
upvoted 0 times
...
Phillip
7 months ago
I think the answer is B) keyboard trap.
upvoted 0 times
...
Theodora
8 months ago
Okay, let's think this through. 'Keyboard tab', 'locked focus', 'sticky key' - those don't really seem to fit the description of not being able to move focus away from a web component using only a keyboard. 'Keyboard trap' is the only one that makes sense to me.
upvoted 0 times
...
Frederic
8 months ago
Haha, 'sticky key'? What is this, a 90s computer game? Nah, it's gotta be 'keyboard trap'. I remember learning about that in my accessibility training. It's a common pitfall for developers to watch out for.
upvoted 0 times
Virgie
7 months ago
I agree. It's important for accessibility to avoid trapping users in certain areas of a website.
upvoted 0 times
...
Latonia
7 months ago
Yeah, you're right. It's a 'keyboard trap'. Developers need to ensure they can easily navigate websites using only a keyboard.
upvoted 0 times
...
...
Yolande
8 months ago
Keyboard trap, for sure. I can't imagine any of the other options really fitting the description provided in the question. Although, 'sticky key' does sound kind of fun. Maybe we could get the web components to do the moonwalk or something.
upvoted 0 times
...
Regenia
8 months ago
Ah yes, the dreaded keyboard trap! I remember running into that problem on one of my projects. It can be a real pain to debug and fix. I'm glad they're testing our knowledge of WCAG on this kind of issue.
upvoted 0 times
...
Rasheeda
8 months ago
Hmm, I think I know the answer to this one. Isn't a 'keyboard trap' when the focus gets stuck on a certain element and you can't navigate away from it using the keyboard? That sounds like the most plausible option to me.
upvoted 0 times
...
Odette
8 months ago
This is a tricky one. I'm not sure if I've encountered this issue before in my web development work. I wonder if it has to do with how the tabbing order is set up on the page?
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77