search

HTTPArchive / almanac.httparchive.org

HTTP Archive's annual "State of the Web" report made by the web community
https://almanac.httparchive.org
Apache License 2.0
622 stars 182 forks source link

Accessibility 2021 #2147

Closed rviscomi closed 3 years ago

rviscomi commented 3 years ago

Part II Chapter 9: Accessibility

Accessibility illustration

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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Content-Team-Leads'-Guide)** is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress. - **[Authors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Authors'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Reviewers'-Guide)** are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases. - **[Analysts](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Analysts'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Editors'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Section-Leads'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle) doc.

Milestone checklist

0. Form the content team

1. Plan content

2. Gather data

3. Validate results

4. Draft content

5. Publication

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 commented 3 years ago

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

tunetheweb commented 3 years ago

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 commented 3 years ago

Reviewer right, argh. Sorry about that.

rviscomi commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

Happy to join as another editor too :)

rviscomi commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

@rviscomi peer reviewer would be fine too!

rviscomi commented 3 years ago

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

alextait1 commented 3 years ago

Hey @rviscomi I'm down to help author again this year (and happy to be jumping in earlier this time haha)

rviscomi commented 3 years ago

Glad to have you back @alextait1! Tentatively putting you down as a reviewer as we leave the author nominations open for a while longer.

alextait1 commented 3 years ago

Glad to have you back @alextait1! Tentatively putting you down as a reviewer as we leave the author nominations open for a while longer.

Sounds great!

scottdavis99 commented 3 years ago

Hello! I'd love to contribute as an author for the Accessibility section.

I've written half a dozen books, hundreds of articles, and I speak on the international software conference circuit on Web Accessibility.

My Amazon author page: https://smile.amazon.com/Scott-Davis/e/B001ILMANK

A popular keynote of mine: "It's Spelled 'Accessibility', not 'Disability" (~15 minutes) https://www.youtube.com/watch?v=dp_h2VfW0sc

rviscomi commented 3 years ago

Great to have you @scottdavis99! Tentatively putting you down as a reviewer before we make author picks (more info: #2165)

oluoluoxenfree commented 3 years ago

I'd also love to help as a reviewer or elsewise this year!

rviscomi commented 3 years ago

Great to have you back @oluoluoxenfree!

@ericwbailey @clottman @shantsis @alextait1 @scottdavis99 @oluoluoxenfree please join the collaborative doc and request edit access to get a head start planning the content for the chapter. At a high level, what topics could you start adding to the outline? We'll start selecting content team leads this week.

shantsis commented 3 years ago

Great to have you back @oluoluoxenfree!

@ericwbailey @clottman @shantsis @alextait1 @scottdavis99 @oluoluoxenfree please join the collaborative doc and request edit access to get a head start planning the content for the chapter. At a high level, what topics could you start adding to the outline? We'll start selecting content team leads this week.

@rviscomi how do we request access?

rviscomi commented 3 years ago

Should be fixed now! Apparently letting anyone comment means that no one can request to edit! Confusing but now "view only" is the default and anyone can request edit access.

rviscomi commented 3 years ago

@alextait1 thanks for your interest in authoring this chapter! As the content team lead, you'll be responsible for the scope and direction of the chapter and keeping it on schedule. We automatically monitor the staffing and progress of each chapter based on the state of the initial comment so please keep that updated as you add new contributors and meet each milestone.

@scottdavis99 @oluoluoxenfree, I've spoken with @alextait1 and we'd like to have you both on as coauthors. There's a lot of potential content to cover in this chapter so a team of 3 coauthors should be a nice balance.

We've created a Google Doc for this chapter, which you're encouraged to use to collaborate with the content team on the initial outline, metrics, and ultimately the final draft.

Next steps for this chapter are:

@obto will be the section coordinator for this chapter, so they'll be periodically checking in with you directly to make sure the chapter is staying on schedule. Reach out to them here in this issue if you have any questions about the process.

More information about the content team lead and author roles and responsibilities are available for reference in the wiki if needed.

To anyone else still interested in contributing to this chapter, please comment below to join the team!

alextait1 commented 3 years ago

@rviscomi thanks for the info, and looking forward to working on this. Are we responsible for sourcing the data analyst for this as the content team, or do you have a group of data folks getting involved already?

rviscomi commented 3 years ago

@HTTPArchive/analysts would anyone be interested to work on this year's Accessibility chapter? We're looking for one or two analysts to round out the team.

There are a few other chapters in urgent need of analysts too, you can browse them in the help wanted: analysts hotlist.

rviscomi commented 3 years ago

📟 paging 2019/2020 contributors: @obto @kleinab @rachellcostello @ljme @dougsillars @aardrian

Would any of you be interested to contribute to the 2021 chapter as reviewers or analysts?

rviscomi commented 3 years ago

@schachin @digitala11ies were either of you interested in contributing as a peer reviewer?

digitala11ies commented 3 years ago

Hey all! Getting a late start since I was on a much needed computer break. I am honestly up for a lot and happy to plug in where people feel I fit best.

I love writing and know a lot about accessibility (especially the edge cases like speech recognition, cognitive/mental health concerns, and high contrast modes) and would be happy as an author and/or reviewer. I'm also a diligent researcher so could potentially be an analyst (for sections I don't write if I write), and I have a long history as a developmental/structural and copy editor. I don't mind wearing multiple hats as long as the time commitment for the hat-wearing is parsed in a respectful manner.

estelle commented 3 years ago

Please add me to the reviewer list.

rviscomi commented 3 years ago

Hi @alextait1 just checking in. Here are some tips to help keep the chapter on track:

alextait1 commented 3 years ago

@rviscomi we're still in need of an analyst! Would love to work with you again @obto if you're up for it? If not we could use support finding someone (I appreciate the pings I've already seen thanks!). Aside from that we have all the folks we need in terms of authors and reviewers.

Hey authors! What's your preferred method of communication? We have the option of having a slack channel created for us, or we can keep things here/on the google doc. We've got a little over a month to get our initial outline together of what we want to cover. Would you be open to having an intro call sometime? @oluoluoxenfree and I know each other, but would be good to connect with you @scottdavis99 and have a high level chat about our plans.

Hey reviewers! Last year @ericwbailey contributed some good ideas and comments in the outline phase, so once we start jamming on the google doc please feel free to comment away with ideas and considerations. Welcome abord @clottman @shantsis @digitala11ies

Everyone: we need to add names and emails to the google doc (you might also need to request access if you haven't yet). I added what I could find here on github but some of you do not have email addresses and some of you may have alternate addresses you prefer for communication. Here's the link to the doc.

I'm pretty stoked about this project. We learned a ton last year and I'm excited to take the insights further.

ericwbailey commented 3 years ago

Happy to join the intro call if you'd find that helpful, @alextait1!

schachin commented 3 years ago

Hi sorry this got buried and I do not think I saw it. What would I be contributing too? Something Accessibility it seems.

Most likely interested in it though :)

More Info & Publications

Contact Info

Helping You Make It Better by Making It Work. Recommendations and References available on LinkedIn or by request. Client information is generally protected by NDA and not typically available on public sites. 

On Wednesday, May 5, 2021, 1:23:01 PM PDT, Rick Viscomi ***@***.***> wrote:

@schachin @digitala11ies were either of you interested in contributing as a peer reviewer?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

alextait1 commented 3 years ago

Happy to join the intro call if you'd find that helpful, @alextait1!

Happy to have you of course!

schachin commented 3 years ago

Is there a call right now? Sorry things have been so hectic, so very interested just need to get caught up. :)

More Info & Publications

Contact Info

Helping You Make It Better by Making It Work. Recommendations and References available on LinkedIn or by request. Client information is generally protected by NDA and not typically available on public sites. 

On Wednesday, May 12, 2021, 2:37:36 PM PDT, Alex Tait ***@***.***> wrote:

Happy to join the intro call if you'd find that helpful, @alextait1!

Happy to have you of course!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

alextait1 commented 3 years ago

Hi @schachin! I think @rviscomi was seeing if you'd like to be one of the content reviewers. If you'd like to join that group I'll add you. No call happening now, I'm trying to organize one for the author team (though reviewers would be welcome).

schachin commented 3 years ago

Sure :) thank you! So what are the specifics of what is being reviewed? Be happy to do so. I see the subject line, but don't know the details :)

More Info & Publications

Contact Info

Helping You Make It Better by Making It Work. Recommendations and References available on LinkedIn or by request. Client information is generally protected by NDA and not typically available on public sites. 

On Wednesday, May 12, 2021, 2:40:44 PM PDT, Alex Tait ***@***.***> wrote:

Hi @schachin! I think @rviscomi was seeing if you'd like to be one of the content reviewers. If you'd like to join that group I'll add you. No call happening now, I'm trying to organize one for the author team (though reviewers would be welcome).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

alextait1 commented 3 years ago

@schachin nothing yet! There's a google doc where the planning will be happening. Reviewers are welcome to comment and weigh in for this process and there will be content to review and comment on starting Mid-June. Checkout the milestones at the top of this page for more info :)

rviscomi commented 3 years ago

@schachin oh I think if you're only reading the email thread you don't have the full context. Visit https://github.com/HTTPArchive/almanac.httparchive.org/issues/2147#issue-868435842 to see the whole GitHub issue; the top comment explains how to contribute in more detail. And here's the post that kicks off the project. For context I got your info from the 2021 Web Almanac interest form where you indicated that you're a SME in accessibility and open to authoring or reviewing. You also mentioned SEO, but that chapter has more than enough contributors at the moment!

schachin commented 3 years ago

Oh great thank you! I appreciate you adding me. :) Will check that out.

BTW I know you have a lot for SEO but if you can't add contributors would love to be a reviewer because a lot of people purvey a lot of bad information about SEO and I speak and write on it so usually can dispute something with references.

(I have written over 120 articles, spoken over 80 times in the US and Europe, and work with site auditing and recovery a lot of the time which means I test a lot of the assumptions.)

Just let me know :)

BTW I have someone that would be great for this part of the project if you need any additional people.

More Info & Publications

Contact Info

Helping You Make It Better by Making It Work. Recommendations and References available on LinkedIn or by request. Client information is generally protected by NDA and not typically available on public sites. 

On Wednesday, May 12, 2021, 2:47:05 PM PDT, Rick Viscomi ***@***.***> wrote:

@schachin oh I think if you're only reading the email thread you don't have the full context. Visit #2147 (comment) to see the whole GitHub issue; the top comment explains how to contribute in more detail. And here's the post that kicks off the project. For context I got your info from the 2021 Web Almanac interest form where you indicated that you're a SME in accessibility and open to authoring or reviewing. You also mentioned SEO, but that chapter has more than enough contributors at the moment!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

foxdavidj commented 3 years ago

@alextait1 I'll look around for an analyst and put myself down for the time being. Stoked to work with you again this year :)

alextait1 commented 3 years ago

@obto thank you so much! Whether we get to work with you or someone you find, I'm sure we'll be in good hands and with our analyst spot at least filled for now we're good for the May 31st Milestone. Woooooo!

foxdavidj commented 3 years ago

@alextait1

As for next steps:

  1. @ericwbailey @clottman @digitala11ies Please add yourselves to the Google doc in the format: Name (email@example.com). I've also added links within the doc to the previous years Google doc in case you'd like to mine it for ideas.
  2. Would love to set up a 30 minute Zoom call in the next couple weeks to kick-start the chapter planning and brainstorming process, and put some faces to the names of the people we'll all be working with this year. I'll reach out again later this week to find a time that works.
schachin commented 3 years ago

Am I still working on this? Or am I already on that sheet :) ?

More Info & Publications

Contact Info

Helping You Make It Better by Making It Work. Recommendations and References available on LinkedIn or by request. Client information is generally protected by NDA and not typically available on public sites. 

On Sunday, May 16, 2021, 10:52:04 AM PDT, David Fox ***@***.***> wrote:

@alextait1

As for next steps:

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

alextait1 commented 3 years ago

@schachin yes please add yourself to the sheet in the format listed (you may need to request access)

schachin commented 3 years ago

Ok great thanks!

More Info & Publications

Contact Info

Helping You Make It Better by Making It Work. Recommendations and References available on LinkedIn or by request. Client information is generally protected by NDA and not typically available on public sites. 

On Monday, May 17, 2021, 10:38:06 AM PDT, Alex Tait ***@***.***> wrote:

@schachin yes please add yourself to the sheet in the format listed (you may need to request access)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

ericwbailey commented 3 years ago

Added my email to the doc. A Zoom call sounds great.

alextait1 commented 3 years ago

@scottdavis99, @ericwbailey and @obto what timezone(s) are you in? I know @oluoluoxenfree is in the UK and I'm in EST. I'd like to book our intro chat before the end of the month ideally (30 min should suffice). Other reviewers welcome too!

ericwbailey commented 3 years ago

I'm EDT, but also, uh, online a lot 😅

I'll also add my timezone to the doc, just to get it all in one place.

schachin commented 3 years ago

I am on PDT time.

More Info & Publications

Contact Info

Helping You Make It Better by Making It Work. Recommendations and References available on LinkedIn or by request. Client information is generally protected by NDA and not typically available on public sites. 

On Tuesday, May 18, 2021, 6:59:09 AM PDT, Alex Tait ***@***.***> wrote:

@scottdavis99, @ericwbailey and @obto what timezone(s) are you in? I know @oluoluoxenfree is in the UK and I'm in EST. I'd like to book our intro chat before the end of the month ideally (30 min should suffice). Other reviewers welcome too!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

bkardell commented 3 years ago

Just dropping this in here for analysts - it strikes me that in neither the CSS nor Accessibility chapters in 2019/2020 is there any analysis on focus stying (including the disabling of) which is very relevant to a lot of conversations and would be great to have more facts on

alextait1 commented 3 years ago

Just dropping this in here for analysts - it strikes me that in neither the CSS nor Accessibility chapters in 2019/2020 is there any analysis on focus stying (including the disabling of) which is very relevant to a lot of conversations and would be great to have more facts on

Yes we can maybe query for this (maybe even adding custom focus styles)