Skip to content

Commit

Permalink
Merge pull request #73 from YuriDevAT/version
Browse files Browse the repository at this point in the history
Latest release
  • Loading branch information
YuriDevAT authored Sep 2, 2024
2 parents 534ed26 + 55daed1 commit c139c48
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion _posts/ja/accessibility-the-what-why-&-how.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: 'アクセシビリティ 何を、なぜ、どのように'
title: 'アクセシビリティ何を、なぜ、どのように'
excerpt: 'ウェブ・アクセシビリティは、幸いにも最近ますます注目されるようになってきました。しかし、ウェブ・アクセシビリティが実際にどのようなもので、なぜ重要なのかを知らない人はまだ多い。このトピックを紹介することで、アクセシビリティに関する全体的な理解を深めましょう。。。'
coverImage: '/assets/blog/en/accessibility-the-what-why-&-how/cover.png'
date: '2022-10-09T05:35:07.322Z'
Expand Down
2 changes: 1 addition & 1 deletion locales/en/accessibility-statement.json
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
"a1": "Web Content Accessibility Guidelines (WCAG)",
"p4": " defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. Accessibility First is partially conformant with WCAG 2.2 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.",
"h3": "Additional accessibility considerations",
"p5": "Although our goal is WCAG 2.2 Level AA conformance, we have also applied some Level AAA Success Criteria (SC): Images of text are only used for decorative purposes (SC 1.4.9). Everything can be done with a keyboard (SC 2.1.3). Users understand what each link will do (SC 2.4.9). Content is organized in section, so users can orient themselves (SC 2.4.10). Focus is not obscured and its appearance meets SC 2.4.13. Expanded form of abbreviations are provided (SC 3.1.4). The purpose of controls and key information can be identified by the users (SC 1.3.6)",
"p5": "Although our goal is WCAG 2.2 Level AA conformance, we have also applied some Level AAA Success Criteria (SC): Images of text are only used for decorative purposes (SC 1.4.9). Everything can be done with a keyboard (SC 2.1.3). Users understand what each link will do (SC 2.4.9). Content is organized in section, so users can orient themselves (SC 2.4.10). Focus is not obscured and its appearance meets SC 2.4.13. Expanded form of abbreviations are provided (SC 3.1.4). The purpose of controls and key information can be identified by the users (SC 1.3.6).",
"h2-3": "Feedback",
"p6": "We welcome your feedback on the accessibility of Accessibility First. Please let us know if you encounter accessibility barriers on Accessibility First:",
"li7": "Report bug: ",
Expand Down
6 changes: 3 additions & 3 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
{
"name": "accessibility-first",
"version": "1.2",
"version": "1.3",
"private": true,
"homepage": "https://accessibilityfirst.at",
"description": "Accessibility First is a collection of insights, learnings, and experiences from industry professionals / leaders to spread awareness and help you eradicate invisible barriers.",
"description": "Accessibility First is a collection of insights, learnings, and experiences from industry professionals to spread awareness and help you eradicate invisible barriers.",
"repository": {
"type": "git",
"url": "git+https://github.com/YuriDevAT/accessibility-first.git"
Expand All @@ -24,7 +24,7 @@
],
"author": "Julia Undeutsch",
"bugs": {
"url": "https://github.com/YuriDevAT/website-bug-tracker"
"url": "https://github.com/YuriDevAT/accessibility-first#readme"
},
"scripts": {
"dev": "next dev",
Expand Down

0 comments on commit c139c48

Please sign in to comment.