Accessibility 2021

[rviscomi]

Part II Chapter 9: Accessibility

If you're interested in contributing to the Accessibility chapter of the 2021 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.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@alextait1	@alextait1 @scottdavis99 @oluoluoxenfree	@ericwbailey @clottman @shantsis @digitala11ies	@OBTo	-	@OBTo

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

• May 31: The content team has at least one author, reviewer, and analyst

1. Plan content

• June 15 The content team has completed the chapter outline in the draft doc

2. Gather data

• June 30: Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress

• July 1 - 31: HTTP Archive runs the July crawl

3. Validate results

• September 30: Analysts have queried all metrics and saved the output to the results sheet

4. Draft content

• October 31: The content team has written, reviewed, and edited the chapter in the doc

5. Publication

• November 15: The completed chapter and all required metadata and figures are converted to markdown and submitted to GitHub

• December 1: Target launch date 🚀

Chapter resources

Refer to these 2021 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

[ericwbailey]

I'd like to offer my services as an Editor a Reviewer again this year, if you'll have me.

[tunetheweb]

Would love to have your expertise again this year @ericwbailey , but I think you mean Reviewer role (part of the chapter team who works on the content, in an advisory capacity and makes sure what's written is factually correct for the topic).

The Editor role is after the chapter's finished, and is is more about typos and consistency across the chapters, rather than the content necessarily (though as last year's editor of this chapter, and someone who's interesting in a11y, I couldn't help myself with a few comments and changes to the content while I was editing! 😁).

@rviscomi maybe we should remove the Editors box from the chapter issues for now to avoid this confusion?

[ericwbailey]

Reviewer right, argh. Sorry about that.

[rviscomi]

Great to have you back @ericwbailey!

@tunetheweb I'd like to more tightly integrate editors with content teams this year and have them involved during the drafting stage. This should help us avoid major changes or surprises right before publication, eg unexpected conventions.

[tunetheweb]

OK makes sense @rviscomi ! Will hopefully avoid some of the controversies we've had in the past on some of the conventions used which come as a bit of a surprise to authors!

[clottman]

I'd be happy to help as an editor for this chapter! I'm a software engineer and knowledgeable about accessibility, but also enjoy content editing from time to time.

[shantsis]

Happy to join as another editor too :)

[rviscomi]

Great to have you @clottman! Can I put you down as a peer reviewer since you've got accessibility experience?

@shantsis same question, would you be interested in reviewing?

[shantsis]

Great to have you @clottman! Can I put you down as a peer reviewer since you've got accessibility experience?

@shantsis same question, would you be interested in reviewing?

@rviscomi I'm not a subject matter expert but I do have an understanding of accessibility, so happy to help as a reviewer if that works

[clottman]

@rviscomi peer reviewer would be fine too!

[rviscomi]

Thank you both! Updated the team assignments at the top of the issue.