Skip to content

fix: implement keyboard navigation and accessibility on canvas#35

Open
Babin123456 wants to merge 1 commit into
itzzavdhesh:mainfrom
Babin123456:fix/keyboard-navigation-accessibility
Open

fix: implement keyboard navigation and accessibility on canvas#35
Babin123456 wants to merge 1 commit into
itzzavdhesh:mainfrom
Babin123456:fix/keyboard-navigation-accessibility

Conversation

@Babin123456

@Babin123456 Babin123456 commented Jun 27, 2026

Copy link
Copy Markdown

Related Issue

Closes #24

Summary

This PR implements keyboard navigation and accessibility features on the flowchart canvas.

Changes Made

  • Added handleKeyDown callback to process panning (Arrow keys), zooming (+/-), and zoom resets (0).
  • Configured focus rings on the main canvas viewport.
  • Assigned tabIndex={0}, role="button", and dynamic ARIA descriptions to flowchart blocks.
  • Added key event selectors (Enter / Space) to activate block selections.
  • Added focus ring indicators to diamond and parallelogram shapes via Tailwind group styles.

Testing

  • Tested locally by focusing on the canvas container and panning/zooming using keyboard hotkeys.
  • Verified block selection by tabbing through nodes and hitting Space/Enter.

Screenshots

N/A

Impact

Improves accessibility conformance.

Checklist

  • Code follows project standards
  • Tested locally
  • No unrelated changes included
  • Responsive design verified
  • Accessibility considered

Summary by cubic

Adds keyboard navigation and accessibility to the flowchart canvas. Arrow keys pan, +/- zooms, 0 resets; the canvas and nodes are focusable, ARIA-labeled, show clear focus rings, and nodes can be selected with Enter or Space.

Written for commit 7229280. Summary will update on new commits.

Review in cubic

@vercel

vercel Bot commented Jun 27, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the itzzavdhesh's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added bug Something isn't working ELUSOC VETERAN labels Jun 27, 2026
@github-actions

Copy link
Copy Markdown

✅ Thanks! This PR is linked to #24 and will close it automatically when merged.

@coderabbitai

coderabbitai Bot commented Jun 27, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Babin123456, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 57 minutes and 52 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9cc7d436-7ec1-444e-ae82-2a3d7b0af893

📥 Commits

Reviewing files that changed from the base of the PR and between 22009dd and 7229280.

📒 Files selected for processing (1)
  • src/components/CenterCanvas.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/components/CenterCanvas.tsx">

<violation number="1" location="src/components/CenterCanvas.tsx:647">
P2: Keyboard selection handler is duplicated across all three node-render branches (decision, io, and default). The same `onKeyDown`, `tabIndex`, `role`, and `aria-label` pattern is repeated identically, creating maintainability and consistency risk.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

key={node.block.id}
id={`flow-node-${node.block.id}`}
onClick={() => onSelectBlock(node.block.id)}
onKeyDown={(e) => {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Keyboard selection handler is duplicated across all three node-render branches (decision, io, and default). The same onKeyDown, tabIndex, role, and aria-label pattern is repeated identically, creating maintainability and consistency risk.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At src/components/CenterCanvas.tsx, line 647:

<comment>Keyboard selection handler is duplicated across all three node-render branches (decision, io, and default). The same `onKeyDown`, `tabIndex`, `role`, and `aria-label` pattern is repeated identically, creating maintainability and consistency risk.</comment>

<file context>
@@ -614,13 +644,22 @@ export default function CenterCanvas({
                       key={node.block.id}
                       id={`flow-node-${node.block.id}`}
                       onClick={() => onSelectBlock(node.block.id)}
+                      onKeyDown={(e) => {
+                        if (e.key === 'Enter' || e.key === ' ') {
+                          e.preventDefault();
</file context>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working ELUSOC VETERAN

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] [ELUSoC_2026] Improve Canvas Accessibility with Keyboard Navigation

1 participant