From Norah #5 (comment)

would suggest changing
"The Web is fundamentally designed to work for all people, whatever their hardware, software, language, culture, location, or physical or mental ability...."
to
"The Web is fundamentally an open platform designed to be used by all people, whatever their hardware, software, language, culture, location, or physical or mental ability..."

I think the content of the page is spot on. Its a wonderful introduction to accessibility. However, the few bold sentences (or partially bold sentences) under the intro and Why is throwing me off. Is it just because you're trying to make the case most for the Why of accessibility. And if so, then I think that "Accessibility also benefits people without disabilities" needs to be bolded too.

Nothing else is bolded/strong in the What or How which makes it seem like those things aren't as important as the Why.

[UPDATE: this comment moved to https://github.com//issues/6]

would suggest changing
"The Web is fundamentally designed to work for all people, whatever their hardware, software, language, culture, location, or physical or mental ability...."

to
"The Web is fundamentally an open platform designed to be used by all people, whatever their hardware, software, language, culture, location, or physical or mental ability..."

What do we want in the Use It section?

Please see similar sections in W3C site sibling pages, e.g.,:

• Internationalization has:
  ** Tutorials
  ** Tools
  ** Quick Tips
  ** More Resources
• HTML & CSS
• Mobile Web

I love this sentence: "Accessibility is essential for developers and organizations that want to create high-quality websites and web tools, and not exclude people from using their products and services." but I think it's lost where it is. Can we move it up to the 2nd paragraph?

"The impact of disability is radically changed on the Web because the Web removes barriers to communication and interaction that many people face in the physical world. Accessibility is essential for developers and organizations that want to create high-quality websites and web tools, and not exclude people from using their products and services. However, when websites, web technologies, or web tools are badly designed, they can unknowingly create barriers that exclude people from using the Web."

Please read through the existing/old WAI Introduction to Web Accessibility carefully.

Update:

• What important points, phrases, ideas, etc. do we want to make sure to keep when update and revised this page?
• What things can be cut or tersified?

The W3C page was created for the W3C-specific audience that is largely developer and standards orientated -- and following a template for sibling pages (linked under "WEB DESIGN AND APPLICATIONS").

Do we want essentially the same content for the WAI page? (probably minus some of the template info, e.g., "Current Status of Specifications" section)

Or do we want a different focus or emphasis for the WAI page?

(Obviously it would be simpler to have same content.)

If different, how would we define the different Requirements?

Current draft does not have a separate section on Evaluation / Testing. It does have:

• How section includes link to Easy Checks
• Learn More section has linked "testing/evaluation"

We could include it in the Use It section.

Is this sufficient coverage? Do we want to add more -- either sentences, links, additional section?

Line 152 of https://github.com/w3c/accessibility-intro/blob/master/index.html#L152

<p>WAI's coverage of web accessibility includes '<a href="http://www.w3.org/WAI/intro/wcag.php">web content</a>' (websites and web applications), <a href="http://www.w3.org/WAI/intro/atag.php">authoring tools</a> (such as content management systems (CMS) and blog software), browsers and other '<a href="http://www.w3.org/WAI/intro/uaag.php">user agents</a>', and <a href="http://www.w3.org/WAI/PF/">W3C technical specifications</a>, including <a href="http://www.w3.org/WAI/intro/aria.php">WAI-ARIA</a> for accessible rich Internet applications.</p>

The link 'W3C technical specifications' points to the WAI PFWG which is discontinued.

Proposed:
s/
and <a href="http://www.w3.org/WAI/PF/">W3C technical specifications</a>, including <a href="http://www.w3.org/WAI/intro/aria.php">WAI-ARIA</a> for accessible rich Internet applications.
/
and W3C technical specifications, including <a href="http://www.w3.org/WAI/intro/aria.php">WAI-ARIA</a> for accessible rich Internet applications and <a href="https://www.w3.org/WAI/APA/">APA</a> for accessible platform architectures.
/

I want to make sure that this is the current working repository that replaces https://github.com/w3c/wai-intro-accessibility.

If so, we can delete w3c/wai-intro-accessibility, as no work happened there, to avoid confusion.

👋 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.