# Make login screen accessible for keepass/ChromeIPass **URL:** \ **Category:** UX\ **Created:** [3월 3, 2017, 9:01오전 UTC](https://meta.discourse.org/t/make-login-screen-accessible-for-keepass-chromeipass/58288 "2017-03-03T09:01:44Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\ **Post date:** [3월 3, 2017, 10:03오전 UTC](https://meta.discourse.org/t/make-login-screen-accessible-for-keepass-chromeipass/58288/5 "2017-03-03T10:03:30Z")
It’s a [known limitation of ChromelPass](https://github.com/pfn/passifox/blob/master/documentation/chromeIPass.md#72-auto-detection-of-input-fields), but there’s a simple workaround. > ### 7.2 Auto detection of input fields > #### 7.2.1 Problem > > The detection does only detect fields which are **visible** when this function is called. > > It is only one time called automatically: After loading of the page finished. > New input fields which are created with JavaScript or with an AJAX-call cannot be detected, because they get visible **after** the auto detection was called. > For example an overlay for signin or signup could possibly not auto detected by chromeIPass because either the input fields are created just-in-time or they are hidden to the user while auto detection is running. > #### 7.2.2 Solution > > When it did not detect any username + password field combination you can click on the browser icon of chromeIPass and press the button “Redetect credential fields”. > You can also focus the visible username field or password field and press **Ctrl+Shift+U**. This will start a redetection for the focused field, too. --- _[View the full topic](https://meta.discourse.org/t/make-login-screen-accessible-for-keepass-chromeipass/58288)._