| 开发者 | anblik |
|---|---|
| 更新时间 | 2026年6月20日 15:42 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-login.php with a slug you choose (e.g. /my-secret-door); when you enable it, the old URL can return 404 to block automated brute-force scanners.__() with the ananyoo-accessible-login text domain.ananyoo-accessible-login folder to the /wp-content/plugins/ directory, or install via Plugins → Add New → Upload Plugin.Yes. The plugin only customizes the WordPress login / register / lost-password / reset screens (the screens that live at wp-login.php), not your public theme.
No. Deactivating restores the default WordPress login screen exactly as it was. Your settings are preserved so you can reactivate later. Whether deleting the plugin removes your stored settings depends on your preference — see "What happens to my settings when I delete the plugin?" below.
You decide. On the Advanced tab there is a section called "When the plugin is deleted" with two choices:
Yes. On the Login URL & Security tab, set a custom slug (e.g. my-secret-door). The default /wp-login.php URL will return 404 for unauthenticated visitors, which blocks the vast majority of automated brute-force scanners.
Yes. The plugin loads the genuine WordPress login page — it never replaces it — and enhances the standard form through WordPress's own login hooks. So third-party CAPTCHA plugins that use those same hooks render and validate normally, including when you have set a custom login URL. For the best accessibility we recommend Cloudflare Turnstile or hCaptcha's accessible mode, which are generally friendlier to screen-reader and keyboard users than Google reCAPTCHA v2's "I'm not a robot" checkbox. The choice is entirely yours — the plugin imposes none.
The palettes are starting points, not jail cells. Every individual color is exposed as its own WordPress color picker on the Colors & Palette tab — change as many or as few as you like.
No. It only reveals the password the user themselves typed, in their own browser, after they explicitly click the toggle. WCAG 2.2 SC 3.3.8 recommends this exact pattern for accessible authentication.
Open Advanced → Export settings, copy the JSON, and paste it into Advanced → Import settings on the other site.
Yes. Each site has its own settings, including its own uninstall preference. On a network uninstall, each site's choice is respected independently — site A can keep its data while site B wipes its data in the same uninstall pass.
It is built with accessibility as the primary design goal rather than an afterthought: defaults, palettes and options are chosen with WCAG 2.2 AA in mind, and the customization controls are bounded so that common accessibility pitfalls (low contrast, hidden focus, tiny targets) are avoided by design.
/wp-login.php for unauthenticated visitors to block automated brute-force scanners.prefers-reduced-motion and Windows forced-colors mode.ananyoo-accessible-login text domain.