🎨 Palette: 향상된 프리셋 버튼 접근성 및 활성 상태 마이크로 UX 개선

[seonghobae]

💡 변경 사항

saas_web.py의 용량 프리셋 버튼 UI에서 접근성과 시각적 피드백(Micro-UX)을 개선했습니다.

🎯 이유

• 접근성(A11y): 기존에는 프리셋 버튼들을 포함하는 컨테이너가 target_bytes 입력의 aria-describedby로 지정되어 있어, 사용자가 입력 필드에 포커스를 맞출 때마다 스크린 리더가 "25 MiB 100 MiB 500 MiB 1 GiB"를 모두 읽어버리는 불편함이 있었습니다.
• UX (시각적 피드백): 버튼을 클릭하여 값을 설정하거나 수동으로 프리셋과 동일한 값을 입력했을 때, 어떤 프리셋이 선택되었는지 시각적으로 알 수 없었습니다.

♿ 접근성 및 UX 개선 사항 상세

1. target_bytes 입력 필드의 aria-describedby에서 불필요한 버튼 컨테이너 참조를 제거하여 스크린 리더의 정보 과부하를 방지했습니다.
2. 버튼 컨테이너에 role="group" 과 aria-label="Target size presets"을 부여하여 스크린 리더에 명확한 맥락을 제공했습니다.
3. 각 프리셋 버튼에 aria-pressed 속성을 적용하고, JavaScript를 통해 현재 설정된 값과 일치하는 프리셋 버튼의 상태를 동적으로 업데이트합니다.
4. aria-pressed="true" 상태인 버튼의 배경색과 테두리색을 변경하여 선택된 프리셋을 시각적으로 강조합니다.
5. 유효하지 않은 HTML 구조(블록 레벨 요소를 포함하는 <p> 태그)를 <div> 태그로 수정하여 시맨틱 마크업을 준수했습니다.

📸 결과

버튼을 클릭하거나 값을 입력하면 해당되는 프리셋 버튼이 파란색(background-color: #0056b3)으로 강조됩니다. 100% 테스트 커버리지를 유지하며 Playwright를 통한 UI 검증을 완료했습니다.

---

PR created automatically by Jules for task 12490061308625860512 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[Copilot]

Pull request overview

Note

Copilot couldn't run its full agentic review because no GitHub Actions runner was available. Make sure your repository has a runner available to run Copilot's review, or add a copilot-setup-steps.yml file specifying one with the runs-on attribute. See the docs for more details.

Updates the target_bytes preset button UI to reduce screen reader noise and add a clear “active preset” state for better accessibility and micro-UX.

Changes:

• Removed the preset button container from target_bytes’s aria-describedby and added role="group" + aria-label to the container.
• Added aria-pressed toggling logic (JS) and corresponding active-state styling (CSS).
• Replaced invalid <p> wrappers with <div> wrappers to fix HTML semantics.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
saas_web.py	Adds a11y attributes, active-state styling, and JS state syncing for preset buttons; fixes invalid HTML structure.
.jules/palette.md	Documents the accessibility learning/action for preset buttons and active states.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[opencode-agent]

OpenCode Review Overview

• Head SHA: 501081a785eb2d0aaeea4407d93b2e773705bd66
• Workflow run: 28638216693
• Workflow attempt: 1
• Gate result: APPROVE (approval step)

Pull request overview

OpenCode reviewed the current-head bounded evidence and found no blocking issues.

Findings

No blocking findings.

Summary

Approval sufficiency: bounded evidence supplied affirmative approval evidence for changed files, coverage/docstring posture, risk surfaces, and current-head verification; approval is not based merely on the absence of known blockers.
Verification posture: CodeGraph evidence was initialized and bounded current-head evidence reviewed for changed-file evidence including .jules/palette.md, saas_web.py, tests/test_saas_web.py.
Linter/static: workflow/static review evidence is bounded by the current-head GitHub Checks gate and changed-file evidence.
TDD/regression: coverage execution evidence and focused changed hunks were reviewed from bounded-review-evidence.md.
Coverage: coverage execution evidence reports supported repository test suites passed.
Docstring coverage: coverage execution evidence reports configured repository docstring gates passed or docstring coverage was advisory.
DAG: CodeGraph/source-backed behavior map connects .jules/palette.md to the affected review, runtime, or workflow path and required checks.
PoC/execution: coverage-evidence job executed on the current head and reported PASS.
DDD/domain: workflow and repository-governance invariants were reviewed against changed files in bounded evidence.
CDD/context: CodeGraph evidence, changed-file history, and focused hunks were reviewed from bounded-review-evidence.md.
Similar issues: changed-file history evidence was reviewed for comparable local precedents.
Claim/concept check: bounded evidence, repository source, current-head workflow evidence, and, where numeric, scientific, statistical, or literature-backed claims are affected, original-paper/formula evidence and parameter-recovery expectations were used for claims.
Standards search: standards and external-source checks are delegated to configured OpenCode web_search/Context7/DeepWiki sources when applicable; no evidence-backed standards blocker is present in bounded evidence.
Compatibility/convention: changed workflow/script conventions, object naming, and reserved-word safety for schema/API/config/code surfaces were checked in bounded evidence.
Breaking-change/backcompat: deployment evidence and changed-file history were checked for backward-compatibility risk.
Performance: changed surfaces were checked for performance risk in bounded evidence.
Developer experience: changed automation, review, test, setup, and maintenance surfaces were checked for helpful or obstructive DX impact in bounded evidence.
User experience: connected user, operator, API, CLI, documentation, review-comment, status-check, rendering, and workflow-reader behavior was checked for contradictions against code, docs, and tests in bounded evidence.
Visual/DOM: Playwright visual, DOM locator, ARIA snapshot, console, and responsive evidence were checked when a web UI surface was present; for non-web surfaces, API/CLI/log/docs/workflow interaction evidence was reviewed instead.
Accessibility/i18n: accessibility, localization, and human-readable text surfaces were checked where UI, CLI, API message, docs, logs, or review text changed.
Supply-chain/license: dependency, package, model, container, and external-tool changes were checked in bounded evidence.
Packaging: package, build, test, lint, and security contracts were checked in bounded evidence.
Security/privacy: workflow-token, review-gate, and repository-automation security/privacy boundaries were checked in bounded evidence.

• Result: APPROVE
• Reason: The PR improves accessibility and micro-UX for preset buttons in the UI, with no unresolved review threads and passing test coverage.
• Head SHA: 501081a785eb2d0aaeea4407d93b2e773705bd66
• Workflow run: 28638216693
• Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Test: test_saas_web.py"]
  S2 --> I2["regression suite"]
  I2 --> R2["Review risk: Test: test_saas_web.py"]
  R2 --> V2["targeted test run"]

Loading

[opencode-agent]

Pull request overview

OpenCode reviewed the current-head bounded evidence and found no blocking issues.

Findings

No blocking findings.

Summary

Approval sufficiency: bounded evidence supplied affirmative approval evidence for changed files, coverage/docstring posture, risk surfaces, and current-head verification; approval is not based merely on the absence of known blockers.
Verification posture: CodeGraph evidence was initialized and bounded current-head evidence reviewed for changed-file evidence including .jules/palette.md, saas_web.py, tests/test_saas_web.py.
Linter/static: workflow/static review evidence is bounded by the current-head GitHub Checks gate and changed-file evidence.
TDD/regression: coverage execution evidence and focused changed hunks were reviewed from bounded-review-evidence.md.
Coverage: coverage execution evidence reports supported repository test suites passed.
Docstring coverage: coverage execution evidence reports configured repository docstring gates passed or docstring coverage was advisory.
DAG: CodeGraph/source-backed behavior map connects .jules/palette.md to the affected review, runtime, or workflow path and required checks.
PoC/execution: coverage-evidence job executed on the current head and reported PASS.
DDD/domain: workflow and repository-governance invariants were reviewed against changed files in bounded evidence.
CDD/context: CodeGraph evidence, changed-file history, and focused hunks were reviewed from bounded-review-evidence.md.
Similar issues: changed-file history evidence was reviewed for comparable local precedents.
Claim/concept check: bounded evidence, repository source, current-head workflow evidence, and, where numeric, scientific, statistical, or literature-backed claims are affected, original-paper/formula evidence and parameter-recovery expectations were used for claims.
Standards search: standards and external-source checks are delegated to configured OpenCode web_search/Context7/DeepWiki sources when applicable; no evidence-backed standards blocker is present in bounded evidence.
Compatibility/convention: changed workflow/script conventions, object naming, and reserved-word safety for schema/API/config/code surfaces were checked in bounded evidence.
Breaking-change/backcompat: deployment evidence and changed-file history were checked for backward-compatibility risk.
Performance: changed surfaces were checked for performance risk in bounded evidence.
Developer experience: changed automation, review, test, setup, and maintenance surfaces were checked for helpful or obstructive DX impact in bounded evidence.
User experience: connected user, operator, API, CLI, documentation, review-comment, status-check, rendering, and workflow-reader behavior was checked for contradictions against code, docs, and tests in bounded evidence.
Visual/DOM: Playwright visual, DOM locator, ARIA snapshot, console, and responsive evidence were checked when a web UI surface was present; for non-web surfaces, API/CLI/log/docs/workflow interaction evidence was reviewed instead.
Accessibility/i18n: accessibility, localization, and human-readable text surfaces were checked where UI, CLI, API message, docs, logs, or review text changed.
Supply-chain/license: dependency, package, model, container, and external-tool changes were checked in bounded evidence.
Packaging: package, build, test, lint, and security contracts were checked in bounded evidence.
Security/privacy: workflow-token, review-gate, and repository-automation security/privacy boundaries were checked in bounded evidence.

• Result: APPROVE
• Reason: The PR improves accessibility and micro-UX for preset buttons in the UI, with no unresolved review threads and passing test coverage.
• Head SHA: 501081a785eb2d0aaeea4407d93b2e773705bd66
• Workflow run: 28638216693
• Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Test: test_saas_web.py"]
  S2 --> I2["regression suite"]
  I2 --> R2["Review risk: Test: test_saas_web.py"]
  R2 --> V2["targeted test run"]

Loading