a11y: drop support for ask.ci and migrate any relevant content here
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24
- Forks
- 15
- Avg merge
- 10d 3h
- Merged PRs (30d)
- 1
Description
What would you like to see added?
Due to accessibility requirements, I want us to drop support for ask.ci. We rarely use it, the answers there are mostly outdated, and I can't get any information about their accessibility statement or VPATs. I suspect the website has very little administrative or financial support.
If we can get that information at a future date because there is a specific need, then we can address the site again at that time.
Action Items
- Examine all ask.ci QA at our page to decide if it is obsolete or current
- Migrate and integrate current QA back to our docs
- Remove references to ask.ci from our docs
- Remove ask.ci from the FAQ GitHub issue label
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying the ask.ci QA and references in the project documentation, then determine which QA is obsolete or current. Migrate current QA into the docs and remove the external references and ask.ci from the FAQ GitHub issue label. Done means all listed action items are completed and the documentation no longer depends on ask.ci.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100