Project: ✅ Wagtail.org website accessibility

[thibaudcolas]

Please use this Discussions thread to ask anything and everything relating to our Wagtail.org website accessibility project idea.

Don’t hesitate to answer other people’s questions and mark this as a contribution on the Outreachy website if you’re particularly happy with your answer.

[thibaudcolas]

Q: I saw a project called "Wagtail.org accessibility" on Outreachy. What’s the difference? Are they the same?

[thibaudcolas]

I’m glad you asked @thibaudcolas! Yes, this is the one and only "wagtail.org" project. I just changed the name to hopefully clarify it’s about a specific website.

[MugoBrian]

Hello @thibaudcolas . While trying to install wagtail.org locally , I am getting the following error while running the command make setup, I tried with and without sudo.
Screenshot of the error.

Kindly assist me.

[MugoBrian]

Whoa! I am proud of you @praiztech .I am still facing challenges. This time round is a new error. Installation of Poetry is failing

[praiztech]

Thanks @MugoBrian.

I don't really know how linux works but is it possible to maybe uninstall and reinstall the OS? I had to do a clean install of Windows 10 64-bit before I could install Docker.

[MugoBrian]

Doing a clean install is not feasible for me. I'll do more research on my errors.For now I'll stick to Gitpod setup.

[MugoBrian]

@praiztech and @thibaudcolas I have successfully managed to setup the codebase locally using Docker. Thank you.

[praiztech]

Finally!

[khushishikhu]

I tried to setup wagtail and did all the steps but it seems to show me this page on localhost. Please help me with this issue

[thibaudcolas]

@khushishikhu this looks alright to me, though the docs could be clearer! I’m glad you reached this step :) You essentially have an empty site here. From there, you need to log into the CMS and create test content. Most likely replace this placeholder page with a real homepage, and then expand from there.

[khushishikhu]

@thibaudcolas could you please guide me a bit about how to log into CMS and move ahead. I can't find any link which has this step clearly mentioned

[MugoBrian]

Perhaps you could follow this tutorial on
Your first wagtail site

[thibaudcolas]

@khushishikhu I would expect this is the kind of thing you can figure out on your own. If you don’t have Django experience, I’d recommend going through their tutorial or our Your first Wagtail site as mentioned by @MugoBrian before trying to contribute to this project.

[khushishikhu]

@thibaudcolas I tried logging into the CMS but ended up with this error, the moment I clicked login. Can you please help me to resolve it

[thibaudcolas]

@Chidera6 the instructions you share are about getting Wagtail itself set up for local development. If @khushishikhu is asking here I believe it’s wagtail.org she wants help setting up?

[thibaudcolas]

@khushishikhu from what you shared it looks like you didn’t run the make setup step? Please make sure to follow the instructions carefully, that’s meant to be the first step in the setup, not make start.

[Chidera6]

@thibaudcolas Yes that's what she is asking for. I realized I mixed it up during the video call I had with her.

[khushishikhu]

@thibaudcolas I did run make setup and after that I run make start the. I created the superuser but it still gave me this error

[MugoBrian]

@khushishikhu ,did you try to do a fresh install of the wagtail.org. Sometimes that's what I do if no solution is working. I would delete the repository and start over again , it helps sometimes.

Have you tried setting it up using Gitpod?

[thibaudcolas]

@nouman17610 please keep this for questions about the project. I’ve answered on the Helpdesk thread.

[thibaudcolas]

Q by @Amarajah on Slack:

I'm working on contributing to the Wagtail.org website accessibility project, one of the contribution requirements is:

Find an accessibility issue on the live wagtail.org website, and report it on the project’s issue tracker, with appropriate details (title, description, screenshot if applicable, why you think this is an accessibility issue).

I went through the site and was unable to find anything I could report, but on the Wagtail GitHub repo I found some issues regarding the live site which were still open.

Am I allowed to work on one of those issues? Or is it mandatory I find my own errors?
If we're allowed to work on those already reported issues, how many should we contribute to? Is one enough?

[thibaudcolas]

Yes, you are allowed to work on those pre-existing issues. It’s not mandatory to find your own errors.

As part of working on those pre-existing issues, I’d still recommend taking a moment to check whether you can actually spot the issue – confirming whether the report is clear enough, and whether it’s still up-to-date (if the issue is old). Taking the time to comment on the issue with a summary of your findings is a great contribution. Something along the lines of "I’m going to work on this. I can confirm this is still an issue – I’ve tested this on <page you tested it on, with link>, with the following steps / tool." Perhaps a screenshot if you think it helps.

---

If we're allowed to work on those already reported issues, how many should we contribute to? Is one enough?

Yes, one is enough. I’d say zero can also be enough. We have those tasks on our checklist for three reasons, but there are other ways to make it work:

1. So you can check whether the project is a good fit for you. The actual internship will be full of tasks like this – going through it one time is a good sense-check that this will be interesting for you, and that you have the right skillset.
2. So mentors can check whether you’re a good fit for the project. You can prove yourself in other ways but doing something that’s similar to what the project involves is definitely a great approach.
3. Because those are useful contributions! That one is a bit obvious but I guess worth saying – those issues are really important for us to identify and fix.

One is plenty enough if it fits the bill on those three criteria. So if you did only one, strategically I’d recommend picking an issue that gives you plenty of opportunity to test/demonstrate your abilities. From my perspective as a mentor, I’d much rather review one thing you’ve put serious thought into, than 2/3/4/5 that were all very basic. Quality over quantity.

[praiztech]

Thank you

[nishantn31]

Thank you @thibaudcolas for discussing it in detail. I had recently successfully raised a PR for the issue after checking it's existence in live site and now studying project further for accessibility improvements. Also updating my checklist with every task I'm completing.

[thibaudcolas]

Nice one @nishantn31, I’ll try to review it soon.

[nishantn31]

Thank you! @thibaudcolas

[MugoBrian]

Hello @thibaudcolas. I believe you are doing good. I have two questions, in particular, I would love help with.

1. How do I live preview pages such as /roadmap or /packages, in the wagtail.org code base? I would like to see the changes I made affecting those pages.
2. How do I solve these errors?
   
   

I am using Gitpod to run the wagtail.org codebase.

[MugoBrian]

Thank you @oly-baby .So what would be the path to that page?

[oly-baby]

You have to check Django package repo

[thibaudcolas]

@MugoBrian could you open an issue about this? I don’t think you have any need to use this view for the time being though.

[MugoBrian]

Ok. I will open an issue, on it.
@thibaudcolas How about if I want to live preview the changes I make on particular page , let's say for example the about page in the /about-wagtail route?

[thibaudcolas]

@MugoBrian create that page in the CMS and view it in the browser?