# Make perspective logged out view more accessible

**URL:** <https://forum.inductiveautomation.com/t/make-perspective-logged-out-view-more-accessible/95212>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [August 27, 2024, 2:23pm UTC](https://forum.inductiveautomation.com/t/make-perspective-logged-out-view-more-accessible/95212 "2024-08-27T14:23:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![electricschmidt](https://avatars.discourse-cdn.com/v4/letter/e/6f9a4e/32.png) [@electricschmidt](https://forum.inductiveautomation.com/u/electricschmidt)\
**Post date:** [August 27, 2024, 2:23pm UTC](https://forum.inductiveautomation.com/t/make-perspective-logged-out-view-more-accessible/95212/1 "2024-08-27T14:23:16Z")

</div>

The current 'logged out' view in a perspective app has bad accessibility. After logging out of a perspective app you land on a page that looks a like this:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/2/b2efe0c3fd1c857b2ccf1bb7ce420bb2fd93e5ad.png)

The back button on the page isn't actually a `<button>` element but an `<a>` tag. If the `<a>` tag used an `href` attribute it would be possible to tab to the element and cause the navigation, but it doesn't, so there's currently no way of 'pressing' the back button on said page using just the keyboard. Refreshing by hitting F5 obviously works because you then land on the login screen but it would also be nice and not particularly difficult to add a `tabIndex` attribute to the `<a>` tag.

---

<div class="post-metadata">

**Author:** ![electricschmidt](https://avatars.discourse-cdn.com/v4/letter/e/6f9a4e/32.png) [@electricschmidt](https://forum.inductiveautomation.com/u/electricschmidt)\
**Post date:** [August 27, 2024, 3:08pm UTC](https://forum.inductiveautomation.com/t/make-perspective-logged-out-view-more-accessible/95212/2 "2024-08-27T15:08:18Z")

</div>

Turns out this is an actual issue when running the session through the perspective workstation. Tabbing to elements to focus them still works within the workstation browser but the F keys (i.e. F5 to refresh) do not, so without the use of a mouse a user could just get stuck on this window. I know I could roll my own logged out/log in pages that I could have focussable buttons on and such but the fix of adding a `tabIndex` to the `<a>` tag on this existing logged out screen seems an awful lot simpler.