Communities

(DEV) Codidact Meta
(DEV) Codidact Meta
(DEV) Writing
(DEV) Writing
Proposals
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 »
Blog

Codidact Accessibility Statement

+0
−0

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.

An in-depth guide to creating more accessibile posts is available to all users in the Help Center of each community.

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 2024-02-29.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads