microsoft/autogen

Autogen website accessibility issues (low severity)

Open

#6090 opened on Mar 24, 2025

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Python (58,033 stars) (8,759 forks)batch import
documentationhelp wanted

Description

What happened?

Note: Some of these issues may be the duplicates of the same underlying problem. If you are unable to reproduce an issue, please mark the issue as fixed and leave a comment to that effect!

  • (9) Close button is not defined inside the 'hamburger' dialog. Problem Image
  • (12) No underline or change in color is appearing, when keyboard focus lands on links control. Problem Video -- @AndreaTang123 (https://github.com/microsoft/autogen/pull/6409)
  • (15) No underline is provided on left navigation controls. Problem Image
  • (16) Screen reader is announcing the information 'Navigation' twice when focus lands on left navigation control 'Installation'. Problem Video
  • (17) Screen reader is announcing the information 'list' twice when focus lands on link control 'Trace Logger Name'. Problem Video
  • (18) Multiple <H1> is defined on the page. Problem Video -- @LuluZhuu (https://github.com/microsoft/autogen/pull/6412)
  • (21) Underline/ Chevron is not defined for links present in ‘On This Page’ section. Problem Image
  • (23) Screen reader is announcing unwanted position information '1 of 1' when focus lands on Collapse button. Problem Video
  • (25) Back to Top control is not accessible with keyboard. Problem Video
  • (28) At 320*256 settings, Horizontal scrollbar appears on the page. Problem Image
  • (30) Incorrect role is defined for the 'Venv' and 'Conda' controls. Problem Video
  • (32) In browse mode, screen reader is focus moving to hidden after 'Discover and create your own' link control. Problem Video
  • (37) Screen reader not announcing out of list information. Problem Video
  • (38) Screen reader announcing unnecessary information as document when focus lands on copy control. Problem Image
  • (39) Screen reader announcing blank after 'Discover community projects' text. Problem Image
  • (42) In browse mode, screen reader focus order is not logical on tabs controls. Problem Video

docs source: https://github.com/microsoft/autogen/tree/main/python/packages/autogen-core/docs/src/user-guide docs custom js/css: https://github.com/microsoft/autogen/tree/main/python/packages/autogen-core/docs/src/_static

Which packages was the bug in?

Python Core (autogen-core)

AutoGen library version.

Python dev (main branch)

Other library version.

No response

Model used

No response

Model provider

None

Other model provider

No response

Python version

None

.NET version

None

Operating system

None

Contributor guide

Tech stack
htmlcssjavascript
Domain
accessibilityfrontend
Issue type
accessibility
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Knowledge of HTML and CSSUnderstanding of web accessibility (WCAG)Familiarity with ARIA rolesBasic JavaScript for interactive elements
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Review the documentation source located in /python/packages/autogen core/docs/src. Each unchecked issue likely corresponds to a specific component in the user guide pages. Look at the custom JavaScript and CSS in the static directory. For example, issue (9) about the hamburger dialog close button might require adding a button with 'aria label' inside the dialog. Check existing pull requests (e.g., #6409, #6412) to see how similar issues were fixed. Ensure any changes are tested for keyboard and screen reader accessibility.