... fic input devices and assistive technologies. アクセシビリティ基準 ¶ We work to conform with the Web Content Accessibility Guidelines (WCAG), version 2.2, at the AA level. WCAG is the most established standard for web accessibility. AA-level guidelines are ... the most common legal compliance target worldwide. We also aim to follow other best practices, such as: WCAG 2.2 AAA-level guidelines – stricter criteria that go beyond the AA level. The upcoming WCAG 3.0 guidelines – a new, evolving standard that aims to ... unify and improve upon previous versions of WCAG. Authoring Tool Accessibility Guidelines (ATAG) 2.0 – guidelines for software and services that are used to produce web content. To learn more about accessibility ... ... fic input devices and assistive technologies. アクセシビリティ基準 ¶ We work to conform with the Web Content Accessibility Guidelines (WCAG), version 2.2, at the AA level. WCAG is the most established standard for web accessibility. AA-level guidelines are ... the most common legal compliance target worldwide. We also aim to follow other best practices, such as: WCAG 2.2 AAA-level guidelines – stricter criteria that go beyond the AA level. The upcoming WCAG 3.0 guidelines – a new, evolving standard that aims to ... unify and improve upon previous versions of WCAG. Authoring Tool Accessibility Guidelines (ATAG) 2.0 – guidelines for software and services that are used to produce web content. To learn more about accessibility ... ... . If you can't send a pull request for some reason, you can also use patches in Trac. When using this style, follow these guidelines. Submit patches in the format returned by the git diff command. Attach patches to a ticket in the ticket tracker , using t ... o not exist. Placeholder or fictitious content will result in rejection. Respect all contribution requirements. Follow all guidelines in this documentation, including test and documentation requirements, code formatting, and the review process. Follow the ... butions require a ticket unless the change is considered trivial . All code changes ¶ Does the coding style conform to our guidelines? Are there any black , blacken-docs , flake8 , isort , or zizmor errors? You can install the pre-commit hooks to automatic ... ... . If you can't send a pull request for some reason, you can also use patches in Trac. When using this style, follow these guidelines. Submit patches in the format returned by the git diff command. Attach patches to a ticket in the ticket tracker , using t ... o not exist. Placeholder or fictitious content will result in rejection. Respect all contribution requirements. Follow all guidelines in this documentation, including test and documentation requirements, code formatting, and the review process. Follow the ... butions require a ticket unless the change is considered trivial . All code changes ¶ Does the coding style conform to our guidelines? Are there any black , blacken-docs , flake8 , isort , or zizmor errors? You can install the pre-commit hooks to automatic ... ... large volumes of reports submitted in a short period of time, and reports submitted in bulk may be put on hold. Reporting guidelines ¶ Include a working proof of concept ¶ Please privately share a minimal Django project or code snippet that demonstrates t ... the exploit, etc). Verify that the issue describes a real, reproducible vulnerability that otherwise meets these reporting guidelines. Avoid fabricated code, placeholder text, or references to non-existent Django features. Reports that appear to be unverif ... ent, fictitious APIs, or made-up citations will result in automatic rejection. Respect all policy requirements. Follow all guidelines in this document, including limits on request sizes, realistic application patterns, proper user input validation and esca ... ... ket_xxxxx branch. Make some changes and commit them: git commit When writing the commit message, follow the commit message guidelines to ease the work of the merger. If you're uncomfortable with English, try at least to describe precisely what the commit d ... med messages for each commit: a summary line and then paragraphs wrapped at 72 characters thereafter -- see the committing guidelines for more details, documentation and tests, if needed -- actually tests are always needed, except for documentation changes ... nything else you need to do to investigate the quality of the patch. For more detail on working with pull requests see the guidelines for mergers . 概要 ¶ Work on GitHub if you can. Announce your work on the Trac ticket by linking to your GitHub branch. Wh ... ... large volumes of reports submitted in a short period of time, and reports submitted in bulk may be put on hold. Reporting guidelines ¶ Include a working proof of concept ¶ Please privately share a minimal Django project or code snippet that demonstrates t ... the exploit, etc). Verify that the issue describes a real, reproducible vulnerability that otherwise meets these reporting guidelines. Avoid fabricated code, placeholder text, or references to non-existent Django features. Reports that appear to be unverif ... ent, fictitious APIs, or made-up citations will result in automatic rejection. Respect all policy requirements. Follow all guidelines in this document, including limits on request sizes, realistic application patterns, proper user input validation and esca ... ... ket_xxxxx branch. Make some changes and commit them: git commit When writing the commit message, follow the commit message guidelines to ease the work of the merger. If you're uncomfortable with English, try at least to describe precisely what the commit d ... med messages for each commit: a summary line and then paragraphs wrapped at 72 characters thereafter -- see the committing guidelines for more details, documentation and tests, if needed -- actually tests are always needed, except for documentation changes ... nything else you need to do to investigate the quality of the patch. For more detail on working with pull requests see the guidelines for mergers . 概要 ¶ Work on GitHub if you can. Announce your work on the Trac ticket by linking to your GitHub branch. Wh ... ... は、コミュニティを巻き込むこと、仕事を終わらせること、そして使えるコミット履歴を持つことです。 コミットガイドライン ¶ These guidelines apply to all commits to Django's Git repository, whether submitted by a contributor via a pull request or landed directly ... ed-By as appropriate, including anyone whose earlier work the change builds on. 例えば: Fixed #18307 -- Added git workflow guidelines. Refactored the Django's documentation to remove mentions of SVN specific tasks. Added guidelines of how to use Git, GitHu ... ... は、コミュニティを巻き込むこと、仕事を終わらせること、そして使えるコミット履歴を持つことです。 コミットガイドライン ¶ These guidelines apply to all commits to Django's Git repository, whether submitted by a contributor via a pull request or landed directly ... ed-By as appropriate, including anyone whose earlier work the change builds on. 例えば: Fixed #18307 -- Added git workflow guidelines. Refactored the Django's documentation to remove mentions of SVN specific tasks. Added guidelines of how to use Git, GitHu ... 2026年10月08日