docs: say "display scale" where the statement and the issue form said zoom

There is no zoom in 1.5.0, so asking a reporter for their zoom level asks for
something the application does not have.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
poli0981andClaude Fable 5.2 committed 2026-11-10 20:01:03 +07:00
1 parent 2df161cb36
commit f9c5001dc4
2 files changed
+3 -3

No files matched your search

+2 -2
View File
@@ -1,5 +1,5 @@
name: Accessibility barrier
description: Something in PipDock is hard or impossible to use with a keyboard, a screen reader, high contrast or zoom
description: Something in PipDock is hard or impossible to use with a keyboard, a screen reader, high contrast or larger text
title: "[A11y]: "
labels: ["accessibility", "triage"]
body:
@@ -34,7 +34,7 @@ body:
id: assistive-tech
attributes:
label: Assistive technology and version, if any
placeholder: "Narrator (Windows 11 24H2) · NVDA 2026.3 · a contrast theme · 200% zoom · keyboard only"
placeholder: "Narrator (Windows 11 24H2) · NVDA 2026.3 · a contrast theme · 200% display scale · keyboard only"
- type: dropdown
id: where
attributes:
+1 -1
View File
@@ -161,7 +161,7 @@ Write in English or Vietnamese — tiếng Việt cũng được. It helps to in
- what you were trying to do, and what happened instead;
- the PipDock version (**About → This build**) and your Windows version;
- the assistive technology you use and its version, if any — Narrator, NVDA, a contrast theme,
zoom level, keyboard only;
display scale, keyboard only;
- whether it stops you completely or slows you down.
You do not have to work out the cause, name a WCAG criterion or propose a fix. "I could not get