w3c / wai-fundamentals-overview Goto Github PK

edit ideas:

1. intro sentence:

The... course provides the foundation for making your websites, apps...

-> + "you need":

The ... course provides the foundation you need for making your websites, apps...

or different bolding:

The ... course provides the foundation you need for making your websites, apps...

@cmuncharaz Do you want to do this translation, or should I try to find someone else?

Currently there's WCAG conformance logo on the page. It's full of acronyms.

Short-term solution was to add this to the main text:

The course covers principles from the World Wide Web Consortium (W3C) Web Accessibility Initiative’s (WAI) Web Content Accessibility Guidelines (WCAG)...

I think we want to simplify -- delete that sentence and put the acronym expansions in small text under the logo.

Thoughts?

asap:

• figure out if really do want non-youtube alternative to be TPAC page or other, and add Makotos
• to trainer headshots near end:
  • fix bug when photos go to two lines (e.g., browser zoom), then the names in the first row are overlapped with the photos in the second row.
  • CSS so images stay on one line in big viewports configurations (and shrink as needed) and do other nice stuff in different size viewports (e.g., if wrap to multiple lines, doesn't cut off the names)
  • add names underneath (thanks Laura!)

maybe -- to be determined:

• add student quote(s)
• to trainer headshots near end, add contributors (could be separate list, or after name it has something like "trainer" or "demo-er"/"contributor")

lower priority:

• CSS - clean up the in-line CSS throughout
• fix and polish blockquote hack for smaller (https://wai-website-theme.netlify.app/components/blockquotes/#pullquote-color-alt-2)
• add links to this page throughout website, e.g., in
  • Fundamentals overview, sitemap, resources page
  • Intro page
  • training page(s)?
  • ...
• use video with yellow side background (instead of blue) (update in YouTube)
• add pointer from original blog post to the new course page
• tweak CSS so there is less space after "Provided by" heading and following paragraph

site-wide maybe?

• make the alternatives for video heading smaller and paler?

updated text:

For example, you can choose to focus on:

• Coding web applications to meet international W3C standards.
• Designing interfaces to meet the needs of people with disabilities, including older users.
• Writing a business case to present to management.
• Advocating for accessibility by understanding real-life experiences of how accessibility is essential for some, and useful for all.
• Managing accessibility in projects and in organizations.
• Checking web pages for basic accessibility issues and improving accessibility.

consider:

1. Checking -- Is that well understood to broad audience? Would testing or evaluating be better? (probably not for novice audience)

2. changing "writing" (which on the WAI website often refers to writing content).
   instead bold "business case" or such.
   (Shawn did it on purpose - to get "writing" and "business case" in the bullet list -- yet is open to doing it differently.)

English: ... Describes tools and approaches that people with different kinds of disabilities use to browse the web and the barriers they encounter due to poor design.

French:... Décrit les outils et les solutions pour lesquelles les personnes qui présentent différents types de handicaps optent pour naviguer sur le Web et les obstacles auxquels elles se heurtent lorsque le design n’est pas optimal.

Comment: I it better in French to use "approches" in the French version since we do not speak of "solutions" in the English. Second, is it possible to simplfy the second part of the sentence to "les obstacles recontrés" instead of "les obstacles auxquels elles se heurtent"

Originally posted by @vmmiller in #33 (comment)

English: "Accessibility, Usability, and Inclusion"

French translation: Accessibilité, ergonomie, et inclusion (en anglais)

I was just wondering if "usabilité" could be used or is "ergonomie" the usual translation for usability, usability testing etc.

Originally posted by @vmmiller in #33 (comment)

published version: https://www.w3.org/WAI/fundamentals/foundations-course/

update 8 Dec:

• draft preview with TOC: https://deploy-preview-18--wai-fundamentals-overview.netlify.app/fundamentals/foundations-course/#course-comments-and-survey-response added TOC to published page
• Note that the TOC box also houses a callout box now -- so it looks better!

pro: people can more easily jump to the information they are more interested in. people will want different information first. Some will want to know who the course is for, others Duration, others Video excerpts from the course, and others maybe Course comments and survey responses.

Consider adding heading before the syllabus list -- in middle of "What you get from the course" section.

Maybe h2 like "What's in the course

• [minor] H2 not smooth 'cause sentence at the end applies to both sections/lists

More “What you’ll learn” and syllabus is in the edX course page.

Maybe h3 - something like "Course Content"

update 8 Dec:

• draft preview with TOC: https://deploy-preview-18--wai-fundamentals-overview.netlify.app/fundamentals/foundations-course/#course-comments-and-survey-response added to published page: https://www.w3.org/WAI/fundamentals/foundations-course/

EOWG, any:

• Comments on including quotes such as these in general?
• Comments on these specific quotes -- in these locations?
• Ideas for others in addition to, or instead of? others: https://www.w3.org/WAI/EO/wiki/Promoting_W3Cx_Intro_Course#student_public_comments

English: Learn about the impact of accessibility and the benefits for everyone in a variety of situations.
French: Les vidéos suivantes exemplifient l’impact de l’accessibilité et les bénéfices pour tous dans diverses situations.

Proposed text:
Découvrez l'impact de l'accessibilité et les avantages pour tout le monde dans diverses situations.

under https://www.w3.org/WAI/fundamentals/foundations-course/#what-you-get-from-the-course

The AI and Accessibility Research page is a great resource! Thank you. Would it be possible to make the paragraphs shorter in all the descriptions? I think you know why I'm suggesting this.