Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introductionの日本語化 #147

Open
wants to merge 4 commits into
base: waic-main
Choose a base branch
from
Open

Introductionの日本語化 #147

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f0c1dcc
Aboutの公開中最新を反映する
tsmd Feb 25, 2024
323c2e4
Introductionの粗訳
tsmd Feb 25, 2024
07e9a79
about.html の翻訳見直し
DaichiImai May 9, 2024
6cd1a55
次の微調整を行いました。「和文と欧文の間のスペース」「日本語としての自然さ」
DaichiImai May 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 20 additions & 20 deletions content/about/about.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
<!DOCTYPE html>
<html lang="en">
<html lang="ja">
<head>
<meta charset="UTF-8">
<meta content="width=device-width, initial-scale=1.0" name="viewport">
Expand All @@ -15,48 +15,48 @@
<body>
<main>
<h1>About</h1>
<!-- 翻訳元リビジョン: https://github.com/w3c/aria-practices/tree/7f54d9620e32231021aad607b7af7eeee5c24f54 -->
<ul>
<li lang="ja">
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

htmlにlang="ja"指定済みなので、ここには不要ですね

Suggested change
<li lang="ja">
<li>

<h2><a href="introduction/introduction.html">はじめに</a></h2>
<p>
APG の目的、前提知識、およびその構成について学ぶには、 <a href="introduction/introduction.html">はじめに</a> をお読みください。
</p>
</li>
<li>
<h2><a href="introduction/introduction.html">Introduction</a></h2>
<h2><a href="aria-basics/aria-basics.html">ARIA の基本</a></h2>
<p>
To learn about the purpose of the APG, the prerequisite knowledge it assumes, and how it is organized, read the
<a href="introduction/introduction.html">Introduction</a>.
このセクションでは <a href="aria-basics/aria-basics.html">ARIA の基本</a> について説明します。ARIA が何であるか、アクセシビリティのセマンティクスが何であるか、そしてそれらの目的と限界をしっかりと理解することは、APG（Accessible Rich Internet Applications Practices Guide）のガイダンスを適用する際の成功を容易にします。
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ここずいぶん原文と乖離している感がありますね…？
ChatGPTが暴走しちゃってたんでしょうかｗ

Suggested change
このセクションでは <a href="aria-basics/aria-basics.html">ARIA の基本</a> について説明します。ARIA が何であるか、アクセシビリティのセマンティクスが何であるか、そしてそれらの目的と限界をしっかりと理解することは、APG（Accessible Rich Internet Applications Practices Guide）のガイダンスを適用する際の成功を容易にします。
<a href="aria-basics/aria-basics.html">ARIAの基本</a>のこのセクションを読むことで、ARIAとは何か、アクセシビリティのセマンティクスとは何か、その目的と限界を理解し、APGガイダンスを適用する際の成功を促進しましょう。

というかんじでしょうか…

</p>
</li>
<li>
<h2><a href="aria-basics/aria-basics.html">ARIA Basics</a></h2>
<h2><a href="contributing/contributing.html">APG への貢献</a></h2>
<p>
Facilitate success when applying APG guidance by developing a solid understanding of what ARIA is, what accessibility semantics are, and their purpose and limitations with this section about
<a href="aria-basics/aria-basics.html">ARIA Basics</a>.
APG タスクフォースは、APG の有用性と品質を継続的に向上させるために、広範囲なコミュニティの代表と参加に依存しています。 <a href="contributing/contributing.html">アクセシブルな体験の開発を促進する方法として、あなたがどのように貢献できるかを学びましょう</a> 。
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

representationは「意見」とするのが自然かなと思います。また「依存している」より「頼りにしている」くらいの方が堅くなくて良いかなと。
また後半は、learnするのはcontributeする方法で、それによってpromoteをhelpするという構文なのかなと思いました。

Suggested change
APG タスクフォースは、APG の有用性と品質を継続的に向上させるために、広範囲なコミュニティの代表と参加に依存しています。 <a href="contributing/contributing.html">アクセシブルな体験の開発を促進する方法として、あなたがどのように貢献できるかを学びましょう</a> 。
APG タスクフォースは、APG の有用性と品質を継続的に向上させるために、幅広いコミュニティからの意見と参加を頼りにしています。<a href="contributing/contributing.html">あなたがどのように貢献できるかを知り、アクセシブルな体験の開発を促進するためにご協力ください</a> 。

ご意見いただきたく！

</p>
</li>
<li>
<h2><a href="acknowledgements/acknowledgements.html">Acknowledgements</a></h2>
<h2><a href="acknowledgements/acknowledgements.html">謝辞</a></h2>
<p>
To learn about the people and organizations who contribute to the development of the APG, read the <a href="acknowledgements/acknowledgements.html">Acknowledgements</a>.
APG の開発に貢献している人々や組織について知るには、<a href="acknowledgements/acknowledgements.html">謝辞</a> を読んでください。
</p>
</li>
<li>
<h2><a href="change-history/change-history.html">Change History</a></h2>
<h2><a href="change-history/change-history.html">変更履歴</a></h2>
<p>
A history of how the APG has changed, dating back to 2014, including easy access to the detailed commit log is available in the
<a href="change-history/change-history.html">Change History</a>.
2014 年からの APG の変更履歴、および詳細なコミットログへの簡単なアクセスは「 <a href="change-history/change-history.html">変更履歴</a> 」でご覧いただけます。
</p>
</li>
<li>
<h2><a href="related-specifications/related-specifications.html">Related Specifications</a></h2>
<h2><a href="related-specifications/related-specifications.html">関連する仕様</a></h2>
<p>
The APG synthesizes guidance based on information from several specifications.
While the guidance contains contextual links to relevant specifications, it can be handy to have a consolidated list of all the
<a href="related-specifications/related-specifications.html">Related Specifications</a>.
APG は、いくつかの仕様からの情報に基づいてガイダンスを統合しています。ガイダンスには関連する仕様への文脈に応じたリンクが含まれていますが、すべての <a href="related-specifications/related-specifications.html">関連する仕様</a> をまとめた一覧を持っていると便利です。
</p>
</li>
<li>
<h2><a href="coverage-and-quality/coverage-and-quality-report.html">Coverage and Quality Report</a></h2>
<h2><a href="coverage-and-quality/coverage-and-quality-report.html">カバレッジと品質レポート</a></h2>
<p>
Objectives of the APG Task Force include providing guidance or examples for all ARIA attributes and doing so with code that implements practices documented in the APG code guide.
As the APG is revised, the build process updates our view of Progress toward these objectives in the
<a href="coverage-and-quality/coverage-and-quality-report.html">Coverage and Quality Report</a>.
APG タスクフォースの目標には、すべての ARIA 属性に対するガイダンスや例を提供し、APG のコードガイドに記載されている実践を実装するコードでこれを行うことが含まれます。APG が改訂されるにつれて、ビルドプロセスはこれらの目標に対する進捗状況を <a href="coverage-and-quality/coverage-and-quality-report.html">カバレッジと品質レポート</a> で更新していきます。
</p>
</li>
</ul>
Expand Down
132 changes: 132 additions & 0 deletions content/about/contributing/contributing.html
View file
Open in desktop
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

このページわたし粗訳をし忘れてましたね…別のプルリクに分けることにしましょう。
忘れないようにissueを立てました: #149

Original file line number Diff line number Diff line change
@@ -0,0 +1,132 @@
<!DOCTYPE html>
<html lang="en">

<head>
<meta charset="UTF-8">
<meta content="width=device-width, initial-scale=1.0" name="viewport">
<title>Contributing to the APG</title>

<!-- Core JS and CSS shared by all About content -->
<link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2016/base.css">
<link rel="stylesheet" href="../../shared/css/core.css">
<script src="../../shared/js/highlight.pack.js"></script>
<script src="../../shared/js/app.js"></script>
<script src="../../shared/js/skipto.js"></script>
</head>

<body>
<main>
<h1>Contributing to the APG</h1>

<section id="introduction">
<h2>Introduction </h2>
<p>
Continuous improvement to the utility and quality of the ARIA Authoring Practices Guide (APG) depends on broad community input and participation.
Anyone may contribute feedback, suggestions, or code via the channels described below.
However, if you would like to contribute regularly, please consider
<a href="#joining-the-authoring-practices-task-force">joining the Authoring Practices Task Force</a>.
As a task force participant, you and your organization have greater influence over APG development, and are listed as contributors where appropriate.
</p>
</section>

<section id="providing-feedback">
<h2>Providing feedback</h2>
<p>
The APG provides two public feedback channels -- GitHub and email.
Links to both are provided at the bottom of every page in the APG.
</p>
<p>
GitHub issues are the best way to ask a question, make a suggestion, or report a problem.
Before creating a new issue, it is helpful if you first review existing issues to determine whether there is an issue addressing the same concern.
If so, please comment on that issue rather than raising another.
If the concern you would like addressed is related to an example implementation of an APG pattern, at the bottom of the page, next to the revision date, there is a link named "Related Issues".
That link opens a GitHub project containing all issues associated with the relevant pattern and its examples.
</p>
<p>
<a href="https://github.com/w3c/aria-practices/issues">View and create APG issues on GitHub.</a>
</p>
<p>
The task force also uses the aria-practices public mailing list for email discussion.
Meeting announcements, agendas, and links to minutes are sent to the mailing list.
While GitHub issues are the preferred place to discuss APG content, the mailing list is available to anyone who would prefer to communicate by
<a href="mailto:[email protected]">sending email to the ARIA Authoring Practices public mailing list</a>.
</p>
<p>
<a href="https://lists.w3.org/Archives/Public/public-aria-practices/">View the aria-practices mailing list archive</a>.
</p>
</section>

<section id="Making-improvements-to-documentation-or-code">
<h2>Making improvements to documentation or code</h2>
<p>
If you would like to help improve the APG with enhancements or fixes to documentation or code, please adhere to the following procedure.
</p>
<ol>
<li>Get your development environment ready:
<ul>
<li>
Install and configure linters as described in the
<a href="https://github.com/w3c/aria-practices#code-conformance">code conformance section of the repository readme</a>.
</li>
<li>
Read our wiki page about
<a href="https://github.com/w3c/aria-practices/wiki/Submitting-Pull-Requests">preparing and submitting pull requests</a>.
</li>
</ul>
</li>
<li>Comment in an existing issue or raise a new issue, expressing your willingness to help and briefly summarizing the nature of your proposed resolution.</li>
<li>An editor will confirm there are no conflicting plans and, if needed, provide guidance.</li>
<li>Do some fabulous work and submit a pull request.</li>
<li>Watch your GitHub notifications and respond to feedback during the pull request review process.</li>
</ol>
<p>
If you run into any difficulties, please feel free to ask questions either via a GitHub issue or by
<a href="mailto:[email protected]">sending email to the ARIA Authoring Practices public mailing list</a>.
</p>
</section>

<section id="joining-the-authoring-practices-task-force">
<h2>Joining The Authoring Practices Task Force</h2>
<p>
The APG is developed by the
<a target="_blank" href="https://www.w3.org/WAI/ARIA/task-forces/practices/">ARIA Authoring Practices Task Force</a>,
which is a sub-group of the
<a target="_blank" href="https://www.w3.org/WAI/ARIA/">ARIA Working Group</a>.
The task force meets weekly to coordinate work on development of the APG.
Task force participants are expected to regularly attend meetings and to actively contribute.
Examples of contributions include:
</p>
<ul>
<li>Testing the functionality and accessibility of example implementations of the APG patterns</li>
<li>Fixing bugs and implementing enhancements in example implementations of the APG patterns</li>
<li>Helping write responses to community feedback</li>
<li>Reviewing and editing documentation</li>
<li>Designing or engineering pattern implementation examples</li>
<li>Creating and editing patterns and practices for ARIA usage</li>
</ul>
<p>
To participate in the Authoring Practices Task Force, you first need to
<a href="https://www.w3.org/WAI/ARIA/participation">become a participant in the ARIA Working Group</a>.
If you are already a participant in the ARIA Working Group, contact
<a href="https://www.w3.org/staff/#dmontalvo">Daniel Montalvo</a>
and request membership in the Authoring Practices Task Force.
</p>
</section>

<section id="Helping-provide-assistive-technology-support-data">
<h2>Helping provide assistive technology support data</h2>
<p>
The assistive technology support tables included on APG example pages, e.g.,
<a href="../../patterns/radio/examples/radio-activedescendant.html#at-support">Assistive Technology Support for Radio Group Example Using aria-activedescendant</a>,
are provided by the
<a href="https://www.w3.org/groups/cg/aria-at/">ARIA and Assistive Technologies (ARIA-AT) Community Group</a>.
The ARIA-AT community group aims to ensure APG patterns have consistent and interoperable accessibility support.
If you would like to contribute to this aspect of the APG, you can learn more about the ARIA-AT project and how to contribute at
<a href="https://aria-at.w3.org/">ARIA and Assistive Technologies Home</a>.
</p>
</section>

</main>
</body>

</html>
Loading