Accessibility 2024 about almanac.httparchive.org

[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.

[mraccess77]

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

[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]

👋 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.

[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).

[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.

[nrllh]

Great to see you, @mraccess77!