[Draft] Analysis for Accessibility page and blurbs for W3C site redesign
- pages with relevant blurbs:
- [done] Accessibility - W3C page
- Web Design and Applications page - Accessibility blurb, plus others
- Browsers and Authoring Tools, Browsers, Authoring Tools
- open: what are other "bucket" pages for accessibility-related info?
Agents (Browsers and Authoring Tools) "bucket" page
Goals
- Get people interested in the sub-pages (Browsers & Authoring Tools)
- ... (these are rough ideas as discussion starters only)
Audience
- [same as subpages below]
Notes
- ...
- from Jan's 6 January e-mail: Reword "Authoring Tools" caption:
"The Web has given everyone the opportunity to be content creators. - 7 Jan EOWG telecon discussion
Related info:
- Browsers and Authoring Tools placeholder page.
example of another bucket page: Web Design and Applications
March 2011 notes
Emphasise...
- Reading and writing the web - using tools vs. creating tools
- ARIA
Structure...
- Fanfare.
- This is for firstly Developers and secondly for People who use, procure or write policy about software used to read and write to the web. You're in the right place, keep reading.
- Links.
- More discussion if required.
Browsers page
Goals
- Promote UAAG to user agent developers
- Promote UAAG to user agent procurers and IT specifiers
- Promote WAI-ARIA User Agent Implementation Guide
- ... (these are rough ideas as discussion starters only)
Audience
- Browser, media players, & other user agent developers
- Browser, media players, & other user agent procurers and IT specifiers
- ... (these are rough ideas as discussion starters only)
Notes
Related info:
- Browsers placeholder page.
examples of other pages at this level: Multimodal Access, Voice Browsing, Mobile Web, Accessibility, Linked Data - parent page: Browsers and Authoring Tools.
example of another parent page: Web Design and Applications - UAAG Overview
- WAI-ARIA User Agent Implementation Guide
March 2011 Notes
- remove: 'written by people from all over the world, in many different languages, on many different computers, using many different input and output devices.'
- Remove: 'war ensues'
- note The number of people writing accessibility extensions e.g. Firevox, Link numbering thing
- Don't put it all on the browser developer BUT don't make them think that they can rely on extension developers to clear up their mess.
Authoring Tools page
Goals
- Promote ATAG to authoring tool developer
- Promote ATAG to procurers and IT specifiers
- ... (these are rough ideas as discussion starters only)
Audience
- Authoring tool developers
- Authoring tool procurers and IT specifiers
- ... (these are rough ideas as discussion starters only)
Notes
- ...
- from Jan's 6 January e-mail:
Points to make:
- emphasize that W3C takes a wide view on the enormous variety of authoring tools:
e.g. making use of the info in ATAG's definition:
http://www.w3.org/TR/2010/WD-ATAG20-20100708/#def-Authoring-Tool - authoring tools even more diverse than technologies... because each technology can be authored in many different ways...
- user-submitted content (Facebook etc.)
- collaborative authoring (multiple authors in series or parallel)
- mention Live Content authoring
- make the point that the W3C technology Recommendations of the outputted technology(ies) are the starting points for authoring tool developers
- authoring tools are also critical because they can "define the possible" for authors
- authors don't need to "know" they are using authoring tools...the transitions between authoring and browsing are so fluid
- emphasize that W3C takes a wide view on the enormous variety of authoring tools:
- 7 Jan EOWG telecon discussion
March 2011 Notes
- remove: 'written by people from all over the world, in many different languages, on many different computers, using many different input and output devices.'
- Remove: 'war ensues'
- note The number of people writing accessibility extensions e.g. Firevox, Link numbering thing
- Don't put it all on the browser developer BUT don't make them think that they can rely on extension developers to clear up their mess.
- Tweak: "The best authoring tools require less technical knowledge from their users in order to produce accessible, robust web content." - this is not a sufficient requirement for 'best. So there may be a much better authoring tool that does everything else BUT.
- Note 1: Examples of authoring tools: ATAG 2.0 applies to a wide variety of web content generating applications, including, but not limited to:
- web page authoring tools (e.g. WYSIWYG HTML editors)
- software for directly editing source code (see note below)
- software for converting to web content technologies (e.g. "Save as HTML" features in office suites)
- integrated development environments (e.g. for web application development)
- software that generates web content on the basis of templates, scripts, command-line input or "wizard"-type processes
- software for rapidly updating portions of web pages (e.g. blogging, wikis, online forums)
- software for generating/managing entire web sites (e.g. content management systems, courseware tools, content aggregators)
- email clients that send messages in web content technologies
- multimedia authoring tools
- debugging tools for web content
- software for creating mobile web applications
- Note 2: Web-based and non-web-based: ATAG 2.0 applies equally to authoring tools of web content that are web-based, non-web-based or a combination (e.g. a non-web-based markup editor with a web-based help system, a web-based content management system with a non-web-based file uploader client).
- Note 3: Live publishing: ATAG 2.0 also applies to authoring tools with workflows that involve live authoring of web content (e.g. some collaborative tools). For these authoring tools, conformance to Part B of ATAG 2.0 may involve some combination of support before (e.g. for preparing slides), during (e.g. for live captioning as WCAG 2.0 requires at Level AA) and after the live authoring session (e.g. the ability to add a transcript to the archive of a presentation that was initially published in real-time). For more information, see the Implementing ATAG 2.0 - Appendix E: Authoring Tools for Live Web Content.
Related info:
- Authoring Tools placeholder page.
examples of other pages at this level: Multimodal Access, Voice Browsing, Mobile Web, Accessibility, Linked Data - parent page: Browsers and Authoring Tools.
example of another parent page: Web Design and Applications - ATAG Overview
- Selecting and Using Authoring Tools for Web Accessibility
[The information below is old notes for a page that is already completed.]
Accessibility - W3C Main Page
About the doc
Purpose, Goals, Objectives
- introduces accessibility
- encourages action, encourages readers to learn more, encourages readers to make their website accessible
- speakers especially to people:
- not aware of accessibility issues
- not convinced of the importance of accessibility
- gives idea of the breadth of resources available from WAI, that is: "need more info about xyz? we've got it for you on the WAI site!"
Relevant points from the 2005 WAI site redesign:
- is welcoming, encourages visitors to use the site; draws people in - into the site, into WAI process, into Web accessibility
- "talks" to wide range of audiences, identifying needs and meeting needs
- facilitates easy understanding of web accessibility issues; inspires confidence that people can "do" accessibility
- is seen as the definitive (re)source, authoritative, credible; comprehensive, yet not overwhelming
- fosters accessibility adoption and "evangelism"; increases positive attitudes towards accessibility; is inspiring
Audience for this Document
- Primary will be people browsing through the W3C site who land on the Accessibility page, or read the Accessibility blurbs -- thus this will likely be readers less familiar with accessibility and WAI (as they would usually go right to the WAI pages), yet most will be somewhat familiar with W3C. Thus we especially want these blurbs and pages to address people
- not aware of accessibility issues
- not convinced of the importance of accessibility
- Secondary audience includes people already familiar with accessibility
Notes
- WAI branding on Accessibility page - Ian prefers not
References and version comments
- 11 Sept 2008 draft
- EOWG minutes 11 Sept
- 10 Sept 2008 draft
- 09 Sept 2008 draft
- 04 Sept 2008 draft
- EOWG minutes 4 Sept
- 03 Sept 2008 draft (there were only 2 minor changes from the 29 Aug version: "badly written" to "badly written/coded", and a CSS change for font size)
- 29 Aug 2008 draft
- 28 Aug 2008 draft
- 28 Aug 2008 draft discussed during EOWG
- EOWG minutes 28 Aug
- 27 Aug 2009 draft
- 25 Aug 2009 draft A
- 25 Aug 2009 draft L - please see e-mail thread about this version
- 24 Aug 2009 draft
- lots of discussion on the EOWG mailing list, detailed one is:
25 Aug e-mail thread "w3.beta Comments for discussion" from Liam - 21 Aug 2009 draft - changes: intro significantly; order of sections: why, what, how, tweaked wording for flow. See also 21 Aug wording drafts.
- EOWG minutes 21 Aug
- 20 Aug 2009 draft A
- 20 Aug 2009 draft B - order of sections rearranged
- 19 Aug 2009 draft - changes: tweaked text to try to shorten & improve flow. filled in @@s near the end
- 18 August e-mail thread "Accessibility page for beta.w3.org"
- 18 Aug 2009 draft A
- 14-18 Aug EOWG mailing list archives - several with subject "Re: stab at betaw3" are relevant
- 18 Aug 2009 draft L - the minimalist version - while eloquent, this one doesn't use the current beta.w3.org template design noted in email
- 17 Aug 2009 draft - a universality experimental version
- EOWG minutes 14 Aug 2009
- 13 Aug 2009 draft B
- 13 Aug 2009 draft A
- 11 Aug 2009 draft
- EOWG minutes 10 July 2009
Changes & Notes
See "References" section above for previous drafts with some change notes, meeting minutes, and such.
Once the document is stable, more detailed changes will be recorded in this section.
- UN convention links:
http://www.un.org/disabilities/default.asp?id=269
http://www.un.org/disabilities/default.asp?id=281 - 28 Aug - removed from end of Why section: "Accessibility enables your website and web tools to be used effectively by more people and in more situations."
- 17 Aug - additional wording at end of first paragraph took out: Web accessibility means that people can perceive, understand, navigate, and interact with the Web in diverse situations; that includes contributing content to the Web.
Archive Notes
4 Sept wording ideas
Introduction:
- Current:
The Web is fundamentally designed to work for all people, whatever their hardware, software, language, culture, location, or physical or mental ability. When the Web meets this goal, it is accessible to people with a diverse range of hearing, movement, sight, and cognitive ability.
Thus 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. However, when websites, web technologies, or web tools are badly designed, they can create barriers that exclude people from using the Web.
The mission of the Web Accessibility Initiative (WAI) is to lead the Web to its full potential to be accessible, enabling people with disabilities to participate equally on the Web.
- Second sentence and paragraph breaks different:
The Web is fundamentally designed to work for all people, whatever their hardware, software, language, culture, location, or physical or mental ability.
When the web meets its full potential, it allows people with a diverse range of hearing, movement, sight, and cognitive ability to use the web equally well. Thus 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.
However, when websites, web technologies, or web tools are badly designed, they can create barriers that exclude people from using the Web. The mission of the Web Accessibility Initiative (WAI) is to lead the Web to its full potential to be accessible, enabling people with disabilities to participate equally on the Web.
- more like what we talked about in the EOWG telecon [differences noted in brackets]:
The Web is fundamentally designed to work for all people, whatever their hardware, software, language, culture, location, or physical or mental ability.
When the Web meets [its full potential], it is accessible to people with a diverse range of hearing, movement, sight, and cognitive ability. Thus the impact of disability is radically changed on the Web – because the Web removes barriers to [getting information,] communication, and interaction that many people face in the physical world.
However, when [the Web does not reach its potential because] websites, web technologies, or web tools are badly designed, they can create barriers that exclude people from using the Web.
[Leading the Web to meet it's full potential to be accessible, thus enabling people with disabilities to participate equally on the Web, is the mission of the W3C Web Accessibility Initiative (WAI).]
transcripts made easy.
- now: It's easy and relatively inexpensive for website developers to provide transcripts for podcasts and audio files. There are services that create text transcripts in HTML format.
- was, and could go back to being: Providing transcripts for podcasts and audio files is easy and relatively inexpensive [for website developers]. There are services that provide[offer/create/produce/make] text transcripts in HTML format.
28 August wording ideas
- Liam for "Why" section:
Barriers are often introduced unintentionally - we provide extensive support to help managers, developers and site owners ensure their sites are accessible to all.
Sometimes, however, barriers are intentionally allowed to occur, where a site's disabled audience is believed to be low or non-existent - we provide data and case studies for those who are making these decisions.
25 August wording drafts
- intro: modification of Liam's suggestion:
The web should be accessible to everyone, including people with different levels of vision or hearing, different ranges of movement, different levels of literacy or cognitive function, different software, hardware or internet connection speeds.
The web radically changes the nature of disability - it removes barriers to communication and interaction. However, badly written web pages or technologies re-introduce these barriers.
The W3C Web Accessibility Initiative works to help legislators, programmers, developers, managers and site owners prevent such barriers reappearing.
21 Aug wording drafts
- intro:
- The web is fundamentally designed to be available to all people, whatever their hardware, software, language, culture, location, or physical or mental ability. Accessibility focuses on this last aspect of diversity, and overlaps with the others.
- When the web meets its full potential, it is accessible to everyone, including people with a diverse range of hearing, movement, sight, and cognitive ability. The flexibility of the web enables people with auditory, physical, visual, and some cognitive impairments to use the web just as well as anyone. Think about what this means: There is no such thing as a disability on the web. ... However: When websites and web tools are not accessible, they disable people.
21 Aug EOWG discussion
- first paragraph: At its foundation, the web is designed to be available to "all people, whatever their hardware, software, network infrastructure, native language, culture, geographical location, or physical or mental ability." Accessibility focuses on one aspect of this, and overlaps with others."
question: Is this good to put accessibility into context with these other things? Or is it not worth the space? - second paragraph, first sentence:
- Accessibility is developing the web to meet its potential to be usable by people with a diverse range of capabilities.
- Web accessibility is developing websites and web tools to meet the potential of the Web to be usable by people with a diverse range of capabilities.
- second paragraph, second sentence:
- Accessibility is about not disabling people from using your website or web software because they can't hear, move, see, or understand well. Accessibility is enabling your website to be used effectively by more people and in more situations.
- Accessibility is about not disabling people from using your website or web software because they don't have a certain level of dexterity, eyesight, hearing, neurological function, or cognitive ability due to a permanent impairment, injury, or simply aging. Accessibility is enabling your website to be used effectively by more people and in more situations.
- in the Alt Text section, is "(Some visual browsers display this text in a little popup when you hover over the image.)" good for novices? or not worth the space?
Misc
- Tim quotes
- "The social value of the Web is that it enables human communication, commerce, and opportunities to share knowledge. One of W3C's primary goals is to make these benefits available to all people, whatever their hardware, software, network infrastructure, native language, culture, geographical location, or physical or mental ability." - Tim <http://www.w3.org/2008/04/dd-global.html>