New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Post] 2023 Web Almanac style report on Web Accessibility #1552
Comments
Howdy! I'm a big fan of the Web Almanac and we'd love to host a report of that nature.
Hope that helps. What's your timeline for this report? |
Excellent! 馃槍 We鈥檝e not discussed a specific timeline yet. For me it鈥檇 be easier to do this between June and September, @SaptakS might have other plans. |
Between June and September works for me as well. |
Yay :) I鈥檓 not super clear on the process for this proposal 鈥撀爄s there anything further I/we need to do or is this considered approved? |
馃憢 just a quick update to say Saptak and I are about to get going with this, unless there鈥檚 any last-minute reservations. Our first step will be to gather and analyse the data the report is based on, once that鈥檚 done we can get going with the writing. |
Thank you for your interest in writing a post! Please fill out the following information:
Your idea
馃憢 long time reader, first time poster! I and @SaptakS are interested in publishing a 2023 version of the Accessibility chapter from the HTTP Archive鈥檚 Web Almanac. The Almanac is a data-driven survey of how the web is built, assessing websites via the HTTP Archive鈥檚 dataset of about 8M sites. The Accessibility chapter in particular looks into the prevalence of specific good and bad patterns in HTML and CSS.
We鈥檙e looking for a publication to write this for because the Web Almanac itself won鈥檛 be running in 2023, simply for logistics reasons on their side. We鈥檝e discussed our intentions to publish an unofficial 2023 version of the chapter with the Almanac team directly, who are keen to support us (feedback on our plans, guidance on the dataset, access to the data, funding for data analysis costs). All we鈥檙e missing is a place to publish the report.
From my perspective, the A11Y Project feels like a great fit for this kind of reporting: well-established and authoritative in the web accessibility space.
Outline (optional)
The tentative outline would be as per the 2022 accessibility chapter. Most likely, as we start drafts there will be a few iterative changes.
Additional information (optional)
It鈥檚 worth noting both Saptak and I were heavily involved with the creation of the 2022 report, so have ample experience with the data as well as the writing style. And a clear understanding of the scale of the project.
Having read the contributing guidelines, I have a few concerns:
Terms
The text was updated successfully, but these errors were encountered: