Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Please review a new Accessibility Statement and Accessibility Policy

Parent

Please review a new Accessibility Statement and Accessibility Policy

+9
−0

Here at Codidact, we believe that everyone deserves to have access to information and to be a part of a community. "Everyone" includes people with disabilities, and so that means making our site and posts as accessible as possible.

To make that clear to everyone, I've put together the following document. This document details both Codidact's Accessibility Statement - which makes our commitment clear, and gives some relevant information (such as what to do when encountering an accessibility issue) - and an Accessibility Policy, which explains on a technical level what standards we should be meeting and what the expectations are for code changes to Codidact-controlled spaces.

The current plan is to host this document at /policy/accessibility, and to add an "Accessibility" link to this page in both the footer and the "About the Network" section in the Help Center.

Please take a few minutes to review it before it goes live, and leave feedback as an answer below. I'm also happy to answer any questions or concerns that people might have.

The document begins after the horizontal line.


Codidact Accessibility Statement

Sharing information and being part of a community are the two fundamental goals of the Codidact Project. Everyone deserves access to information and to be a part of a community, and with that in mind, the Codidact Foundation is committed to accessibility in all areas of the Codidact Project.

Who is responsible for accessibility?

Accessibility is the responsibility of everyone, from the people writing posts to the people working on the website. However, the chief person responsible for accessibility in the Codidact Foundation is Mithical, Co-Lead for User Documentation and a member of the Board of Directors. Questions about Codidact's accessibility can be directed to support@codidact.org.

I'm encountering an accessibility problem, what do I do?

Please report any accessibility problems you have on Codidact Meta, using the [bug] and [accessibility] tags. That makes sure that we're aware of the problem, and we'll do our best to fix it as soon as reasonably possible with our available resources.

Technical details: Codidact Accessibility Policy

This Accessibility Policy outlines the technical details of our commitment to accessibility and sets expectations for what is in scope of that commitment.

The Codidact Network

The platform that the Codidact Network runs on, known as QPixel, should meet both the Web Content Accessibility Guidelines (WCAG) 2.2 and the Authoring Tool Accessibility Guidelines (ATAG) 2.0 standards at the AA conformance level.

Since the platform is open-source and volunteer operated, setting strict timetables isn't realistic. However, new changes to the platform should be made with these standards in mind, including using Accessible Rich Internet Applications (WAI-ARIA) features.

User-contributed content

The Codidact Foundation encourages all people contributing posts, such as questions, answers, and articles, to make their posts accessible. This is done via system reminders, such as a warning when posting images without alt text, and via other users editing those posts to be more accessible.

By the end of February 2024, an in-depth guide to creating accessible posts will be published in the Help Center.

The "codidact.org" and "codidact.com" sites

The codidact.com and codidact.org static domains should meet WCAG 2.2. When those pages are updated, steps should ideally be taken to increase the accessibility of those pages. At a minimum, changes must not cause the accessibility of those pages to decrease. However, a full redesign is not in scope at the moment.

This document was last updated on [date].

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+9
−0

status-completed


Just a minor concern: I don't think a single person should be the point of contact, maybe set up something like access@codidact.org. That is, if it even needs a dedicated mail address - I don't quite see why support@codidact.org address won't do?

If all accessibility concerns are routed to Mithical internally, that's all well and good. But I believe we should direct support requests to roles/titles rather than relying on a certain individual. Open source projects tend to suffer from people coming and going and on top of that, everyone's a volunteer. So someone else in the Codidact organization might have to step in during vacation/hiatus.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

Accessible email address (3 comments)
Accessible email address
trichoplax‭ wrote 6 months ago

I also see no problem with using support@codidact.org as the accessibility contact, but if a dedicated email address is required, I would much prefer accessibility@codidact.org rather than access@codidact.org - removing the ambiguity seems worth the extra 7 characters.

Lundin‭ wrote 6 months ago · edited 6 months ago

trichoplax‭ I was going to suggest accessibility too, but the word accessibility isn't exactly the easiest one to spell, with dyslexia in mind. Would be kind of ironic if the e-mail address to complain about accessibility is needlessly hard to access... But maybe I'm overthinking things.

trichoplax‭ wrote 6 months ago

Oh I hadn't thought of it that way. Interesting. Maybe support is safest...