From f9c5001dc4d5cabbd784845dce089a4a299cea72 Mon Sep 17 00:00:00 2001 From: poli0981 <127664709+poli0981@users.noreply.github.com> Date: Tue, 10 Nov 2026 19:26:10 +0700 Subject: [PATCH] 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 --- .github/ISSUE_TEMPLATE/accessibility.yml | 4 ++-- ACCESSIBILITY.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/accessibility.yml b/.github/ISSUE_TEMPLATE/accessibility.yml index c9fb923..0fb5b6a 100644 --- a/.github/ISSUE_TEMPLATE/accessibility.yml +++ b/.github/ISSUE_TEMPLATE/accessibility.yml @@ -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: diff --git a/ACCESSIBILITY.md b/ACCESSIBILITY.md index 7e0bcb6..38d7250 100644 --- a/ACCESSIBILITY.md +++ b/ACCESSIBILITY.md @@ -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