w3c / wai-components

Important

This repository has been archived 16 May 2024.

Essential Components of Web Accessibility is now edited in the wai-website repository.

wai-components's Issues

Link to long descriptions of illustrations

The illustrations have long descriptions. An obsolete longdesc attribute is used in the img tag. It is difficult for people who need long descriptions to reach the page with descriptions. How about adding a link to long descriptions of illustrations at the beginning of the article?

link fixes needed

https://validator.w3.org/checklink?url=https://www.w3.org/WAI/beta/fundamentals/components/

Images for translation

[low] images smaller. centered?

hey @remibetin I think some of the images were smaller in the original. and centered. Not a big deal, yet nice to go back to that if easy. :-)

Redundant section in wai-components-example.md

The "Components and Guidelines Illustration Description" section in the document Descriptions of Essential Components of Web Accessibility Illustrations is redundant. The image is already described in the first section "How the Components Relate Illustration Description"

[low] changelog

https://www.w3.org/WAI/EO/changelogs/cl-components

• add recent tweaks
• un-comment-out in footer
• address issues

Still learning

breadcrumb wrong

https://www.w3.org/WAI/fundamentals/components/examples/

fix colors to avoid relationship confusion

Fix color that implies relationships that are not correct:

• HTML, ARIA, CSS are on blue background. SVG, SMIL, ETC. are on orange background. They shouldn't be on either.
• ATAG and WCAG are blue. UAAG is orange.

Prepare for Translations

rel: w3c/wai-translations#22

Add a bit up front about standards & clarify guidelines are standards

Assuming leave as first link under "Standards/Guidelines" in nav:

• Add a bit more about standards up front
• clarify WAI Accessibility Guidelines = W3C Recommendations = Web Standards
  and things like ARIA = W3C Recommendations = Web Standards

WAI-ARIA add at least a little about it

To help clarify the misunderstanding that one would either use WCAG or ARIA, and to put it into context with the other stuff.

big image +ARIA

to https://www.w3.org/WAI/intro/specs.png add ARIA - and maybe others - probably replacing some in the bottom line, not adding new row

Stadtwerke

Starts asap

title/name

Please:

• Skim the document content
• Skim the requirements
• Read and think about previous discussions on the title:
  ** e-mail thread - click "Next in thread" to see more
  ** minutes 1
  ** minutes 2
• See where it is in the draft navigation — under "Accessibility Fundamentals" and "Standards/Guidelines" - with placeholder renaming "How Accessibility Works" update: How Standards Work Together

Please comment on:

• pros, cons, considerations of "Essential Components of Web Accessibility"
• pros, cons, considerations of "How Accessibility Works" update: How Standards Work Together

Please add other brainstorms, along with pros, cons, considerations for them...

[!!] Inconsistency with capital letters after bullets

Introduction section - uses lower case to start each bullet except for one time.
Interdependencies Between Components section - uses capital letters to start each bullet

I believe that the Introduction section should start with capital letters for each of the 7 bullets.

COLIN JAMES BARR

New issue

Preparations for the Redesign

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

Use of the word "developers" in the introduction

Criticality: low
Priority: low

The introduction section refers to the various components, and refers to anyone who has a role to play in web content as developers.

developers - designers, coders, authors, etc., including developers with disabilities and users who contribute content

I have a problem with referring to everyone who has a role to play in web content as a developer, whether they're an actual developer, a content writer, a designer, a tester, or whatnot. I think it might give people the wrong idea about who we have in mind... Why not use another qualifier instead, such as web stakeholders, or web resources, even?