Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[workshop-playwright-qa] README: 1 QA finding(s) — readability

Closed Beginner friendly
  • Is something wrong?
#4,555 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
css
Domain
frontend

Research direction

The overflow comes from the README's "Other pages" side-quest link whose label contains an inline code element (gh aw run) with href #side-quest-08-01-codespaces-actions-write. Load the README at a 360×800 viewport and check that document.documentElement.scrollWidth exceeds clientWidth by 2px. The suggested selector is .markdown-body a code, or the link or list item itself. Done when scrollWidth no longer exceeds clientWidth by more than 1px at 360px, and the other viewports still render correctly.

Written by the indexing model from the issue text.

Description

accessibility bug

QA findings for README

Tested at: 2026-10-13T19:53:00Z
Viewports: small (360×800), medium (768×1024), desktop (1280×800), wide (1440×900), full-hd (1920×1080)

Automated QA covered 98 workshop pages × 5 viewports (490 page/viewport combinations), checking navigation, readability, accessibility, and brand alignment per /github-brand. This was the only finding produced.

# Viewport Category Description
1 small readability Horizontal document overflow of 2px detected on the README page ((127.0.0.1/redacted) document.documentElement.scrollWidthis362pxvsclientWidth 360px. Root cause: the link Fix Codespaces actions:write Errors When Running gh aw run(href#side-quest-08-01-codespaces-actions-write) contains an inline gh aw runelement that does not wrap, pushing its right edge tox=361.875px, just past the 360px` viewport boundary.
Reproduction
  1. Load (127.0.0.1/redacted) (workshop READMEpage) at a360×800` viewport.
  2. Observe document.documentElement.scrollWidth (362px) exceeds clientWidth (360px), producing a 2px horizontal scrollbar — fails the brand skill's hard requirement of "no horizontal document overflow greater than 1px".
  3. The offending element is a list-item link containing an inline <code> span (gh aw run) that doesn't break, in the "Other pages" / side-quest links section of the README.
Suggested fix

Allow the inline <code> elements inside these link labels to wrap (e.g. overflow-wrap: anywhere or word-break: break-word on .markdown-body a code, or on the link/list-item itself) so long link labels with inline code don't force a fixed-width overflow at narrow viewports.

Screenshots

README small viewport horizontal overflow near the "Fix Codespaces actions:write Errors" link

[!WARNING]

Firewall blocked 7 domains

The following domains were blocked by the firewall during workflow execution:

  • accounts.google.com
  • android.clients.google.com
  • clients2.google.com
  • registry.npmjs.org
  • update.googleapis.com
  • www.google.com
  • www.gstatic.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "accounts.google.com"
    - "android.clients.google.com"
    - "clients2.google.com"
    - "registry.npmjs.org"
    - "update.googleapis.com"
    - "www.google.com"
    - "www.gstatic.com"

See Network Configuration for more information.

Generated by 🎭 Workshop Playwright QA · copilot · auto · 169.1 AIC · ⌖ 5.02 AIC · ⊞ 9.5K · ◷

  • expires on Oct 14, 2026, 7:56 PM UTC
Dominant language
JavaScript
Stars
53
Forks
35
Avg merge
13h 50m
Merged PRs (30d)
14

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-aw-workshop

All issues in githubnext/gh-aw-workshop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.