w3c / wai-news Goto Github PK

👋 The redesign is coming to this repository soon. (Hooray! 🎉) We need to check off several steps before we can link your content to the redesign repository. I marked some of the steps with RM meaning Resource Manager. Others are marked with @yatil, and I’ll do/help you through the technical parts.

In addition to this issue, you might find other issues in your repository that are labeled with wai-redesign-before that should be addressed/resolved before the redesign. That might mean to postpone working on it until after the redesign (use the label wai-redesign-after for those issues).

• Content is updated and ready to be put into the new design. (RM)
  • The best case scenario would be that the content is ready before doing step three below. However, that might not be feasible in every case, so @yatil might do the next step before the content is ready and just port the content that is available to him.
  • Once done, add label wai-redesign-content-done.
• Tech Create branch/repository with the new structure (@yatil)
  • For simple resources (separate pages/pages that don’t need a left navigation), you will find the documents in the root directory of the repository.
  • For more complicated resources, @yatil creates a Jekyll collection which adds the left sidebar navigation amongst other things. You will then find your files in a folder called _resource_name.
  • Documentation should be available in the w3c/wai-website wiki soon.
  • Once done, add label wai-redesign-repo-done.
• Content Use current content and port it to the new design (@yatil)
  • Once this is done, all previews will be in the new design.
  • Once done, add label wai-redesign-content-ported.
• Content Check if content renders well, make changes as needed/wanted. (documentation) (RM)
  • Once done, add label wai-redesign-content-checked.
• Tech Link this repository to the w3c/wai-website repository (@yatil)
  • Once done, add label wai-redesign-repo-linked.
• When all checkpoints above are checked, close this issue.

Hi! Please publish the following news item:

---
title: "For Wide Review: Personalization Semantics Content Module 1.0"
date: 2020-01-30
---
<p>The <a href="https://www.w3.org/TR/personalization-semantics-content-1.0/">Personalization Semantics Content Module 1.0</a> specification is available for wide review. For a short introduction to personalization and the related documents, see the <a href="https://www.w3.org/WAI/personalization/">Personalization Overview</a>. The Working Group particularly requests review of section <a href="https://www.w3.org/TR/personalization-semantics-content-1.0/#action-explanation">3.1 action</a>. Please send any comments by 10 March 2020.</p>

Note: If you are sending this in, the Website team will make sure to publish the news article on or after the date specified in the Markdown file above. Please comment below in case of delays!

https://card-apply.apple.com/web/application/domain/ccs/assets/pdf_static-a268d65e-829f-4e11-8a2e-f99a255dba76?fileName=ElectronicCommsAgreement

Under "Updated Resources: Planning and Managing Web Accessibility"

(2016-Dec-15)

(2017-12-15)

breadcrumb is wrong on https://www.w3.org/WAI/news/all/

e.g., https://www.w3.org/WAI/news/2018-01-31/wcag21-cr/

2021-Internet-Society-Impact-Report-EN-1.pdf

catch up on missing https://lists.w3.org/Archives/Public/public-wai-announce/2021JulSep/

Hi! Please publish the following news item:

---
title: "This is the new shiny headline"
date: YYYY-MM-DD
---
Write your news item in **Markdown** or HTML.

Note: If you are sending this in, the Website team will make sure to publish the news article on or after the date specified in the Markdown file above. Please comment below in case of delays!

Consider exploring "trigger warnings" as mitigation to trauma related disabilities. Media and other websites may display post-event footage, for example, the aftermath of a school shooting, which may induce symptoms in users with trauma related disabilities. Trigger warnings are also useful as parental controls in preventing children from watching this type of content.

URL:
https://www.w3.org/TR/coga-gap-analysis/#introduction

Section:
Introduction

Issue:
Bullet #6 is duplicated content from bullet #5
"Attitudes and misinformation can also ..."

<a href="https://www.w3.org/personalization-semantics-1.0/">Personalization Semantics 1.0</a>

is 404

<a href="https://www.w3.org/WAI/GL/">Accessible Rich Internet Applications Working Group</a>

is to AGWG not ARIA WG

To avoid ambiguity, I think we need to display it as:

0000-MMM-00

e.g.:

2018-Feb-14

(We were using that for the home page listing, but needed 0000-00-00 for RSS.)