add support for screen readers for the AIO-interface

Steps to reproduce

1. Start up the AIO container using either docker run or the compose.yaml file.
2. Access https://ip.address.of.server:8080
3. The screen shows that Nextcloud AIO is already installed. There is a login link.

Expected behavior

On a fresh run (never used Nextcloud AIO before), it should prompt you to set a passphrase.

Actual behavior

The already-installed screen appears, giving you an option to log in with an existing passphrase even though none has been set as of yet.

Other information

Host OS

Ubuntu 24.04.4 LTS

Output of sudo docker info

docker info
Client: Docker Engine - Community
Version: 29.4.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.33.0
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v5.1.3
Path: /usr/libexec/docker/cli-plugins/docker-compose

Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 29.4.1
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 77c84241c7cbdd9b4eca2591793e3d4f4317c590
runc version: v1.3.5-0-g488fc13e
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.8.0-110-generic
Operating System: Ubuntu 24.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.749GiB
Name: nextcloud-prod
ID: 52570a59-9806-4f13-acda-b239ce2d559f
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
::1/128
127.0.0.0/8
Live Restore Enabled: false
Firewall Backend: iptables

Docker run command or docker-compose file that you used

I used the compose.yaml file in the repository, unchanged.

Output of sudo docker logs nextcloud-aio-mastercontainer

docker logs nextcloud-aio-mastercontainer
Trying to fix docker.sock permissions internally...
Creating docker group internally with id 988
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443
[30-Apr-2026 07:55:08] NOTICE: fpm is running, pid 168
[30-Apr-2026 07:55:08] NOTICE: ready to handle connections

Output of sudo docker inspect nextcloud-aio-mastercontainer

See my paste on Pastebin

Output of sudo docker ps -a

docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b26adf962304 ghcr.io/nextcloud-releases/all-in-one:latest "/start.sh" 2 minutes ago Up 2 minutes (healthy) 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 0.0.0.0:8443->8443/tcp, [::]:8443>8443/tcp, 9000/tcp

Other valuable info

None that I can think of. I have not attempted using the beta channel. If the passphrase is randomly generated and embedded in an image, I wouldn't know about it, as I am blind and rely on screen reading software.