Accessibility 2024

[nrllh]

Accessibility 2024

If you're interested in contributing to the Accessibility chapter of the 2024 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author, reviewer, analyst, and/or editor. You might be interested in exploring the changes to this year's version here.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@thibaudcolas	@thibaudcolas, @jcmpagel, @mraccess77	@shantsis, @dotjay	@rvth, @thibaudcolas	@Cherry	@tomvangoethem

Expand for more information about each role 👀

• The content team lead is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress.
• Authors are subject matter experts and lead the content direction for each chapter. Chapters typically have one or two authors. Authors are responsible for planning the outline of the chapter, analyzing stats and trends, and writing the annual report.
• Reviewers are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases.
• Analysts are responsible for researching the stats and trends used throughout the Almanac. Analysts work closely with authors and reviewers during the planning phase to give direction on the types of stats that are possible from the dataset, and during the analyzing/writing phases to ensure that the stats are used correctly.
• Editors are technical writers who have a penchant for both technical and non-technical content correctness. Editors have a mastery of the English language and work closely with authors to help wordsmith content and ensure that everything fits together as a cohesive unit.
• The section coordinator is the overall owner for all chapters within a section like "User Experience" or "Page Content" and helps to keep each chapter on schedule.

Note: The time commitment for each role varies by the chapter's scope and complexity as well as the number of contributors.

For an overview of how the roles work together at each phase of the project, see the Chapter Lifecycle doc.

Milestone checklist

0. Form the content team

• 📆 April 15 Complete program and content committee - 🔑 Organizing committee
  • The content team has at least one author, reviewer, and analyst.

1. Plan content

• 📆 May 1 First meeting to outline the chapter contents - 🔑 Content team
  • The content team has completed the chapter outline.

2. Gather data

• 📆 June 1 Custom metrics completed - 🔑 Analysts
  • Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress.
• 📆 June 1 HTTP Archive Crawl - 🔑 HA Team
  • HTTP Archive runs the June crawl.

3. Validate results

• 📆 August 15 Query Metrics & Save Results - 🔑 Analysts
  • Analysts have queried all metrics and saved the output.

4. Draft content

• 📆 September 15 First Draft of Chapter - 🔑 Authors
  • Authors has written the chapter.
• 📆 October 10 Review & Edit Chapter - 🔑 Reviewers & Editors
  • Reviewers and Editors has processed the the chapter.

5. Publication

• 📆 October 15 Chapter Publication (Markdown & PR) - 🔑 Authors
  • Authors has converted the chapter to markdown and drafted a PR.
• 📆 November 1 Launch of 2024 Web Almanac 🚀 - 🔑 Organizing committee

6. Virtual conference

• 📆 November 20 Virtual Conference - 🔑 Content Team

Chapter resources

Refer to these 2024 Accessibility resources throughout the content creation process:
📄 Google Docs for outlining and drafting content
🔍 SQL files for committing the queries used during analysis
📊 Google Sheets for saving the results of queries
📝 Markdown file for publishing content and managing public metadata
💻 Collab notebook for collaborative coding in Python - if needed
💬 #web-almanac-accessibility on Slack for team coordination

[shantsis]

Happy to join as a reviewer.

[Cherry]

As a first time Web Almanac contributor, I’d be happy to join this chapter as an editor.

[dotjay]

I’m interested in contributing as a reviewer.

[rvth]

I'm interested in being a reviewer or editor or potentially an analyst :)

[thibaudcolas]

I’d like to join this year as author and analyst like in 2022. Possibly also content lead.

I was personally very happy with the 2022 chapter’s approach to content, could do a re-run of that, though if someone else comes forward with a more ambitious vision I’d be happy too. One thing that’s new that I’d be interesting in trying out is to report on the accessibility issues found with different technologies, in the spirit of things like cwvtech.report.

[thibaudcolas]

👋 checking in to see who would be up for a coordination meeting next week? I have a bit of time this weekend to get back up to speed with HTTP Almanac methodologies and start planning a bit more.

If you know anyone else who might be interested in contributing to this, now is a great time to reach out. It’ll be important to confirm our team size & expertise so we adjust our goals accordingly.

---

If you haven’t already, consider joining the HTTP Archive Slack workspace, where there are channels for each of the chapters as well as each of the roles.

[mgifford]

I'd be happy to be part of a coordinating meeting. I'm curious what we can pull out of this data and what we might be able to do to advance it further than previous years.

[nrllh]

Given the content team's next deadline on May 1, it might be prudent to schedule a meeting close to this date, especially in anticipation of new contributors potentially joining in the coming days.

[mraccess77]

I have time to contribute and I'm offering to be a co-author of the accessibility chapter.

[nrllh]

Great to see you, @mraccess77!

[thibaudcolas]

Here’s an initial shared Google Docs for us to start work on the chapter – Accessibility (Web Almanac 2024). For people intending to contribute this year, please follow the instructions in there to request edit access.

At this stage there are two sections we need to refine in short order:

• Our chapter outline – we have a first draft outline due by May 1st. I’ve started one based on the outlines of the chapter in past years, and improvements we intended to make in 2022 but had to postpone.
• Our list of experiments – possible changes we’d want to do from the baseline of past years, that have to be further evaluated.

Given our limited team size, my assumption here is that we’re starting from the baseline of past years and deciding what to add or tweak.

---

For anyone who wants to contribute and hasn’t already done so, please join the HTTP Archive Slack workspace so we can coordinate further actions / meeting times (or let us know here if you want to participate but Slack doesn’t work for you).