TapNoiseA protected password field can restrict the keyboard events available to other apps. If a typing sound utility becomes silent there but works in an ordinary document, that can be expected security behaviour rather than a broken keyboard.
Compare without exposing a password
Test normal typing in a harmless TextEdit document. You do not need to paste a real password into an unprotected field to diagnose sound playback.
If feedback works in the document, the permission and playback path may already be healthy. Protected input or app-specific event handling can explain a difference limited to a particular field.
Respect the protection
Apple’s Secure Event Input mechanism is intended to limit observation of sensitive keyboard input. Do not disable a security feature just to make an aesthetic click sound continue everywhere.
The exact effect depends on the application and input mechanism. A sound continuing or stopping is not a complete security audit, and it cannot prove whether every other process is handling data appropriately.
If silence persists elsewhere
After leaving the protected field, test the ordinary document again. If the whole app is now silent, inspect the menu status, microphone quieting and selected output before changing permissions.
Use TapNoise’s ordinary no-sound checks for that broader problem. For data handling rather than event availability, read local counts versus keylogging.
Sources: Apple Technical Note TN2150: Secure Event Input, TapNoise troubleshooting.