I am experiencing accessibility challenges with GitHub Actions when using assistive technologies (screen readers, keyboard navigation, or other accessibility tools).

[d4-core]

Select Topic Area

Question

GitHub Feature Area

Actions

Body

Hello GitHub Accessibility Team,

I am experiencing accessibility challenges with GitHub Actions when using assistive technologies (screen readers, keyboard navigation, or other accessibility tools). The issues I’ve noticed include:

• Difficulty navigating workflow logs and run histories using keyboard shortcuts or screen reader commands.
• Inconsistent labeling of buttons and controls, making it unclear what each action does.
• Limited support for notifications or feedback for completed/failed workflows when using accessibility tools.

These issues hinder the efficient management of repositories and workflows for users relying on assistive technology.

Additional context:

• This occurs on both personal and organizational accounts.
• Tested across multiple devices and browsers.
• The issues persist even with the latest GitHub interface updates.

I would greatly appreciate guidance on any workarounds and whether there are plans to improve accessibility in GitHub Actions for users relying on assistive technology.

Thank you for your attention and support.

[pratikrath126]

[d4-core]

@pratikrath126 Thank you for the update and for outlining the recommended steps.

I confirm that I am already using an up-to-date screen reader together with a modern, fully supported browser. I have also enabled the Reduce motion accessibility setting within GitHub. Despite these measures, the issue continues to occur consistently.

Because of this, I will proceed with submitting a detailed bug report through GitHub Support, including clear reproduction steps and any additional information that may assist the Accessibility team in their investigation.

I appreciate the continued efforts to improve accessibility across GitHub products and thank you for your attention to this matter.

[queenofcorgis]

@pratikrath126

We’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team.  You can read our updated Code of Conduct and the announcement for more details. Thank you for helping us maintain an authentic and beneficial space for everyone.

[panda667]

@pratikrath126

We’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team.  You can read our updated Code of Conduct and the announcement for more details. Thank you for helping us maintain an authentic and beneficial space for everyone.

Why do you think that was incorrect AI usage? That comes across as ableist, especially because certain tools people use to talk and express themselves do use AI.

It could also just be formal writing by someone who's eloquent.

If your going to call out "You're AI!!", you should really think about who posted it and the context.

[d4-core]

@panda667 I understand the goal of maintaining authentic discussions and reducing low-effort AI spam, but I also think it’s important to avoid making assumptions based purely on writing style.

Some people naturally write in a formal or polished manner, while others utilize accessibility tools, translation tools, or AI-assisted writing support to enhance their communication clarity. That alone shouldn’t automatically be treated as suspicious or misleading behavior.

I think the concern being raised here is less about moderation itself and more about the risk of normal communication styles being incorrectly labeled as “AI-generated” without clear context or evidence.

Focusing on the actual quality, accuracy, and usefulness of the content seems more productive than trying to determine whether someone’s writing “sounds AI.”

Otherwise, discussions can quickly shift from a constructive conversation into people policing writing styles instead of focusing on ideas.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[queenofcorgis]

@d4-core welcome to the community - thank you for posting! Could you share more details on the below so we can report this to our team:

• Difficulty navigating workflow logs and run histories using keyboard shortcuts or screen reader commands.
• Inconsistent labeling of buttons and controls, making it unclear what each action does.
• Limited support for notifications or feedback for completed/failed workflows when using accessibility tools.

We appreciate you helping us approve!

[d4-core]

Hi @queenofcorgis,

Here are the issues I encountered with accessibility:

Difficulty navigating workflow logs and run histories using keyboard shortcuts or screen reader commands: When reviewing workflow logs, focus sometimes jumps unexpectedly, and keyboard navigation is inconsistent, making it hard to follow the sequence of events.

Inconsistent labeling of buttons and controls, making it unclear what each action does: Some buttons in the workflow dashboard do not have descriptive labels, so it’s unclear whether they start, stop, or modify a workflow.

Limited support for notifications or feedback for completed/failed workflows when using accessibility tools: There’s no accessible alert or confirmation when a workflow fails or completes, so users relying on screen readers may miss critical updates.

We appreciate your helping us address these accessibility concerns!

— David

[pratikrath126]

Thank you for raising these important accessibility concerns. A few additional suggestions:

• Use the GitHub CLI (gh run view, gh run list) to interact with Actions from the terminal, which can be more accessible with your screen reader.
• For log navigation, the "Raw log" view (available via the three-dot menu) may have simpler focus management.
• Consider enabling browser extensions that enhance keyboard navigation if your screen reader interacts well with them.
• For notifications, you can set up external alerts via the Checks API or use third-party monitoring tools.
• Continue to provide specific reproducible steps in this discussion; the team uses such detailed feedback to prioritize fixes.
  Your contribution helps make GitHub more accessible for everyone.

[d4-core]

@pratikrath126 Thank you for the thoughtful suggestions and for taking accessibility feedback seriously.

I appreciate the recommendations around using the GitHub CLI, reviewing logs through the Raw log view, and exploring browser extensions or external notification options. These are helpful interim approaches while the underlying accessibility challenges are being evaluated.

Despite these workarounds, the core issues with keyboard navigation consistency, screen reader focus behavior, and reliable notifications within the native experience remain. I will continue documenting clear, reproducible steps so the team has concrete data to support prioritization and potential fixes.

Thanks again for your support and for helping move accessibility improvements forward for everyone.

[6feb-cell]

0. If you're colorblind

[6feb-cell]

#buyer

[6feb-cell]

TSI:6800

[6feb-cell]

()

[d4-core]

Hi @6feb-cell,
Not sure exactly what the context is yet, but if this relates to colorblind accessibility, you might want to clarify what specific issue you’re experiencing (e.g., UI contrast, chart color differentiation, icon visibility).
For discussions like this, providing:

• A brief description of the problem
• Where it occurs (which screen/page)
• Any relevant screenshots or examples
  helps others understand and assist.
  If the topic was something else (e.g., #buyer or the TSI:6800 tag), feel free to expand on what you need.
  Happy to help once there’s a bit more detail. 👍