This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
(Taken from a meeting between Chris Mills and Shawn Lawton-Henry from the WAI/EOWG) The EOWG/WAI wants to integrate a11y info into other parts of the site as much as possible, and not have a separate a11y section for things like alt text, for example. I think we can all agree on this. The WAI doesn't want to lock down WPD a11y content, but they want to make sure people are contributing in the right place. Shawn doesn't want the main landing page to change much. But she can monitor changes to that one page (http://docs.webplatform.org/wiki/concepts/accessibility). ----------------------------------------- Things that would fit well on webplatform ----------------------------------------- The definition Shawn and Chris came to an agreement on: * Any a11y tech stuff will generally fit on webplatform. * Any disability definition stuff, or business case stuff probably is better left to WAI. Stuff we thought would fit well on webplatform is as follows: * WAI-engage community group material - can we put this stuff on Webplatform.org? Yes, absolutely * WAI teacher training resources - already exist. http://w3.org/WAI/training. At least point to these on webplatform * http://www.w3.org/TR/wai-aria-primer/ - Shawn wants to give this to us; suitable for webplatform? * accessibility site review - another project by WAI - put this on web platform? * Let's add how screenreaders work to webplatform - ideal contribution for web platform * "Where a11y fits into the process"? good document for webplatform - how to make a11y part of good web design. --------------------------------------------------------------------------- Things that don't fit well on webplatform, or are already covered elsewhere --------------------------------------------------------------------------- * Pages about auditory, cognitive, mobility, visual impairment - can we remove those? Basics page already points to those. * Testing tools - already pointed to on the basics page. * AT - on basics page * Definitions of disabilities - on basics page * Bringing a11y into organization - on basics page * Not much on evaluation - WAI currently working on those. New section added soon to a11y basics page. * Writing for an accessible web - move to "writing content for the web" type section * standards - covered in web accessibility basics * WCAG at a glance? WAI already have this - point at this from a11y basics page. With these points in mind, we should go through John Foliot's list of article stubs at http://docs.webplatform.org/wiki/accessibility_article_ideas and prune the ones that don't fit under our new definition and direction. ----------- legal stuff ----------- This is a bit of a minefield - webplatform.org nervous to touch it, WAI only touch on it very lightly. It's probably better to just leave it. ----------------------- Other topics to discuss ----------------------- * There is an Accessibility flag available on WPD, but the original intention for this was for pages that have inaccessible content. However, we also need a separate flag for articles that should have a11y info baked in. Shawn wants to be able to monitor this list. * She also wants to have notes to provide more info about what needs to be included in terms of a11y content on these pages. Editorial notes are a good place for this, BUT They shouldn't show up in the article, AND they should appear in the flag list, e.g. on http://docs.webplatform.org/wiki/Special:SearchByProperty/Content_quality_flag/Accessibility. * It doesn't seem to be so easy to monitor new pages being created - how do we find these? We should be able to pull up a list of articles that contain the keywords accessibility, disability, WCAG. * Who is ultimately responsible for merging and deleting? Chris happy to have final say on this.
Reverting this bug's platform to All, as experience happens on all platforms.
While going through this list here at Web Platform Doc Sprint in Berlin, we're not sure which content from WAI should be moved over to webplatform.org and which content should remain at W3C WAI. E.g. it says “business case stuff probably is better left to WAI”, but then it says “"Where a11y fits into the process"? good document for webplatform” - which to us reads like “business case stuff”, right? Same goes for most of the suggested articles at http://docs.webplatform.org/wiki/accessibility_article_ideas - they all seem to be beyond scope as per the above definition and better suited for WAI. Reason I'm asking is, we have tons of articles that originated at w3.org/wai and that were translated from English to German (see box on the right at http://www.einfach-fuer-alle.de/wcag2.0/) that we would like to add to webplatform.org, and we're not sure what's appropriate and what's not.