CompTIA A+ Core 2 220-1202 tests how well you can work inside Windows Settings under Domain 1, Objective 1.6. This Part 3 guide focuses on the Settings areas that show up in real help desk tickets and on the exam: Ease of Access (Accessibility), Time and Language, Update and Security, Personalization, Apps, and Privacy. You'll see where each area lives in both Windows 10 and Windows 11, since the names and page layouts differ.
You'll also learn what techs change most often, what can safely be adjusted during support, and what should be left to policy or admin tools. Think of Windows Settings as a control panel for user experience and risk. A small change can fix a problem fast, or create a new one if it's done without care.
Make Windows easier to use with Accessibility settings
Accessibility is one of the fastest ways to improve a user's day. It also reduces repeat tickets. Many users won't ask for help directly. Instead, they report "the screen is weird," "my keyboard is broken," or "I can't follow meetings." Accessibility settings often explain those symptoms.
In Windows 11, go to Settings, Accessibility. In Windows 10, go to Settings, Ease of Access. The exam expects you to recognize both paths and the common tools, even if you don't memorize every toggle.
Support outcomes improve when you treat Accessibility as a normal configuration task, not a special case. For example, increasing text size can prevent mistakes in data entry. Turning on captions can reduce meeting confusion. In addition, some settings help users temporarily, like Magnifier during a screen-sharing session.
Vision and hearing tools that solve common user problems
When a user can't read text, start with Text size and Display scaling before you change screen resolution. Text size raises the UI font in many apps. Scaling enlarges the whole interface. Both changes are reversible and low risk.
Magnifier is a quick assist tool during remote support. It helps when the user has a high-resolution display and small UI elements. Narrator reads on-screen content aloud. It can be useful, but it may confuse users if enabled by accident. If a user reports unexpected voice output, check Narrator first.
Contrast also matters. Windows 11 offers Contrast themes. Windows 10 has High contrast. These modes help users with low vision, but they can also trigger "my colors changed" tickets. Color filters support color blindness and can reduce eye strain in some cases.
For hearing support, enable Captions (and live captions where available). Captions help users follow meetings, training videos, and recorded calls. Also check Mono audio if a user hears only part of the sound through one earbud. Some pages also include visual sound cues, such as sound notifications or flash alerts. Those can help users who miss audio prompts.
A practical support pattern works well here: confirm the problem, apply one setting, then test with the user's real task (a document, a meeting app, or the affected website).
Keyboard, mouse, and speech options for faster, cleaner support
Keyboard features can look like hardware failure. Sticky Keys changes how modifier keys work, so shortcuts behave differently. Toggle Keys adds sounds when Caps Lock, Num Lock, or Scroll Lock changes. Filter Keys can ignore brief keystrokes, which feels like input lag.
The On-screen keyboard is a strong workaround when a physical keyboard fails. It also helps during malware cleanup if a keyboard driver acts up. For mouse-related access, Mouse keys lets the numeric keypad move the pointer. Users sometimes enable it by mistake, then report "the mouse is drifting."
Windows also includes speech features. In Windows 11, Voice access supports hands-free control. Windows 10 and 11 also offer speech recognition options. For the exam, keep it high level: you should know where these tools live and what problems they solve.
A common gotcha: repeated Shift presses can trigger Sticky Keys prompts, and long Shift holds can trigger Filter Keys. If a user panics and clicks "Yes," they may feel locked out. During support, disable the shortcut prompts after you confirm the user doesn't need them.
Get Time and Language right to prevent login and app issues
Time and language settings look harmless, yet they break authentication and apps more often than many techs expect. Wrong time can cause certificate warnings, failed sign-ins, and Microsoft Store issues. Incorrect region or keyboard settings can also break data entry and sorting in business systems.
In Windows 11, use Settings, Time and language. In Windows 10, use Settings, Time and Language. The labels differ slightly, but the intent is the same.
Treat time problems like you'd treat a door lock with the wrong key. Everything might look fine, but the system won't accept it. When users report "Teams won't sign in," "VPN says certificate error," or "email keeps prompting," verify time and time zone early.
Time zone, clock sync, and daylight saving basics
Start with Set time automatically and Set time zone automatically when the device moves between locations. Laptops often travel, so an old time zone sticks around. Also check the time zone drop-down if automatic detection fails.
Clock sync matters for certificates and tokens. On a domain-joined PC, time usually syncs with domain controllers. On a non-domain PC, Windows syncs with an internet time source (NTP-based).