mozilla / mozilla/bedrock

A few accessibility and technical findings on mozilla.org

Open
#17,341 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug
Dominant language
HTML
Stars
1.3k
Forks
974
Avg merge
2d 18h
Merged PRs (30d)
21

Description

I was reviewing mozilla.org and noticed a few technical and accessibility issues that may be worth taking a look at:

  • 17 of 23 sampled images appear to be missing descriptive alt text.
  • 1 of 3 sampled form inputs appears to lack an associated label or aria-label.
  • No JSON-LD structured data was detected on the page.
  • /sitemap.xml was not found or did not appear to be valid XML.
  • The robots.txt file does not appear to reference a sitemap.
  • 6 render-blocking stylesheets were detected.
  • 14 external scripts were detected on the page.
  • No WebP/AVIF images were detected among the sampled images.

There are also several things that looked strong during the review, particularly the security headers, social metadata, link health, image dimensions, HTTPS configuration, and general UX structure.

I thought I'd pass these along in case they are useful to whoever maintains the site. Some of the findings may be intentional or already tracked internally, so please treat them simply as observations rather than definitive issues.

Best regards.

Contributor guide

Open the 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.

Research direction

The issue names no repository files or tests. Start by reproducing the reported accessibility, SEO, and performance observations on mozilla.org, then trace each finding to the relevant templates or assets. Done requires an agreed scope and verification of the selected fixes or intentional findings.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html, javascript
Domain
accessibility, performance, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.