🎨 Palette: 기술 용어 약어에 대한 접근성 레이블 추가

.Jules/palette.md

@@ -19,15 +19,6 @@
 ## 2025-02-23 - Add Confirmation and Accessibility to Destructive Actions
 **Learning:** In the ERD canvas, destructive actions like deleting relations or business groups were missing user confirmation, increasing the chance of accidental data loss. Furthermore, mapped lists of interactive elements like "Business Group" rendering generic "삭제" (delete) buttons lacked `aria-label` context, creating ambiguous screen reader experiences.
 **Action:** Next time, always wrap destructive handlers with `window.confirm` dialogues and ensure mapped delete buttons receive an `aria-label` providing full context (e.g., `aria-label={`${itemName} 삭제`}`).
-## 2026-06-21 - Form Input Keyboard Navigation
-**Learning:** Standalone inputs without wrapping `<form>` elements inherently lack keyboard submission support, forcing users to switch from keyboard to mouse just to complete simple forms. Furthermore, modal dialogues holding inputs trap keyboard users unless explicit cancelation escapes are implemented.
-**Action:** When implementing inputs outside of standard `<form>` contexts or within custom modals, explicitly add `onKeyDown` handlers to support `Enter` for submission and `Escape` for cancelation.
-## 2024-06-23 - [Safe Scope UX Tooltips]
-**Learning:** Adding helpful `title` tooltips to text indicating truncation (e.g., "... N more") significantly improves usability for screen readers and confused users without changing visual layouts. More importantly, when working in a repository with aggressive penetration testing (like STRIX), UX changes must avoid touching components that handle sensitive inputs (like `App.tsx` dealing with DSNs). If an agent modifies a vulnerable file, even just for a UX change, the CI will run the pen-test against that file and block the PR.
-**Action:** Always verify the security posture of a file before making non-security changes to it. Prefer touching isolated display components (like `TableNode.tsx`) for UX enhancements rather than high-risk root components.
-## 2026-06-21 - Accessible Badges for Domain Abbreviations
-**Learning:** ERD diagrams heavily use domain abbreviations like "PK", "FK", and "NOT NULL". For visually capable users, these are quickly recognized. However, for screen reader users or beginners, abbreviations can be ambiguous. Wrapping them in generic `span`s without `aria-label` or `title` results in poor accessibility and misses an opportunity to provide helpful context.
-**Action:** When displaying technical or domain-specific abbreviations in badges (like PK/FK), consistently add a descriptive `title` (for mouse hover tooltips) and an `aria-label` (for screen readers) explaining the abbreviation's full meaning (e.g. "Primary Key").
 ## 2026-06-28 - STRIX Security Intersections and Strict Scope Enforcement
 **Learning:** In projects with strict AI code review agents and security scanners (like STRIX), making multiple distinct micro-UX improvements (e.g. across different files or disparate components) in a single task intended for "ONE micro-UX improvement" will cause a CI failure. Furthermore, applying UX improvements to elements that handle potentially sensitive data (e.g. DSNs, or rendering unsanitized user input) can inadvertently trigger security scanners if those elements contain pre-existing vulnerabilities, blocking the PR entirely.
 **Action:** When tasked with a single micro-UX improvement, strictly isolate the change to one specific element and file. When choosing an element, actively avoid modifying components that handle credentials or render un-escaped user inputs to avoid intersecting with existing unpatched security flaws.
@@ -43,3 +34,6 @@
 ## 2024-06-26 - [Abbreviation Comprehension in ERD Nodes]
 **Learning:** Users without deep database administration backgrounds may not immediately recognize domain-specific abbreviations like "PK" or "FK" rendered as minimalist badges inside dense ERD nodes.
 **Action:** Always provide `title` attributes on technical acronym badges (like Primary Key / Foreign Key) to ensure clarity and improve accessibility without cluttering the space-constrained node UI.
+## 2024-07-01 - Technical Abbreviations Accessibility
+**Learning:** Combining `title` and `aria-label` attributes on domain-specific abbreviations (e.g., PK, FK, NN) is crucial. While `title` provides visual hover feedback, screen readers may ignore it on `<abbr>` tags or non-interactive elements. Additionally, associated interactive elements like `<input type="checkbox">` should also have an explicit `aria-label` for full context.
+**Action:** When adding technical abbreviations in UI badges or forms, consistently use a descriptive `title` attribute for tooltips and an `aria-label` for screen readers to ensure accessibility across all modalities.