Skip to content

Improve accessibility and reduced motion handling - #3

Open
Mluysk wants to merge 2 commits into
mainfrom
codex/enhance-website-elegance-and-aesthetics
Open

Improve accessibility and reduced motion handling#3
Mluysk wants to merge 2 commits into
mainfrom
codex/enhance-website-elegance-and-aesthetics

Conversation

@Mluysk

@Mluysk Mluysk commented Nov 4, 2025

Copy link
Copy Markdown
Owner

Summary

  • add keyboard focus indicators to navigation links, buttons, footer links, and insight cards for clearer accessibility cues
  • respect the prefers-reduced-motion setting in CSS and JavaScript, disabling smooth scrolling and long transitions when requested
  • update smooth scrolling helpers to honor motion preferences while keeping animation fallbacks when IntersectionObserver is unavailable

Testing


https://chatgpt.com/codex/tasks/task_e_69096039bab08322aea8f6af4499aa8d

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread styles.css Outdated
Comment on lines +513 to +515
transition: transform 0.3s ease, opacity 0.3s ease;
opacity: 0;
pointer-events: none;

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Keep hidden scroll button out of tab order

The scroll-to-top control is hidden by setting opacity: 0 and pointer-events: none when it lacks the visible class. Because the element remains in the DOM with its default tabindex, keyboard users can still tab to it while it is fully transparent, leaving focus on an invisible control with no perceivable focus outline. Consider removing the button from the tab sequence or hiding it with display: none/hidden until it is shown so that keyboard navigation does not land on an invisible element.

Useful? React with 👍 / 👎.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant