Jump to content 
Important notes:

This page is archived information that is not up-to-date.

Information about EOWG closing is in the 19 September 2024 blog post: Accessibility education and outreach: Another milestone in W3C's 30-year history and evolution.

This Wiki page was edited by participants of the EOWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Gallery of accessible web components/Brainstorming

From Education & Outreach

Name/Title

EOWG discussions (recent first):

Perspectives on X

The title might end up being something like:

Accessible UI Components: [X] of Widgets, Templates, Frameworks

with a short name of:

Components [X]

Note: The list below does not include these words ruled out because they could imply that we created or host the thingies: Repository, Library, Bank, Collection. Some of the words below some people think imply created or hosted.

  • List
  • Index
    • + it is really an index
    • + "an alphabetical list of names, subjects, etc., with references to the places where they occur"
    • – index applies to own material (like in a book) - i.e., we create/host
    • – makes me think of books or info not widgets to use
    • (my brain completes it to index.html automatically…)
  • Gallery
    • + Gallery implies a collection of different items
    • + it is an exhibit, you can browse among it, select from among, etc.
    • + if we are actually able to show the example of the "component"
    • – feels like things to view not things to use
    • – sounds like our collection (i.e., we create/host)
    • – sounds very visual
    • – not codey at all, art gallery
  • Catalog
    • + reminds me of library catalogue
  • Directory
    • ? directory leads you onto something else
    • – too official
    • – Directory usually tries to encompass everything
    • – Too authoritative, comprehensive
  • Toolbox
    • – sounds like we have them here (i.e., we create/host)
    • – Toolboxes hold tools... not components

Administration

  • Will there be a review?
  • Who will review what?
  • How do we make sure that nobody is submitting really inaccessible stuff?
  • Do we need user accounts? That would make the whole thing much more complicated (although, I think we could bend wordpress which integrates into LDAP AFAIK).
  • Would it be possible to run this thing through Github, e.g. Vendors would add a file with descriptions into their repository and would submit only the URL of the repository to our project.
  • What is with versions? Will new versions be separate items?
  • What licenses do we consider “freely available”‽
  • What about a list of candidate components that need to reach a specific number of votes to get into the main Gallery?
  • Let a distinct group downvote bad submissions for a period of time before going online.

List

  • (optional?) Link to an accessibility statement
  • Thumbs up/Star/Like
    • To not have any old projects stuck on the top of the list:
      • With only stars sent in the last 30 (90?) days counting
      • Or with stars sent in last 30 (90?) days counting full, next 30 (90?) days counting half
  • Github integration (likely)
    • Display open issues
    • Display how often the project was starred
  • Twitter integration (unlikely)
    • Being able to tweet about a component from the component page to enable communication on specific aspects of the tool
    • Collecting all the tweets of the last 30 (90?) days
      • Admins should be able to favorite tweets that stay longer and are marked as highlights or something

Submission form

Retrieved from "https://www.w3.org/WAI/EO/wiki/index.php?title=Gallery_of_accessible_web_components/Brainstorming&oldid=15348"