https://www.w3.org/WAI/EO/wiki/api.php?action=feedcontributions&feedformat=atom&user=Jsutton2Education & Outreach - User contributions [en]2024-03-19T09:46:33ZUser contributionsMediaWiki 1.41.0https://www.w3.org/WAI/EO/wiki/index.php?title=Web_Accessibility_Preliminary_Evaluation&diff=4015Web Accessibility Preliminary Evaluation2013-02-22T00:31:14Z<p>Jsutton2: /* Next Steps */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]] > [[Main_Page#Evaluation_pages | Evaluation Pages ]]<br/><br />
Old page on WAI website: [http://www.w3.org/WAI/eval/preliminary.html Prelim Eval]<br/><br />
<br />
=Notes=<br />
* '''[http://www.w3.org/WAI/EO/Drafts/eval/checks WAI draft page]'''<br />
* '''For tasks, example use cases with audience, and focus for this and related documents, see the [[Eval Analysis]] page, including the table at the top and the specific [http://www.w3.org/WAI/EO/wiki/Eval_Analysis#Preliminary_Evaluation_Analysis Analysis] section at the bottom'''<br />
* A template for the check items is at the top of the [http://www.w3.org/WAI/EO/wiki/Talk:Web_Accessibility_Preliminary_Evaluation discussion tab].<br />
* For previous drafts and contributed material, see:<br />
** '''[[Prelim Eval 2013-Feb-08]] - snapshot of draft on 8 February 2013 in the middle of edits'''<br />
** '''[[Prelim Eval 2013-Feb-01]] - snapshot of draft on 1 February 2013 before edits'''<br />
** '''[[Prelim Eval 2013-Jan-24]] - snapshot of draft on 24 January 2013'''<br />
** '''[[Prelim Eval 2013-Jan-17]] - snapshot of draft on 17 January 2013'''<br />
** Extensive revisions and suggestions at [[Archived_Work_on_PreLimEval]] ([http://www.w3.org/WAI/EO/wiki/Archived_Work_on_PreLimEval#Check_link_text_.5B15:_probably_not.5D_.5Bpartly_drafted.5D Links section])<br />
** From Wayne & Tom [[Prelim Eval input: Smart analysis simplified]]<br />
** Old page with Denis' edits and Ian's input in [[Preliminary Eval - old notes]]<br />
<br />
__NOTOC__<br />
<br />
<span style="background:yellow;">'''''Important Note''''': For this draft we have some tool-specific guidance. However, there are potential issues with vendor-neutraility and we might need to address this a different way &mdash; for example, moving tool-specific guidance to WebPlatform Docs or the WAI-Engage wiki where people can easily add other tools.</span><br />
<br />
= Easy Checks - A First Look at Web Accessibility=<br />
[http://www.w3.org/WAI/EO/wiki/Eval_Analysis#Title_ideas title ideas]<br />
<br />
==Contents==<br />
* [[#Introduction]] (in WAI draft page)<br />
* [[#Page title]] (in WAI draft page)<br />
* [[#Image text alternatives ("alt text")]] (in WAI draft page)<br />
* [[#Headings]] (in WAI draft page)<br />
* [[#Color contrast]] -<br />
* [[#Zoom and text size]] - <br />
* [[#Keyboard access, content order, visual focus]] - updated 19 February<br />
* [[#Multimedia (video, audio) alternatives]] - updated 19 February<br />
* [[#Forms, form labels, and error messages]] - updated 19 February<br />
* [[#Next Steps]] - updated 21 February<br />
''<span style="color:#808080;">[Thanks to [[#Contributors]]!]</span>''<br />
<br />
==Introduction==<br />
'''[http://www.w3.org/WAI/EO/Drafts/eval/checks#introduction Introduction in WAI draft page]'''<br />
<br />
===<span style="color: #808080;">EOWG Comments on the Introduction</span>===<br />
<br />
<div style="color: #808080;"><br />
* [done - changed] editor's discretion:section tools.<br />First sentence: <br />"Most of these checks you can do with any browser, that is, you do not need to download anything."<br />Are the words in the right order in this sentence or should it be: <br />"You can do most of these checks with any browser, that is, you do not need to download anything"? {Sylvie}<br />
* [done - this was from the wiki to HTMl conversion -- it added title to all links with the URI. I've removed them. good catch!]Clarity of links:<br />It is not easy for the readers to read the links to the different tools as http text. May be the name of the tool/browser would be more useful?<br />Example: Link text:<br />"http://www.mozilla.org/en-US/firefox/new/". <br />Or: <br />"https://addons.mozilla.org/en-US/firefox/addon/web-developer/add-on."<br />The link text questions seems to concern all the documents linked on this page. {Sylvie}<br />
<br />
* comment {name}<br />
<br />
</div><br />
<br />
==Page title==<br />
<br />
'''[http://www.w3.org/WAI/EO/Drafts/eval/checks#title Page title in WAI draft page]'''<br />
<br />
===<span style="color:#808080;">EOWG Notes on Page Title</span>===<br />
<br />
<div style="color:#808080;"><br />
<br />
* [done] the shortcut with the WAT toolbar is no direct one: <br />You first have to press ctrl+alt+6, then press down arrow key once or type the first menu letter, maybe H for the English version of the toolbar? {Sylvie} [Thanks, Sylvie! I added it. {Shawn}]<br />
<br />
* [add to wish list for later] The text says: "The first thing screen readers say when the user goes to a different web page is the page title. Page titles are important for orientation — to help users know where they are and move between open pages."<br />Would it be useful to have a sound clip of the screen reader going through page titles? Low priority, but maybe neat for people who don't know screen readers? {Shawn}<br />
<br />
* [done? edited to simplify] The text says: "Most browsers have a window title bar by default, except Chrome and IE versions 9 and later. In those browsers, and most others, you can see the full page title by hovering over the tab". <br />Suggested text: "Many browsers have a window title bar and tabs, whereas others, such as Chrome and IE versions 9 and above, use tabs only to display the page title. For browsers with tabs only hover over the tab to view the full page title" {Vicki}.<br />
<br />
* [open] Suggest the alt-text on screen grabs include the browser name and version {Andrew} <br />reply: I think it would add unnecessary clutter - lots of text and do people who cannot see the image care so much which browser & version? what do others think? {shawn}<br />
<br />
* [open] We should include FF web developer toolbar example too - 'Information' then 'View Page Information' opens a new window with the page title at the top {Andrew}<br />why? the page title is shown in the window title bar so why would you need to use the develop toolbar to get it? {shawn}<br />
<br />
* comment {name}<br />
<br />
====<span style="color:#808080;">Images for Page Title</span>====<br />
* To check page title - with IE WAT:<br /><...image link here...><br />
<br />
</div><br />
<br />
==Image text alternatives ("alt text")==<br />
<br />
'''[http://www.w3.org/WAI/EO/Drafts/eval/checks#images alt text in WAI draft page]'''<br />
<br />
===<span style="color:#808080;">EOWG Notes on alt text</span>===<br />
<br />
<div style="color:#808080;"><br />
<br />
* [done? "Some people prefer most images to have more detailed description; and others prefer much less description."] Text reads: "Some people prefer more description of more images; and others prefer less description." <br />Suggested simplified wording: "Some people prefer more descriptive text, others prefer less". or "Some people prefer more description of images, others prefer less." I would remove the "more" of "more images" {Vicki} <br />The issue is that for a given image, some people think there should be no alt at all, some think there should be brief alt, and some think there should be detailed alt. I think your re-wording misses that some people want some images to have no description at all, whereas others think those images should have some description. I tried another edit in between. :-) {shawn}<br />
<br />
* [done, with slight tweak.] Last paragraph. Text reads: (So "alt tag" is technically incorrect; it's "alt attribute", or you can say "alt text".) <br /> Minor editorial comment. Suggested text: (So "alt tag" is technically incorrect; "alt attribute" would be the correct term or you can say "alt text".) {Vicki}<br />
<br />
* [done] Editorial plus typo comment: Text reads: "The first one is easiest of you have the WAT toolbar." Corrected text: "The first one is the easiest if you have the WAT toolbar.". {Vicki}<br />
<br />
* [done] First check, point 2.: Guidance indicating color "...on a tan background." I think this might depend on the browser version and also the resolution. My version, for example, shows a pinkish background. Perhaps, you could say "... on a colored background". {Vicki}<br />
<br />
* [done] First check, point 4.: Editorial."... Tips below." The Tips are above. {Vicki}<br />
<br />
* <span style="background:yellow;">[open EOWG]</span> Finally, I'm mulling over the term "inappropriate alt text". Would that be the correct term? {Vicki}<br />other ideas?<br />
<br />
* comment {name}<br />
<br />
====Keyboard Access {Andrew}====<br />
[done - add to WAI draft page 20 Feb {Shawn}]<br />
* To check alt text - with IE WAT {Andrew}<br />
** ctrl-alt-4, then arrow down to 'show images' which displays the alt-text adjacent to the image<br />
* To check alt text - with FF toolbar<br />
** Alt + 'T' for "Tools", then 'W' for "'''W'''eb Developer Extension", then 'I' "'''I'''mages", then 'O' for "'''O'''utline Images", then 'A' for "Outline Images Without '''A'''lt Attributes"<br />
** Alt + 'T' for "Tools", then 'W' for "'''W'''eb Developer Extension", then 'I' "'''I'''mages", then 'A' for "Display '''A'''lt Attributes"<br />
<br />
</div><br />
<br />
==Headings==<br />
'''[http://www.w3.org/WAI/EO/Drafts/eval/checks#headings Headings in WAI draft page]'''<br />
<br />
===<span style="color:#808080;">EOWG Notes on Headings</span>===<br />
<br />
<div style="color:#808080;"><br />
* [done] heading h4: "To try checking headings in BAD" <br />There seems to be one or two words too much:<br />"Follow the one of the instructions under "To check headings outline" above"<br />Suggestion: <br />"Follow one of the instructions under "To check headings outline" above" {Sylvie}<br />
<br />
* comment {name}<br />
<br />
<br />
==== Keyboard access {Andrew}: ====<br />
[done - add to WAI draft page 20 Feb {Shawn}]<br />
* To check headings outline - with IE WAT<br />
** Ctrl + 6, then down arrow to "Heading Structure"<br />
* To check headings outline - with FF toolbar<br />
** Alt + T, then 'W' for "'''W'''eb Developer Extension", then 'I' for "'''I'''nformation", then 'm' for "View Docu'''m'''ent Outline"<br />
* To show heading markup in the page - with IE WAT<br />
** Ctrl + 6, then down arrow to "Headings"<br />
* To show heading markup in the page - with FF toolbar<br />
** Alt + T for "Tools", then 'W' for "'''W'''eb Developer Extension", then 'O' for "'''O'''utline", then 'S' for "'''S'''how Element Tags Names When Outlining"<br />
** Alt + T for "Tools", then 'W' for "'''W'''eb Developer Extension", then 'O' for "'''O'''utline", then 'H' for "Outline '''H'''eadings"<br />
<br />
</div><br />
<br />
==Color contrast==<br />
<br />
''[Anna Belle and Sharron are editing this section. Here is the previous [http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Feb-01#Check_color_contrast 1 February draft of color contrast] with lots of text.]''<br />
<br />
[[#Contents|back to Contents]]<br />
<br />
<hr /><br />
<br />
==Zoom and text size==<br />
<br />
People with mild to moderate visual impairments may need to enlarge content in order to read it, or read it without straining. This simple requirement is mostly achieved by the functionality of the browser and ensuring that the page design supports that functionality. <br />
<br />
Most browsers offer two ways of enlarging content: page zoom and text resize. Page zoom works by scaling up the page content, so that text, images, and buttons are all increased or decreased in size, and the integrity of the layout is maintained. Text resize only affects text, although implementation techniques can be used to also change the widths and heights of containers, margins, padding, and other aspects of the design.<br />
<br />
Not all browsers offer both choices, and some browsers will not resize text if it has been set using fixed units such as pixels.<br />
<br />
* In browsers that support zoom, increase zoom level to 200% or maximum zoom if smaller than 200%<br />
* In browsers that support text resizing, increase text size to 200% or maximum size if smaller than 200%<br />
<br />
===What to do===<br />
<br />
For each browser to be tested:<br />
<br />
* Set the screen window to full width<br />
* Open your preferred browsers. Internet Explorer, Firefox, Chrome and Opera all offer zoom as a function of View or Function menus, or as a keyboard shortcut (usually, Control +, or for Mac Command +). <br />
* In browsers that support page zoom, enable this option and use the appropriate control to increase zoom level to 200% or maximum zoom. <br />
* In browsers that support text resizing, enable this option and use the appropriate control to increase text size to 200% or maximum size.<br />
<br />
===What you will see===<br />
<br />
* For page zoom layout should remain approximately the same for fixed width designs, and will reflow in the same way as resizing the window would at small sizes.<br />
* For text resize most aspects of the design will not change and layout will probably not increase in size. Content will reflow appropriately within the same available space as text increases in size.<br />
<br />
===What to check for===<br />
<br />
* Text should increase in size in both cases, addionally with page zoom all elements on the page should increase in size.<br />
* No content should overlap.<br />
* All controls must be clickable.<br />
<br />
====Note====<br />
Some browsers can expand the text beyond 200% - this is not covered by the resize requirement as it is recognised that this will cause some of the failures described. It is also accepted that some horizontal scrolling may be necessary but see also 1.4.8 which is a AAA requirement. <br />
Users with more severe visual impairments who need larger text are likely to use screen magnifiers to increase text size above 200%.<br />
<br />
===References===<br />
*link to {appropriate section in Accessibility Requirements page http://www.w3.org/WAI/intro/people-use-web/principles#distinguishable} (doesn’t have a lot to say)<br />
*Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background. <br />
*Resize text: Understanding Success Criteria 1.4.4 (Level AA) {http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html}<br />
*Images of Text: Understanding Success Criteria 1.4.5 (Level AA) http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-text-presentation.html<br />
*Visual Presentation: Understanding Success Criteria 1.4.8 (Level AAA)http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-visual-presentation.html<br />
*link to {BAD example} No specific BAD examples – some reference to Text as image in relation to the phone number, and column width.<br /> '''Question for Shadi or others: Are there any BAD pages that break with text or page zoom?'''<br />
<br />
<br /><br />
<hr /><br />
<br />
===<span style="color:#808080;">EOWG notes on zoom and enlarge</span>===<br />
[See [http://lists.w3.org/Archives/Public/w3c-wai-eo/2013JanMar/0010.html e-mail thread on zoom & resize] ]<br />
<br />
<span style="color:#808080;">[done - 1 Feb agreed to include it] We previously thought we wouldn't include this in the easy checks. One of the issues was conflicting perspectives in forums and critiques that 200% is too hard to meet. Ian has re-drafted this section. <br /><br />
Please comment on reasons to include it or not. Feel free to edit the main text as well.</span><br />
<br />
* <span style="color:#808080;">'''[OPEN]''' Does this currently go beyond what is specifically required by WCAG? If so, should we not include that part? See [http://lists.w3.org/Archives/Public/w3c-wai-eo/2013JanMar/0010.html Wayne e-mail 31 Jan] and [http://lists.w3.org/Archives/Public/w3c-wai-eo/2013JanMar/0011.html Ian e-mail 31 Jan] {Shawn}</span><br />
<br />
* <span style="color:#808080;">I would include this as it's well explained and sounds simple :) Often, this is a check which is quite difficult to understand but as it's explained quite clearly here, I would include it. One comment: at the end of the first section (just before "What to do"), there are two bullet points on the browsers and zooming. Shouldn't this be removed and left (as currently duplicated) in the "What to do" section? {Vicki}</span><br />
<br />
* <span style="color:#808080;">comment {name}</span><br />
<br />
<hr/><br />
[[#Contents|back to contents]]<br />
<br/><br />
<br />
==Keyboard access, content order, visual focus==<br />
<span style="color:#808080;">EOWG notes - importance: HIGH.<br />
<br/> 5min: maybe.<br />
<br />15min: yes, at least part of it.<br />
<br />Without visual rendering: @@</span><br />
<br />
Many people do not use the mouse and rely on the keyboard to interact with the Web. While screen reader users rely on the keyboard, they are not the only ones. In addition, sighted users with mobility impairments may rely on the keyboard or have assistive technologies that are controlled through keyboard actions. This requires keyboard access to all functionality. Without using a mouse, a user must be able to make visible, logical progress through the page elements, including links, form inputs, media controls, and other user interface components. <br />
===What To Do===<br />
* Click in the address bar, then put your mouse aside and '''don't use it'''. <br />
* Press the 'tab' key to move through the interactive elements on the page. <br />
* For subsequent movement within elements, such as select boxes or menu bars, press the arrow keys<br />
* To select a specific item within an element, press the Enter key or Space bar.<br />
<br />
===What To Look For===<br />
* Can you tab to all the elements, including links, form fields, buttons, and media player controls? Are there any actions you can't get to (e.g., if they are only available on mouse hover or click)?<br />
* Does the tab order follow the logical reading order, top to bottom, left to right in sequence?<br />
* Watch as you tab through the elements to verify that the focus indicator is clearly visible - that you can visually determine where the focus has currently landed. (Note that common failures occur when the default focus indicator is turned off in CSS or when the element is styled with borders that occlude the focus indicator.)<br />
* Verify that any visual changes that occur with mouse hover also are triggered with keyboard focus<br />
* Can you tab away from all elements that you can tab to and continue tabbing through to the end of the page, circling back again to the top? (e.g. you don't get stuck anywhere and can't move on - known as a "keyboard trap")<br />
* If there is a drop-down list (for example, for choosing from a select box or navigation to another menu-listed page)<br />
** When tabbing into the drop-down box, can you use the down/up arrow keys to move through the options?<br />
** When the listed content receives focus, are items indicated but not selected automatically? Selection should occur only when user signifies choice through additional keyboard action (usually Enter or Space bar)<br />
<br />
===References===<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#keyboard Functionality is available from a keyboard]<br />
* [http://www.w3.org/WAI/users/browsing#keyboard Browsing the Web by Keyboard] section in [http://www.w3.org/WAI/users/browsing Better Web Browsing: Tips for Customizing Your Computer]<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html Focus Visible - Understanding Success Criteria 2.4.7 (Level A)]<br />
*[http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html Focus Order - Understanding Success Criteria 2.4.3] <br />
* Example: [http://www.w3.org/WAI/demos/bad/before/survey.html web page template that does not enable keyboard access] from the WAI Before and After Demo (BAD)<br />
<br />
===Notes===<br />
* Mac browsers by default only tab through forms, will need to turn on...<br />
* not work easily in Opera...<br />
* ...<br />
<br />
<br /><br />
[[#Contents|back to contents]]<br />
<hr /><br />
<br />
==Multimedia (video, audio) alternatives==<br />
<span style="color: #808080;">''[Updated 7 February]''</span><br />
<br />
Check multimedia elements to ensure that visual and audio content includes equivalent alternatives and that the media player is fully accessible. <br />
<br />
===What to do===<br />
These steps will give you a quick and easy first look. They will identify that alternatives for media content have been considered and attempted. A more comprehensive testing process will be needed to verify the quality of the alternatives provided.<br />
# Ensure that media does not begin to play automatically or, if it does, that tit stops after 3 seconds. <br />
# Follow the steps for keyboard access to ensure that the media player controls are labeled and operable by all users.<br />
# Play a short piece of the audio content<br />
# Play a short segment of the video content<br />
<br />
===What to look for===<br />
====Captions====<br />
* Toggle closed captions on (if available). Look in the control panel of the media player for the closed caption icon button. @@include logo image <br />
** Are captions provided?<br />
** Do captions seem in sync to the spoken content? <br />
** Are the people who are speaking identified when they speak?<br />
** Has important audio content other than dialogue been included? (music, door slamming, applause, noises that impact meaning of narrative, etc)<br />
<br />
====Audio Description====<br />
Audio description is a method of using the natural pauses in dialogue or between critical sound elements to insert narrative that translates visual image information into descriptive text, thereby making it accessible to blind members of an audience. On the web, audio description may be provided using a separate audio track or by means of a text description.<br />
* Toggle audio description on (if available). Look in the control panel of the media player for the audio description icon button. @@include logo image <br />
** Is an audio description track provided in the media itself?<br />
** If not, is an audio description provided as text?<br />
<br />
====Transcript====<br />
* If no captions or audio description options are provided, check page for embedded transcript or a link to transcript page. Transcript should contain all dialogue and other meaningful audio content as well as a full description of visual content to the extent it is needed for understanding.<br />
<br />
===Learn more about providing alternatives for media content===<br />
* [http://www.w3.org/2008/06/video-notes Multimedia Accessibility FAQ]<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-captions.html Captions] Understanding Success Criteria 1.2.2 for WCAG 2.0 (Level A)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-audio-desc.html Audio Description or Media Alternative] Understanding Success Criteria 1.2.3 for WCAG 2.0 (Level A)<br />
<br />
<br /><br />
<hr /><br />
<br />
===<span style="color:#808080;">EOWG Notes on Multimedia</span>===<br />
<br />
* Generally, we aren't addressing the levels; however, this one is complicated. [http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv.html Time-based Media: Understanding Guideline 1.2] has 9 success criteria, including A, AA, AAA -- eek! Ideas on how to address this? <span style="color:#808080;">{Shawn}</span><br />
** comment <span style="color:#808080;">{name}</span><br />
<br />
* vision and hearing needed for checks:<br />
** To check if there are captions, need to be able to see. [visual]<br />
** To check if the captions are synched, need to be able to hear. [auditory]<br />
** To check if audio description is provided, need to be able to see? hear?<br />
** other?<br />
* [OPEN - add back in] Auto play - it is easy to test whether the audio starts automatically. <span style="color:#808080;">{Suzette}</span><br />
* Audio contrast - mightn't be able to say yes/no, but might be able to say 'could be a problem' <span style="color:#808080;">{Andrew}</span><br />
* Order of alternatives - I'd suggest Transcripts ahead of Audio Description as easier to check for and much more common <span style="color:#808080;">{Andrew}</span><br />
* comment <span style="color:#808080;">{name}</span><br />
<br />
<hr /><br />
<br /><br />
<br />
[[#Contents|back to contents]]<br />
<br />
==Forms, form labels, and error messages==<br />
<br />
[15: maybe not]<br />
<br />
<span style="color:#808080;">EOWG notes.<br />
<br/> 5min: no, too complicated.<br />
<br /> 15min: not sure</span><br />
<br />
Forms are everywhere on the web and successful user interaction relies on clear, understandable, and accessible form controls. Even simple forms like log-in and search boxes can be problematic if not properly built. Some critical elements that can affect screen reader users are much easier to detect using an automatic tool to check the HTML and CSS, or within a user trial with an experienced screen reader user. <br />
<br />
Review previous keyboard access checks to ensure that visible, logical access to form inputs is provided for those who don't use a mouse. Review text alternatives checks to ensure proper identification of any graphic buttons or other inputs. <br />
<br />
Forms are complex and will likely require more in-depth assessment. In the meantime, these easy visual checks will help you identify some common problems. <br />
<br />
====Are there any forms====<br />
Check through the web pages to look for examples of forms.<br />
<br />
What to look for: <br />
* Forms include registration forms, contact forms, booking and purchase details which include text entry fields, radio buttons, dropdown boxes and submit buttons and also single text entry boxes such as login or search box.<br />
<br />
====Visually examine the instructions for the form and input fields====<br />
Check over each form.<br />
<br />
What to look for: <br />
* Are there text instructions at the beginning of the form including if any elements are essential?<br />
* Are there text labels (before/after?) the input fields that describe what to do and if any elements are essential<br />
<br />
====Form labels====<br />
Use your mouse to check for labels explicitly tied to the form fields by clicking on the label - look to see if the cursor now appears in the associated text entry box or if the associated radio-button or check-box becomes selected.<br />
<br />
You can also use a browser based testing tool to check the code for labels, the most reliable method for the provision of accessible forms. <br />
<br />
What to look for:<br />
* In FF Toolbar > Navigation > Forms. <br />[Keyboard - Alt + 'T' for "'''T'''ools", then 'W' for "'''W'''eb Developer Extension", then 'F' for '''F'''orms, then 'O' for '''O'''utline Form Fields Without Labels] <br />
** Verify that each form has a unique associated label <br />
* In IE/WAT > Structure > FieldSet/Labels <br />[Keyboard - Ctrl + Alt + 6 for "Structure", then arrow down to "FieldSet/Labels" and select]<br />
** Verify that form has a unique associated label<br />
<br />
If forms are not provided in this conventional way, mark the form for further testing in the next, more comprehensive round.<br />
<br />
====Keyboard access and reading order====<br />
Use the Tab key and arrow keys to move through form controls, text boxes, radio buttons, drop down box and submit button. (Use shift tab to go back). Use the cursor (arrow) keys to access selection box or drop-down menu content.<br />
<br />
What to look for:<br />
* Compare the sequence of information presented visually with the tab through order.<br />
* Follow instructions to check for equivalent Keyboard Access in previous section.<br />
<br />
====Data input and error messages====<br />
Enter correct and incorrect data – eg incorrectly formatted telephone numbers and email addresses.<br />
<br />
What to look for:<br />
When erroneous data is entered and form submitted: <br />
* Ensure that error message is clear and specific about the nature of the error and the field in which it was made <br />
* Ensure that focus moves to the error message <br />
* Ensure that guidance is provided to help user understand and fix the error.<br />
<br />
===References===<br />
<p>Several Accessibility Principles are relevant to the accessibility of forms, including those reviewed in the checks for Keyboard Access and Text alternatives. Also consider these:<br />
* Labels for form controls, input, and other user interface components must be provided. (Labels and Instructions 3.3.2 A)<br />
* Error correction: Forms may be confusing or difficult to use for many people, and, as a result, they may need more time and be more likely to make mistakes. Clear recovery mechanisms must be provided. (Error identification 3.3.1 A, Error suggestion 3.3.3.AA, Error prevention (legal, financial, data) 3.3.4 AA. Timing 2.2.1 A)<br />
<br />
<p>WAI's Before and After Demo (BAD)includes examples of forms that have been made accessible:<br />
* [http://www.w3.org/WAI/demos/bad/before/survey.html Inaccessible forms page]<br />
* [http://www.w3.org/WAI/demos/bad/after/survey.html Accessible forms page]<br />
<br />
==Next Steps==<br />
<br />
So, you've spent a little time getting a sense of the accessibility issues that need to be addressed, but what do you do next? How can you flag what you've discovered, while being sure that the information reaches those who can make the changes happen?<br />
<br />
If you're a site visitor who doesn't work for the organization but wants to report accessibility-related concerns, you will likely want to reach out by using the site's contact form or by sending email to a "Webmaster" address. Of course, if you have a specific point of contact in the organization, starting with that person can be beneificial. <br />
<br />
On the other hand, if you work for the organization that operates the site you've looked at, you might use a bug-tracking/helpdesk system to report your findings. Or you might decide it would be more effective to write a report in which you group problems and possible solutions in a way that makes sense within the company's structure.<br />
<br />
Whether or not you work for the company that runs the site you've checked, you'll want to describe the issues clearly, including identifying the browser and any other tools you used. Providing as much detail as you can will help others replicate the issue and identify approaches to resolve it. For examples of recommendations we have developed to guide site visitors who experience difficulty accessing a web site, see a section of [ http://www.w3.org/WAI/users/inaccessible Contacting Organizations about Inaccessible Websites] called [http://www.w3.org/WAI/users/inaccessible#report "Describe the Problem]." These [http://www.w3.org/WAI/users/inaccessible#pointers Sources for More Information] will help your colleagues familiarize themselves with additional references for more details about problems and solutions.<br />
<br />
When it's time to conduct a more thorough evaluation,either internally or by hiring a qualified contractor, the [WCAG-EM Evaluation Methodology Overview] (coming soon) and accompanying documents will help you or others develop plans as we all work together to provide a more accessible web for all.<br />
<br />
===<span style="color:#808080;">EOWG Notes on Next Steps</span>===<br />
<div style="color:#808080;"><br />
<br />
* comment {name}<br />
<br />
</div><br />
<br /><br />
<hr/><br />
<br />
=Contributors=<br />
Thanks to:<br />
* Those who edited in December and January: Suzette (forms, @@), Sharron (Intro, @@), Shawn (Intro, page titles, headings, alt text), Ian (zoom n text resize).<br />
* Those who commented in December and January: Sylvie, Wayne, Anna Belle, ...<br />
* Those who drafted checks 16-28 November:<br />
** Sharron for drafting {list sections!}<br />
** Suzette for drafting : Check usable with page zoomed and text enlarged, Check color contrast, Check color coding and shape coding, {?other sections}<br />
** Wayne for drafting {list sections!}<br />
* Andrew & Shawn for editing the [http://www.w3.org/WAI/EO/wiki/Web_Accessibility_Preliminary_Evaluation#Check_keyboard_access_and_visual_focus_.5Bmostly_drafted.5D keyboard access & visual focus section] in early Nov.<br />
* Ian, Suzette, Vicki, Sylvie, Helle, Shawn for working on an early draft at the [http://www.w3.org/2012/11/02-eo-minutes f2f in Nov].<br />
* Sharron for help making all the early drafts and versions less confusing.<br />
* Wayne and Ian for sharing colleagues' related work.<br />
* Denis for edits to the old page content.<br />
<br />
testing image: http://www.w3.org/WAI/images/search-icon.png<br />
<br />
<br /><hr /><br />
<span style="background:yellow;">'''''Important Note''''': For this draft we have some tool-specific guidance. However, there are potential issues with vendor-neutraility and we might need to address this a different way &mdash; for example, moving tool-specific guidance to WebPlatform Docs or the WAI-Engage wiki where people can easily add other tools.</span></div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Web_Accessibility_Preliminary_Evaluation&diff=3577Web Accessibility Preliminary Evaluation2013-02-08T05:14:55Z<p>Jsutton2: /* Next Steps */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]] > [[Main_Page#Evaluation_pages | Evaluation Pages ]]<br/><br />
Old page on WAI website: [http://www.w3.org/WAI/eval/preliminary.html Prelim Eval]<br/><br />
<br />
=Notes=<br />
* '''For tasks, example use cases with audience, and focus for this and related documents, see the [[Eval Analysis]] page, including the table at the top and the specific [http://www.w3.org/WAI/EO/wiki/Eval_Analysis#Preliminary_Evaluation_Analysis Analysis] section at the bottom'''<br />
* A template for the check items is at the top of the [http://www.w3.org/WAI/EO/wiki/Talk:Web_Accessibility_Preliminary_Evaluation discussion tab].<br />
* For previous drafts and contributed material, see:<br />
** '''[[Prelim Eval 2013-Feb-01]] - snapshot of draft on 1 February 2013 before edits'''<br />
** '''[[Prelim Eval 2013-Jan-24]] - snapshot of draft on 24 January 2013'''<br />
** '''[[Prelim Eval 2013-Jan-17]] - snapshot of draft on 17 January 2013'''<br />
** Extensive revisions and suggestions at [[Archived_Work_on_PreLimEval]] ([http://www.w3.org/WAI/EO/wiki/Archived_Work_on_PreLimEval#Check_link_text_.5B15:_probably_not.5D_.5Bpartly_drafted.5D Links section])<br />
** From Wayne & Tom [[Prelim Eval input: Smart analysis simplified]]<br />
** Old page with Denis' edits and Ian's input in [[Preliminary Eval - old notes]]<br />
<br />
__NOTOC__<br />
<br />
<span style="background:yellow;">'''''Important Note''''': For this draft we have some tool-specific guidance. However, there are potential issues with vendor-neutraility and we might need to address this a different way &mdash; for example, moving tool-specific guidance to WebPlatform Docs or the WAI-Engage wiki where people can easily add other tools.</span><br />
<br />
= Easy Checks - A First Look at Web Accessibility=<br />
[http://www.w3.org/WAI/EO/wiki/Eval_Analysis#Title_ideas title ideas]<br />
<br />
==Contents==<br />
* [[#Introduction]] - updated 1 Feb<br />
* [[#Check page title]] - updated 7 Feb<br />
* [[#Check image text alternatives ("alt text")]] - updated 4 Feb<br />
* [[#Check headings]] - updated 4 Feb<br />
* [[#Check keyboard access, labels, content order, visual focus]] - '''Sharron & Suzette updating'''<br />
* [[#Check color contrast]] - '''Anna Belle & Sharron updating'''<br />
* [[#Check multimedia (video, audio) alternatives]] - updated 7 February<br />
* [[#Check forms]] - '''Suzette & Sharron''' considering if most moves to keyboard access, etc. section and what if anything is left here.<br />
* [[#Check zoom and text enlarge]] ? - '''Ian updating''' - updated 30 Jan<br />
* [[#Next Steps]] - '''Jennifer''' drafting<br />
<br />
''<span style="color:#808080;">[Thanks to [[#Contributors]]!]</span>''<br />
<br />
==Introduction==<br />
<span style="color: #808080;">''[Updated 1 February]''</span><br />
<br />
<p>These easy checks guide non-experts to gauge the accessibility temperature of a web page. With these few simple steps, you can get an idea whether or not accessibility is addressed in even the most basic way. </p><br />
<br />
<p>These checks cover just a few accessibility issues and are designed to be quick and easy, rather than definitive. A web page could seem to pass these checks, yet still have accessibility barriers. More robust evaluation would be needed to check all issues comprehensively.</p><br />
<br />
===Using this page===<br />
<br />
====Tools====<br />
<br />
'''Most of these checks you can do with any browser, that is, you do ''not'' need to download anything.'''<br />
<br />
However, some checks are easier if you can download tools. To keep it simple, we've included instructions for just two tools - the Web Developer Toolbar for Firefox ("FF Toolbar") and the Web Accessibility Toolbar for IE ("IE WAT"). Both are free extensions/add-ons available in different languages.<br />
* FF Toolbar - To do the checks that are indicated "with FF Toolbar", you'll need the [http://www.mozilla.org/en-US/firefox/new/ Firefox browser] and the [https://addons.mozilla.org/en-US/firefox/addon/web-developer/ Web Developer extension]/add-on.<br />
* WAT for IE - To do the checks that are indicated "with IE WAT", you'll need the [http://windows.microsoft.com/en-US/internet-explorer/downloads/ie-9/worldwide-languages Internet Explorer (IE) browser] and the [http://paciellogroup.com/resources/wat/ie Web Accessibility Toolbar].<br />
<br />
Note that we're not endorsing these tools over others. There are other useful [http://www.w3.org/WAI/eval/selectingtools tools to help with evaluation].<br />
<br />
To learn how to do these checks with other tools, see [TBD either Web Platform Docs -or- WAI-Engage wiki].<br />
<br />
''(If you can't download these tools, that's OK; you can still do the checks indicated "with any browser".)''<br />
<br />
====WCAG Links====<br />
These checks are based on the Web Content Accessibility Guidelines ([http://www.w3.org/WAI/intro/wcag WCAG]) 2.0. The main points in WCAG are called "Success Criteria". In the "Learn more from|References" sections of this page, there are links to pages that explain the relevant success criteria in the "Understanding WCAG 2.0" document. <br />
<br />
====Visual and Non-Visual Checks====<br />
<br />
Some checks require you to be able to see the visual rendering of the page. These are marked ''[visual]''. We've indicated checks that do not require seeing the page with ''[non-visual]''.<br />
<br />
====Practicing with BAD, the Before-After Demo====<br />
<br />
<p>The [http://www.w3.org/WAI/demos/bad/ Before and After Demonstration (BAD)] from W3C WAI shows an inaccessible website and a retrofitted version of this same website with the accessibility barriers fixed. You can use the BAD pages to learn how to do these checks. <span style="color:#808080;">[@@ maybe delete the next sentences if we have the instructions in each section] For example, first, do the check on an accessible version of a page to see what it should look like. Then, do the check on the corresponding inaccessible page to see what it looks like when there are accessibility barriers.[@@end delete]</span></p><br />
<br />
===Little Background===<br />
<br />
These checks are designed for anyone who knows how to use websites. You don't need much knowledge or skill. There are a couple things to know that will help you understand the explanations in the checks:<br />
* ''Screen readers'' read aloud the information in a web page. They are used by people who are blind and by some people with reading disabilities.<br />
* Some people use ''voice input'' instead of a keyboard and mouse. For example, ...@@<br />
* [@@anything else needed?]<br />
<br />
If you want to learn more, see:<br />
* [http://www.w3.org/WAI/intro/people-use-web/ How People with Disabilities Use the Web]<br />
* [http://www.w3.org/standards/webdesign/accessibility Introduction to Accessibility]<br />
* [http://www.w3.org/WAI/yourWAI Other WAI resources]<br />
<br />
<br /><br />
<hr /><br />
<br />
===<span style="color: #808080;">EOWG Comments on the Introduction</span>===<br />
<span style="color: #808080;">[previous wording drafts: [http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Feb-01#Introduction 1 Feb], [http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Jan-24#Introduction 23/24 January version],&nbsp; [http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Jan-17#Intro_text_before_editing_23_January 22 January],&nbsp; [http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Jan-17#Introduction 17 January].]</span><br />
<br />
* <span style="color: #808080;">[done] this introduction is very clear. In the paragraph on FF toolbar, what about indicating that this tool is not only free but also available in many languages? {Sylvie}</span><br />
* <span style="color: #808080;">[done] It is not clear to me if the section about using bad should be deleted or not. If it remains, what about telling the reader that it comes from wai and giving the link to it? {Sylvie} </span><br />
* <span style="color: #808080;">@@ comment {name}</span><br />
<br />
<br /><br />
<hr /><br />
<br /><br />
<br />
==Check page title==<br />
<br />
<span style="color:#808080;">''[updated 7 February]''</span><br />
<br />
[image: top of browser showing full title of current page, and multiple page tabs showing truncated titles. AND page title in window title bar at the top]<br />
<br />
Good page titles are particularly useful when people have multiple web pages open at the same time. The first part of the title is shown in browser tabs, as in the above image. Titles are also used for bookmarks/favorites and in search engine results. The first thing screen readers say when the user goes to a different web page is the page title. Page titles are important for orientation &mdash; to help users know where they are and move between pages.<br />
<br />
===What to do===<br />
# If possible, use a browser that displays the page title in the window title bar, like this: <span style="color:#808080;">[image]</span>. <br />Most browsers have a window title bar by default, except Chrome and IE @@#. In those browsers, and most others, you can see the full page title by hovering over the tab, like this: <span style="color:#808080;">[image]</span>. [@@keyboard way to do this?] <br />
# Look at the page's title (or with a screen reader, listen to it).<br />
# Look at titles of other pages within the website.<br />
<br />
===What to check for===<br />
<br />
* Check that there is a title that adequately and briefly describes the content of the page.<br />
* Check that the title is different from other pages on the website, and adequately distinguishes the page from other web pages.<br />
<br />
====Tips====<br />
* There is flexibility on what makes a good page title. Some guidance is linked from the [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html#navigation-mechanisms-title-resources-head Related Resources section of Understanding Success Criteria 2.4.2].<br />
* Titles should be "front-loaded", meaning the important and unique identifying information is first.<br />
* A common mistake is to put the website name first and then the specific page title, for example:<br />
** Poor titles:<br />
*** Acme Web Solutions, Inc. - About Us<br />
*** Acme Web Solutions, Inc. - Contact Us<br />
*** Acme Web Solutions, Inc. - History<br />
** Better page titles:<br />
*** About Acme Web Solutions<br />
*** Contact Acme Web Solutions<br />
*** History of Acme Web Solutions<br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To check page title <em>- with IE WAT:</em></strong>===<br />
<ol><br />
<li>Open the web page you are checking.</li><br />
<li>In the toolbar, select "Structure", then "Heading structure". Or, with the keyboard: [@@keyboard shortcut]<br /><br />
''A new page opens.''</li><br />
<li>The page title is shown after "Title:".</li><br />
</ol><br />
<br />
===Learn more about page titles from:===<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html Page Titled ]- Understanding Success Criteria 2.4.2 for WCAG 2.0 (Level A)<br />
<br />
<br /><br />
<hr /><br />
<br />
===<span style="color:#808080;">EOWG Notes on Page Title</span>===<br />
<br />
* This section really boggles my mind. It is visually so complex about a seemingly straight forward question - does the page have a title that clearly and succinctly describes its content and purpose? is there a compelling need for bracketed [non-visual] designation? It seems to me to be confusing and distracting. Might this be a case where the nested lists of what makes a good page title is also too much information for an Easy Check, since making those judgement calls result in a check that is less "easy"? <span style="color:#808080;">{Sharron}</span><br />[reply - I added specific questions for 8 Feb agenda & removed the brackets & deleted 2 tips <span style="color:#808080;">{Shawn}</span>]<br />
<br />
* The bracketed [non-visual] is confusing e.g. the instructions state "Look" and the title indicates "non-visual". I would remove the square bracketed bits in the title. The "Tips" part is well explained. Perhaps, expand on IE WAT. For beginners, they may not understand what "WAT" is. <span style="color:#808080;">{Vicki}</span><br/>[reply: IE WAT is explained in the intro. since we'll probably use it and FF Toolbar repeatedly, probably don't want to explain them each time <span style="color:#808080;">{Shawn}</span><br />
<br />
* I deleted two tips: <span style="color:#808080;">{shawn}</span><br />
** "Consider how the page title will be used in context; for example, the title of a page in the middle of a multi-step process probably does not need the website name in the title.<br />
** <em>In HTML:</em> The page title is near the top of the web page markup ("code"), in the &lt;head&gt; area. It looks like this in markup: <code>&lt;title&gt;Acme Web Solutions home page&lt;/title&gt;</code><br />
<br />
* I deleted the BAD Example because 1. you don't really need to see an example of how to check this. 2. The good titles aren't totally frontloaded like our tips. <span style="color:#808080;">{shawn}</span><br />It was: In [http://www.w3.org/WAI/demos/bad/ BAD], all of the inaccessible pages have the title "Welcome to CityLights!" (plus a description in brackets that is necessary for people using them demo). The page titles are not unique. Whereas, the accessible pages are titled: Welcome to CityLights!, Citylights News, Citylights Tickets, and Citylights Survey.<br />
* ...comment <span style="color:#808080;">{name}</span><br />
<br />
<hr /><br />
<br /><br />
<br />
==Check image text alternatives ("alt text")==<br />
<span style="color:#808080;">''[updated 4 February]''</span><br />
<br />
<p>Text alternatives (&quot;alt text&quot;) convey the purpose of an image. They are used by people who cannot see the image. (For example, people who are blind and use screen readers can hear the alt text read out; people who have turned off images to speed download or save bandwidth can see the alt text.)</p><br />
<p>The text should be functional and provide an equivalent user experience, not necessarily describe the image. (For example, appropriate text alternative for a search button (<span style="color:#808080;">[/WAI/images/search-icon.png]</span>) would be &quot;search&quot;, not &quot;magnifying glass&quot;.)</p><br />
<br />
<p>Alt text is in the web page markup ("code"); you don't usually see it in the browser. Every image should have alt defined. If an image conveys information useful for interacting with or understanding the web page content, then it needs alt text. If an image is just decorative and people don't need to know about the image, it should have null alt (which looks like this in the markup: <code>alt=&quot;&quot;</code> with no space between the quotes).</p><br />
<br />
<p>Automated tests can tell you if alt text is missing. To determine if the alt text is appropriate, you need to see the image and judge it in context.</p><br />
<br />
<strong>What to check for:</strong><br />
* Every image has appropriate alternative text.<br />
<br />
===<strong>Tips:</strong>===<br />
<p>Appropriate alt text is not an exact science. Some people prefer more description of more images; and others prefer less description.</p><br />
<ul><br />
<li style="padding-bottom:0.5em;">Appropriate alt text:<br />
<ul><br />
<li style="padding-bottom:0.5em;">The text needs to convey the same meaning as the image. That is, if someone cannot see the image, they get the important information from the image in the alt text.</li><br />
<li style="padding-bottom:0.5em;">Alt text depends on content. For example, for an image of a dog on a kennel club website, the alt text might include the breed of the dog; however, the same image on a dog park website may be there just to make the page more attractive, and the image might not need any alt text (null alt explained below). <span style="color:#808080;">[@@ new sentence:]</span> One way to help think about appropriate alt text is: if you were helping someone read and interact with the web page and they cannot see it, what would you say about the image?</li><br />
<li style="padding-bottom:0.5em;">Images that are functional &mdash; for example, images that initiate actions (like submit buttons) and linked images (like in navigation) &mdash; need alt text that is the functional equivalent.</li><br />
<li style="padding-bottom:0.5em;">If there is text in the image &mdash; for example, in a logo &mdash; that text needs to be included in the alt text.<br /><br />
</li><br />
<li style="padding-bottom:0.5em;">If the image has complex information &mdash; such as charts or graphs &mdash; the image should have a short alt text, and then the detailed description of the information should be provided elsewhere.</li><br />
</ul><br />
</li><br />
<li style="padding-bottom:0.5em;">What's not needed in alt text:<br />
<ul><br />
<li style="padding-bottom:0.5em;">If the image is not important for understanding the content &mdash; for example, it is just decoration or &quot;eye candy&quot; &mdash; it should have null alt (<code>alt=&quot;&quot;</code>). <span style="color:#808080;">[@@ new sentence:]</span> One way to help determine if an image should have null alt is to ask yourself: if the image was removed, would the user still get all the information from the page?</li><br />
<li style="padding-bottom:0.5em;">If the image is sufficiently described in the text &mdash; for example, a simple diagram illustrating what's written in the web page text &mdash; it does not need additional alt text. <span style="color:#808080;">[@@ suggest null or &quot;illustration described in main text&quot; or other?]</span></li><br />
<li style="padding-bottom:0.5em;">The alt text does not need to include the words &quot;button&quot;, &quot;link&quot;, or &quot;image of&quot;. <span style="color:#808080;">[@@suzette: because the screen reader will indicate this automatically. shawn: too screen reader focused? what about others not seeing images?]</span></li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<p><em>In HTML:</em> Alt is an attribute of the image tag, and other tags. (So "alt tag" is technically incorrect; it's "alt attribute", or you can say "alt text".) It looks like this in markup: <code>&lt;img alt=&quot;WAI logo&quot; src=&quot;/wai/logo.png&quot;&gt;</code></p><br />
<br />
<p><em>There are three options for checks listed below. The first one is easiest of you have the WAT toolbar. If you don't have any toolbars, there is a check at the end for any browser.</em></p><br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To check alt text <em>- with WAT:</em></strong><em> [non-visual & visual]</em>===<br />
<ol><br />
<li>Open the web page you are checking.</li><br />
<li>In the toolbar, select "Images", then "Toggle Img/Alt". <span style="color:#808080;">[image][@@AnnaBelle- I don't see "Toggle Img/Alt", but rather "Show Images"]</span> Or, with the keyboard: [@@keyboard shortcut]<br /><br />
''If there are any images missing alt, a dialog box appears with the number of images without alt attributes.''<br /><br />
''The alt text will be displayed before the images in quotes on a tan background.''</li><br />
<li>To check for missing alt: Look for the text "NoAlt!" (visually, or with find-in-page). If you find it, that means the following image is missing alt.</li><br />
<li>To check if alt text is appropriate: <em>[visual]</em><br /><br />
For each image, see if the alt text adequately conveys the information in the image it is next to, per the Tips below.</li><br />
</ol><br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To check if alt text is appropriate <em>- with FF toolbar:</em></strong><em> [visual]</em>===<br />
<ol><br />
<li>Open the web page you are checking.</li><br />
<li>In the toolbar, select "Images", then "Display Alt Attributes". <span style="color:#808080;">[image]</span> Or, with the keyboard: [@@keyboard shortcut]<br /><br />
''The alt text will be displayed before the images as white letters on a red background.''</li><br />
<li>For each image, see if the alt text adequately conveys the information in the image it is next to, per the Tips below.</li><br />
</ol><br />
<br />
With the FF Toolbar, there is no explicit indication if images are missing alt, so you probably want to do one of the other checks if you want to catch all missing alt. <span style="color:#808080;">[@@ '''OPEN''': is this true? if so, this sentence could use editing. OR should we just leave this FF check out all together?]</span><br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To check if alt text <em>- with any browser</em></strong><em>: [non-visual & visual]</em>===<br />
<ol><br />
<li>Open [http://wave.webaim.org/ WAVE] web accessibility evaluation tool.</li><br />
<li>Type the website address in the box after &quot;Enter the URL of the web site you want to evaluate:&quot;</li><br />
<li>Click the &quot;WAVE this page!&quot; button.<br /><br />
''Your web page will show up in the browser with lots of little icons on it.''</li><br />
<li>To check for missing alt: Look for the red icon <span style="color:#808080;">[image]</span>, or search for the alt text "ERROR: Missing alt text". If you find it, that means the following image is missing alt.</li><br />
<li>To check if alt text is appropriate: <em>[visual]</em><br />Look for the green alt icon <span style="color:#808080;">[image]</span>. Next to it is text on a light blue background; the alt text is inbetween the asterisks (*). See if that text adequately conveys the information in the image it is next to, per the Tips below.</li><br />
</ol><br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To try checking the alt text in BAD:</strong>===<br />
<br />
<p>With one of the checks above, use the inaccessible home page <code>www.w3.org/WAI/demos/bad/before/home</code> Notice:<br />
<ul><br />
<li>Missing alt:<br />
<ul><br />
<li>There are lots of images without alt text. (Many of these are just decorative and should have null alt text, per the Tips above.)</li><br />
<li>The weather image of the cloud and sun is missing alt.</li><br />
</ul><br />
</li><br />
<li>Inappropriate alt text:<br />
<ul><br />
<li>Near the top, left, see the long alt text starting with "Red dot with...". That description is way too detailed and includes unimportant information. The appropriate alt text in the accessible page is: "Citylights: your access to the city."</li><br />
<li>Near the bottom in the middle, see the image of text: &quot;(1)269C-H-O-K-E&quot;. The alt is 123456789, which is not equivalent.</li><br />
</ul><br />
</li><br />
<li>Appropriate alt text:<br />
<ul><br />
<li>Near the top, see the W3C image; the alt text is: "W3C logo".</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
===<strong>Learn more from:</strong>===<br />
<ul><br />
<li>[http://www.w3.org/WAI/intro/people-use-web/principles#alternatives Text alternatives for non-text content] is an easy introduction with links to more details</li><br />
<li>[http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html Non-text Content] - Understanding Success Criteria 1.1.1 for WCAG 2.0 (Level A)</li><br />
</ul><br />
<br />
<br/><br />
<hr/><br />
<br />
===<span style="color:#808080;">EOWG Notes on alt text</span>===<br />
<br />
<div style="color:#808080;"><br />
<br />
* <span style="background:yellow">[OPEN]</span>The alt text decision tree gives clear guidance on deciding what type of alt text to add. Could it be referenced? http://dev.w3.org/html5/alt-techniques/#tree {Vicki}<br />[reply: not really until it's published, but that might happen soon. <span style="background:yellow">@@EOWG: thoughts on pros and cons of linking over to it?:</span><br />
**...<br />
<br />
* [done] If an image conveys information useful for interacting with or understanding the web page content, then it needs alt text. If an image is just decorative and people don't need to know about the image, it should have null alt (which looks like this in the markup: <code>alt=&quot;&quot;</code>). [@@ maybe, add (no space between the inverted commas) {Vicki}].<br />
<br />
[Previous comments archived in [http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Feb-01#EOWG_Notes_on_alt_text 1 Feb snapshot] ]<br />
<br />
</div><br />
<br/><br />
<hr/><br />
<br />
==Check headings==<br />
<span style="color:#808080;">''[updated 4 Feb]''</span><br />
<br />
Web pages often have sections of information separated by visual headings, for example, heading text is bigger and bold (like "Check headings" right above this sentence :-). To make these work for all users, the headings need to be "marked up" in the web page "code" (e.g., HTML). That way people can navigate to the headings &mdash; including people who cannot use a mouse and use only the keyboard, and people who use a screen reader.<br />
<br />
Heading levels should have a meaningful hierarchy, e.g.:<br />
<ul><br />
<li>Heading Level 1 &lt;h1&gt;<br />
<ul><br />
<li>Heading Level 2 &lt;h2&gt;<br />
<ul><br />
<li>Heading Level 3 &lt;h3&gt;</li><br />
<li>Heading Level 3 &lt;h3&gt;</li><br />
</ul><br />
</li><br />
<li>Heading Level 2 &lt;h2&gt;<br />
<ul><br />
<li>Heading Level 3 &lt;h3&gt;<br />
<ul><br />
<li>Heading Level 4 &lt;h4&gt;</li><br />
<li>Heading Level 4 &lt;h4&gt;</li><br />
</ul><br />
</li><br />
</ul><br />
</li><br />
<li>Heading Level 2 &lt;h2&gt; </li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<br />
<strong>What to check for:</strong><br />
<ul><br />
<li>Are there headings marked up?</li><br />
<li>Is the hierarchy meaningful? (Ideally the page starts with an "h1" &mdash; which is usually similar to the page title &mdash; and does not skip levels; however, this is not an absolute requirement.)</li><br />
<li>Is there text that looks like headings but is not marked up as a heading?</li><br />
<li>Is there text that is marked up as headings that is not really a section heading?</li><br />
</ul><br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To check headings outline <em>- with IE WAT:</em> </strong><em>[non-visual & visual]</em>===<br />
<ol><br />
<li>Open the web page you are checking.</li><br />
<li>In the toolbar, select "Structure", then "Heading Structure". Or, with the keyboard: [@@keyboard shortcut]<br /><br />
''A new page opens with the outline.''</li><br />
<li>Non-visual checks:<br />
<ul><br />
<li>Are headings listed. If there are no headings marked up, it will say "0 headings".</li><br />
<li>Does the outline start with [H1] and follow a meaningful hierarchy? (That's not required, but strongly suggested.)</li><br />
</ul><br />
</li><br />
<li>Visual checks: Compare the Document Outline to the visual rendering of the page.<br />
<ul><br />
<li>Are the things that look like headings on the page listed in the Document Outline?</li><br />
<li>Are there things in the Document Outline that aren't really headings? </li><br />
</ul><br />
</li><br />
</ol><br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To check headings outline <em>- with FF toolbar:</em> </strong><em>[non-visual & visual]</em>===<br />
<ol><br />
<li>Open the web page you are checking.</li><br />
<li>In the toolbar, select "Information", then "View Document Outline". <span style="color:#808080;">[image]</span> Or, with the keyboard: [@@keyboard shortcut]<br /><br />
''A new page opens with the outline''</li><br />
<li>Non-visual checks:<br />
<ul><br />
<li>Are headings listed. If there are no headings marked up, it will say "0 headings".</li><br />
<li>Does the outline start with [H1] and follow a meaningful hierarchy? (That's not required, but strongly suggested.)</li><br />
</ul><br />
</li><br />
<li>Visual checks: Compare the Document Outline to the visual rendering of the page.<br />
<ul><br />
<li>Are the things that look like headings on the page listed in the Document Outline?</li><br />
<li>Are there things in the Document Outline that aren't really headings? </li><br />
</ul><br />
</li><br />
</ol><br />
<br />
===<strong>To check headings outline <em>- in any browser</em>:</strong> <em>[non-visual & visual]</em>===<br />
<ol><br />
<li>In any browser, open the [http://validator.w3.org/ W3C HTML Validator (The W3C Markup Validation Service)].</li><br />
<li>In the Address field, type the URI (e.g., www.w3.org).</li><br />
<li>Click the More Options link.</li><br />
<li>Select the Outline checkbox.</li><br />
<li>Click the Check button.<br />
<br />''The results page appears (with title starting either [Valid] or [Invalid]).''</li><br />
<li>In the results page, near the top, at the end of the "Jump to:" line, click the Outline text link.</li><br />
<li>Non-visual checks:<br />
<ul><br />
<li>Is there anything there? If there is no text between "Below is an outline for this document, automatically generated from the heading tags (&lt;h1&gt; through &lt;h6&gt;.)" and "If this does not look like a real outline..." it means there are no headings marked up on the page.</li><br />
<li>Does the outline start with [H1] and follow a meaningful hierarchy? (That's not required, but strongly suggested.)</li><br />
</ul><br />
</li><br />
<li>Visual checks: Compare the Document Outline to the visual rendering of the page.<br />
<ul><br />
<li>Are the things that look like headings on the page listed in the Document Outline?</li><br />
<li>Are there things in the Document Outline that aren't really headings? </li><br />
</ul><br />
</li><br />
</ol><br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To show heading markup in the page <em>- with IE WAT:</em> </strong><em>[visual]</em>===<br />
<ol><br />
<li>Open the web page you are checking.</li><br />
<li>In the toolbar, select "Structure", then "Headings". Or, with the keyboard: [@@keyboard shortcut]<br /><br />
''Headings will be surrounded with &lt;h1&gt;, &lt;h2&gt;, etc. icons in purple text on tan background.''</li><span style="color:#808080;">@@perhaps avoid indicating colors. This can change with updates and it's hard to keep track of. The indication of &lt;h1&gt; will certainly remain in future versions.</span><br />
<li>Anything that is a functional heading should have a heading icon before it.</li><br />
<li>Anything that is a '''not''' functional heading should '''not''' have a heading icon before it.</li><br />
</ol><br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To show heading markup in the page <em>- with FF toolbar:</em> </strong><em>[visual]</em>===<br />
<ol><br />
<li>Open the web page you are checking.</li><br />
<li>In the toolbar, select "Outline", then "Show Element Tags Names When Outlining". Or, with the keyboard: [@@keyboard shortcut]<br /></li><br />
<li>In the toolbar, select "Outline", then "Outline Headings". Or, with the keyboard: [@@keyboard shortcut]<br /><br />
''The headings will be outlined and &lt;h1&gt;, &lt;h2&gt;, etc. icons will be before the headings.''</li><br />
<li>Anything that is a functional heading should have a heading icon before it.</li><br />
<li>Anything that is a '''not''' functional heading should '''not''' have a heading icon before it.</li><br />
</ol><br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To show heading markup in the page <em>- with any browser:</em> </strong><em>[visual]</em>===<br />
<ol><br />
<li>Open [http://wave.webaim.org/ WAVE] web accessibility evaluation tool.</li><br />
<li>Type the website address in the box after &quot;Enter the URL of the web site you want to evaluate:&quot;</li><br />
<li>Click the &quot;WAVE this page!&quot; button.<br /><br />
''Your web page will show up in the browser with lots of little icons on it.''</li><br />
<li>Anything that is a functional heading should have a heading icon (<span style="color:#808080;">[image]</span>, <span style="color:#808080;">[image]</span>, ...) before it.</li><br />
<li>Anything that is a '''not''' functional heading should '''not''' have a heading icon before it.</li><br />
</ol><br />
<br />
===<span style="color:#808080;">[+/-]</span> <strong>To try checking headings in BAD:</strong>===<br />
<br />
To check headings outline: <em>[non-visual]</em><br />
<ul><br />
<li>Follow the one of the instructions under "To check headings outline" above and use the accessible News page: <code>www.w3.org/WAI/demos/bad/after/news</code>. Notice there is a nice hierarchical outline.</li><br />
<li>Next, use the inaccessible News page: <code>www.w3.org/WAI/demos/bad/before/news</code>. (In HTML Validator, the "Check" button might now say "Revalidate".) Notice there is just one heading.</li><br />
</ul><br />
<br />
To show heading markup in the page: <em>[visual]</em><br />
<br />
<ul><br />
<br />
<li>Start by visually looking at the [http://www.w3.org/WAI/demos/bad/before/news.html BAD news page]. What looks like headings? ''(Citylights News, Heat wave linked to temperatures, Man Gets Nine Months in Violin Case, ...)''</li><br />
<br />
<li>Next, see how it should look. Follow one of the instructions for "To show heading markup in the page" above on the accessible News page: <code>www.w3.org/WAI/demos/bad/after/home</code>. Notice the headings have icons next to them.</li><br />
<br />
<li>Next, see what it looks like when headings are not marked up. Use the inaccessible News page: <code>www.w3.org/WAI/demos/bad/before/home</code>. Notice there is text that visually looks like headings, but does not have headings icons next to it. (With WAVE, there are yellow icons with "h?" because it thinks these might be headings.)</li><br />
</ul><br />
<br />
===<strong>Learn more about headings from:</strong>===<br />
<ul><br />
<br />
<li>[http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html Info and Relationships] - Understanding Success Criteria 1.3.1 for WCAG 2.0 (Level A)</li><br />
<br />
<li>[http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-descriptive.html Headings and Labels] - Understanding Success Criteria 2.4.6 for WCAG 2.0 (Level AA)</li><br />
<br />
<li>[http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-headings.html Section Headings] - Understanding Success Criteria 2.4.10 for WCAG 2.0 (Level AAA)</li><br />
<br />
<li>Techniques for WCAG 2.0:<br />
<ul><br />
<li>[http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/G130 G130: Providing descriptive headings]</li><br />
<li>[http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/G141 G141: Organizing a page using headings]</li><br />
<li>[http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/H42.html H42: Using h1-h6 to identify headings]</li><br />
<li>[http://www.w3.org/TR/WCAG20-TECHS/H69.html H69: Providing heading elements at the beginning of each section of content]</li><br />
<li>[http://www.w3.org/TR/WCAG20-TECHS/F2.html F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text]</li><br />
<li>[http://www.w3.org/TR/WCAG20-TECHS/F43.html F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content]</li><br />
</ul><br />
</li><br />
<br />
<li><span style="color:#808080;">[@@Do we want to point to a resources that shows how screen reader users navigate with headings? There's not much detail in [http://www.w3.org/WAI/intro/people-use-web/principles accessibility principles] ... ]</span></li><br />
</ul><br />
<br />
<br /><br />
<hr /><br />
<br />
===<span style="color:#808080;">EOWG Notes on Headings</span>===<br />
<br />
* <span style="color:#808080;">comment {name}</span><br />
<br />
<span style="color:#808080;">low priority:</span><br />
<ul><br />
<li style="color:#808080;">do we want to find an appropriate example of text that is marked up as a heading but it not really a heading?</li><br />
* <span style="color:#808080;">Here is one from University of Washington's [http://www.washington.edu/accesscomputing/AU/before.html Accessible University 2.0], fictional pages to teach web accessibility. The Security Check is the only thing marked as a heading. Not sure it fits what we need, and will keep looking. {Sharron}</span><br />
OK, here's a sample, can do in HTML if we have anyplace to put it...[http://www.w3.org/WAI/EO/wiki/Headings_what_not_to_do What not to do for Headings]<br />
<li style="color:#808080;">do we want to find an appropriate example of a web page with no headings at all? to show what you get in the Validator outline?</li><br />
</ul><br />
<br />
<hr /><br />
<br /><br />
<br />
==Check keyboard access, labels, content order, visual focus==<br />
<span style="color:#808080;">EOWG notes - importance: HIGH.<br />
<br/> 5min: maybe.<br />
<br />15min: yes, at least part of it.<br />
<br />Without visual rendering: @@</span><br />
<br />
Many people do not use the mouse and rely on the keyboard to interact with the Web. This requires keyboard access to all functionality, including links, form controls, input, and other user interface components. While screen reader users rely on the keyboard, they are not the only ones. In addition, sighted users with mobility impairments may rely on the keyboard or have assistive technologies that are controlled through keyboard actions. Therefore, key components of effective keyboard access include visible focus indication and a logical tab order.<br />
===What To Do===<br />
* Click in the address bar, then put your mouse aside and don't use it. <br />
* Press the 'tab' key to move around the page.<br />
* Use the keyboard to set the focus to all focusable elements on the page.<br />
===What To Look For===<br />
* Can you tab to all the elements, including links, form fields, buttons, and media player controls? Are there any actions you can't get to (e.g., if they are only available on mouse hover)?<br />
* Does the tab order follow the logical reading order, top to bottom, left to right in sequence?<br />
* Does the focus get stuck anywhere - that is, you can tab into a control but not out? (called a "keyboard trap")?<br />
* Does the order that items get focus make sense to sighted users? (e.g., you don't jump around the page out of order logically)<br />
* Can you tab right through to the bottom of the page and then resume again from the top? (e.g. you don't get stuck anywhere and can't move on)<br />
* If there is a drop-down box (for example, for navigating to a different page): If you tab into the drop-down box, can you use the down/up arrow keys to move through the options, and @@use 'tab' to the following item@@? (Make sure it doesn't automatically select the first item.)<br />
*Visually examine progress through elements and verify that the focus indicator is clearly visible (i.e. you can see where you've 'tabbed' to).<br />
*Common failures occur when the default focus indicator is turned off in CSS or when the element is styled with borders that occlude the focus indicator.<br />
*Verify that any visual changes that occur with mouse hover also are triggered with keyboard focus<br />
<br />
===References===<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#keyboard Functionality is available from a keyboard]<br />
* [http://www.w3.org/WAI/users/browsing#keyboard Browsing the Web by Keyboard] section in [http://www.w3.org/WAI/users/browsing Better Web Browsing: Tips for Customizing Your Computer]<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html Focus Visible - Understanding Success Criteria 2.4.7 (Level A)]<br />
*[http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html Focus Order - Understanding Success Criteria 2.4.3] <br />
* Example: [http://www.w3.org/WAI/demos/bad/before/survey.html web page template that does not enable keyboard access] from the WAI Before and After Demo (BAD)<br />
<br />
===Notes===<br />
* Mac browsers by default only tab through forms, will need to turn on...<br />
* not work easily in Opera...<br />
* ...<br />
<br />
<br /><br />
<hr /><br />
<br />
==Check color contrast==<br />
<br />
''[Anna Belle and Sharron are editing this section. Here is the previous [http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Feb-01#Check_color_contrast 1 February draft of color contrast] with lots of text.]''<br />
<br />
==Check multimedia (video, audio) alternatives==<br />
<span style="color: #808080;">''[Updated 7 February]''</span><br />
<br />
Check multimedia elements to ensure that visual and audio content includes equivalent alternatives and that the media player is fully accessible. <br />
<br />
===What to do===<br />
These steps will give you a quick and easy first look. They will identify that alternatives for media content have been considered and attempted. A more comprehensive testing process will be needed to verify the quality of the alternatives provided. <br />
# Follow the steps for keyboard access to ensure that the media player controls are labeled and operable by all users.<br />
# Play a short piece of the audio content<br />
# Play a short segment of the video content<br />
# Toggle closed captions on (if available) <span style="color:#808080;">{@@ need some guidance on how to do this?}</span><br />
# Toggle audio description on (if available) <span style="color:#808080;">{@@ need some guidance on how to do this?}</span><br />
# If no captions or audio description options are provided, check page for transcript or link to transcript<br />
<br />
===What to look for===<br />
====Captions====<br />
* Are captions provided?<br />
* Are they synchronized to the spoken content? <span style="color:#808080;">{@@ not sure this is necessary for easy check?}</span><br />
* Has important audio content other than dialogue been included? (music, relevant ambient sounds, etc) <span style="color:#808080;">{@@ need to say more and maybe give examples, or is that beyond easy check?}</span><br />
<br />
====Audio Description====<br />
<span style="color:#808080;">{@@ think most people have no idea what this is and we need a brief explanation?}</span><br />
*Is an audio description track provided?<br />
<br />
====Transcript====<br />
* If captions and audio descriptions are not provided, look for a link to a text-based script containing dialogue and other audio content and description of video needed for understanding. <br />
* Check for spelling and accuracy. <span style="color:#808080;">{@@ I think spelling and accuracy is beyond quick check}</span><br />
<br />
===Learn more about providing alternatives for media content===<br />
* [http://www.w3.org/2008/06/video-notes Multimedia Accessibility FAQ]<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-captions.html Captions] Understanding Success Criteria 1.2.2 for WCAG 2.0 (Level A)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-audio-desc.html Audio Description or Media Alternative] Understanding Success Criteria 1.2.3 for WCAG 2.0 (Level A)<br />
<br />
<br /><br />
<hr /><br />
<br />
===<span style="color:#808080;">EOWG Notes on Multimedia</span>===<br />
<br />
* Generally, we aren't addressing the levels; however, this one is complicated. [http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv.html Time-based Media: Understanding Guideline 1.2] has 9 success criteria, including A, AA, AAA -- eek! Ideas on how to address this? <span style="color:#808080;">{Shawn}</span><br />
** comment <span style="color:#808080;">{name}</span><br />
<br />
* vision and hearing needed for checks:<br />
** To check if there are captions, need to be able to see. [visual]<br />
** To check if the captions are synched, need to be able to hear. [auditory]<br />
** To check if audio description is provided, need to be able to see? hear?<br />
** other?<br />
<br />
* comment <span style="color:#808080;">{name}</span><br />
<br />
<hr /><br />
<br /><br />
<br />
==Check forms==<br />
'''SK: see email for update 11pm UK, 23 Jan.'''<br />
<br />
[15: maybe not]<br />
<br />
[drafted, edited, needs review - move keyboard access, visual focus, content order with other section ?Sharron ?Suzette]<br />
<br />
<span style="color:#808080;">EOWG notes.<br />
<br/> 5min: no, too complicated.<br />
<br /> 15min: not sure</span><br />
<br />
''Note: Some aspects will be integrated with keyboard access, visual focus, content order.''<br />
<br />
<p>Forms are everywhere on the web and successful user interaction relies on clear, understandable, and accessible form controls. Several principles of accessibility should be kept in mind when testing forms. Labels for form controls, input, and other user interface components must be provided. Many people do not use the mouse and rely on the keyboard to interact with the Web. This requires visible keyboard access to all functionality, including form controls. Forms may be confusing or difficult to use for many people, and, as a result, they may be more likely to make mistakes. Clear recovery mechanisms must be provided.</p> <br />
<br />
===Forms - simplified===<br />
[Edited by Suzette, is this sufficiently simplified?]<br />
<br />
Note: Some aspects of Forms will be integrated with keyboard access, visual focus, content order. {SK - Also have removed references to colour coding and graphics/non text content and CAPTCHA.} <br />
<br />
Forms are everywhere on the web and successful user interaction relies on clear, understandable, and accessible form controls. Forms are complex and need in depth assessment. <br />
<br />
Some critical elements which can affect screen reader users are much easier to detect using an automatic tool to check the HTML and CSS, or as a user trial with an experienced screen reader user. <br />
<br />
The following visual checks can identify some common problems which are particularly important when testing forms.<br />
<br />
{There 10 Success criteria references are included to help editorial choices – is this too many? SK}<br />
<br />
* Labels for form controls, input, and other user interface components must be provided. (Labels and Instructions 3.3.2 A)<br />
* Keyboard access for people who do not use the mouse and rely on the keyboard to interact with the Web. This requires visible keyboard access to all functionality, including form controls. (Keyboard 2.1.1 A, No keyboard trap 2.1.2 A, Focus visible 2.4.7 AA)<br />
* Information needs to be in a logical order which is followed when tabbing through the input fields. (Meaningful sequence 1.3.2 A, Focus order 2.4.3 A) <br />
* Error correction: Forms may be confusing or difficult to use for many people, and, as a result, they may need more time and be more likely to make mistakes. Clear recovery mechanisms must be provided. (Error identification 3.3.1 A, Error suggestion 3.3.3.AA, Error prevention (legal, financial, data) 3.3.4 AA. Timing 2.2.1 A)<br />
<br />
<br />
<br />
====Are there any forms====<br />
Check through the web pages to look for examples of forms.<br />
<br />
What to look for: <br />
**Forms include registration forms, contact forms, booking and purchase details which include text entry fields, radio buttons, dropdown boxes and submit buttons and also single text entry boxes such as login or search box.<br />
<br />
====Visually examine the instructions for the form and input fields====<br />
Check over each form.<br />
<br />
What to look for: <br />
**Are there text instructions at the beginning of the form including if any elements are essential?<br />
**Are there text labels (before/after?) the input fields that describe what to do and if any elements are essential<br />
**{Exclude? If required fields are indicated by use of color cues, ensure that additional, alternative methods are also used – Use of colour 1.4.1 A)<br />
<br />
====Keyboard access====<br />
Use the Tab key to move through form controls, text boxes, radio buttons, drop down box and submit button. (Use shift tab to go back). Use the cursor (arrow) keys to access selection box content.<br />
<br />
{SK: recommend refering to Keyboard access (above) and delete the rest of this section}<br />
<br />
What to look for:<br />
**Is the focus visible on all form controls, including inputs, submit mechanisms, and check boxes and radio buttons?<br />
**If the form control is a check box or radio button, ensure that focus indication includes form label as well as the actual control (SK –can you do this visually?)<br />
**If the form control is a select box, ensure that arrow keys can move focus between select options and that selection is made by user action and not by default focus. (SK – can you do the second part of this visually?)<br />
<br />
====Logical sequence====<br />
Compare the sequence of information presented visually with the tab through order.<br />
<br />
What to look for:<br />
**Ensure that focus moves logically between the fields. <br />
**Enter correct and false data in form input fields<br />
<br />
{SK: recommend refering to Keyboard access (above)}<br />
<br />
====Use the keyboard to enter data into the text field.====<br />
Enter correct and incorrect data – eg incorrectly formatted telephone numbers and email addresses.<br />
<br />
What to look for:<br />
** Ensure that focus does not automatically advance to the next field, but requires user input to advance (SK – is this easy or advanced, what success criteria?)<br />
** When erroneous data is entered and form submitted: <br />
** Ensure that error message is clear and specific about the nature of the error and the field in which it was made <br />
** Ensure that focus moves to the error message <br />
** Ensure that guidance is provided to help user understand and fix the error.<br />
<br />
{SK: recommend referring to Keyboard access (above) but would suggest keeping this practical suggestion to try filling in the form, especially with correct and incorrect information that will trigger error messages}<br />
<br />
===References===<br />
<p>Several Accessibility Principles are relevant to the accessibility of forms, including these:<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#alternatives Text alternatives to non-text content]<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#keyboard Functionality is available from a keyboard]<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#navigable Users can easily navigate, find content, and determine where they are]<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#predictable Content appears and operates in predictable ways]<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#tolerant Users are helped to avoid and correct mistakes]</p><br />
<p>WCAG2 Guidelines and Success Criteria that may be applied to determining the accessibility of forms include these:<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html Non-text Content]: Understanding Success Criteria 1.1.1 (Level A)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html Keyboard]: Understanding Success Criteria 2.1.1 (Level A)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html Focus Order]: Understanding Success Criteria 2.4.3 (Level A)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-descriptive.html Headings and Labels]: Understanding Success Criteria 2.4.6 (Level AA)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html Visible Focus]: Understanding Success Criteria 2.4.7 (Level AA)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html Predictable]: Understanding Guideline 3.2 (Level A and AA)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error.html Input Assistance]: Understanding Guideline 3.3 (Level A and AA)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html Name, Role, Value]: Understanding Success Criteria 4.1.2 (level A)</p><br />
<br />
<p>WAI's Before and After Demo (BAD)includes examples of forms that have been made accessible:<br />
* [http://www.w3.org/WAI/demos/bad/before/survey.html Inaccessible forms page]<br />
* [http://www.w3.org/WAI/demos/bad/after/survey.html Accessible forms page]<br />
<br />
===Notes===<br />
<span style="color:#808080;">[can be internal notes for now or maybe will be included in final doc]</span><br />
*...<br />
* Is it possible to have a 'first glance' option to identify potential trouble spots and very common problems, which can then be examined in more depth? {Suzette}<br />
* I have noticed some developers having trouble with single fields such as search boxes or login details, or simple little contact forms - perhaps we could expand the opening description to suggest looking for these. It is not just dedicated forms such as membership details, job applications, tax returns, travel booking and shopping etc.{Suzette}<br />
<br />
===Comments 2012-Nov-30===<br />
Shawn: Maybe, a couple of things are easy, some are complex. We could use the nice writeup somewhere else if not used here.<br />
Suzette: I can try and pick the easy bits out of Sharron's content to see if we can get this in.<br />
Shawn: Or add notes on forms to Keyboard Access and Visible Focus sections.<br />
<br />
==Check zoom and text enlarge==<br />
<br />
People with mild to moderate visual impairments may need to enlarge content in order to read it, or read it without straining. This simple requirement is mostly achieved by the functionality of the browser and ensuring that the page design supports that functionality. <br />
<br />
Most browsers offer two ways of enlarging content: page zoom and text resize. Page zoom works by scaling up the page content, so that text, images, and buttons are all increased or decreased in size, and the integrity of the layout is maintained. Text resize only affects text, although implementation techniques can be used to also change the widths and heights of containers, margins, padding, and other aspects of the design.<br />
<br />
Not all browsers offer both choices, and some browsers will not resize text if it has been set using fixed units such as pixels.<br />
<br />
* In browsers that support zoom, increase zoom level to 200% or maximum zoom if smaller than 200%<br />
* In browsers that support text resizing, increase text size to 200% or maximum size if smaller than 200%<br />
<br />
===What to do===<br />
<br />
For each browser to be tested:<br />
<br />
* Set the screen window to full width<br />
* Open your preferred browsers. Internet Explorer, Firefox, Chrome and Opera all offer zoom as a function of View or Function menus, or as a keyboard shortcut (usually, Control +, or for Mac Command +). <br />
* In browsers that support page zoom, enable this option and use the appropriate control to increase zoom level to 200% or maximum zoom. <br />
* In browsers that support text resizing, enable this option and use the appropriate control to increase text size to 200% or maximum size.<br />
<br />
===What you will see===<br />
<br />
* For page zoom layout should remain approximately the same for fixed width designs, and will reflow in the same way as resizing the window would at small sizes.<br />
* For text resize most aspects of the design will not change and layout will probably not increase in size. Content will reflow appropriately within the same available space as text increases in size.<br />
<br />
===What to check for===<br />
<br />
* Text should increase in size in both cases, addionally with page zoom all elements on the page should increase in size.<br />
* No content should overlap.<br />
* All controls must be clickable.<br />
<br />
====Note====<br />
Some browsers can expand the text beyond 200% - this is not covered by the resize requirement as it is recognised that this will cause some of the failures described. It is also accepted that some horizontal scrolling may be necessary but see also 1.4.8 which is a AAA requirement. <br />
Users with more severe visual impairments who need larger text are likely to use screen magnifiers to increase text size above 200%.<br />
<br />
===References===<br />
*link to {appropriate section in Accessibility Requirements page http://www.w3.org/WAI/intro/people-use-web/principles#distinguishable} (doesn’t have a lot to say)<br />
*Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background. <br />
*Resize text: Understanding Success Criteria 1.4.4 (Level AA) {http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html}<br />
*Images of Text: Understanding Success Criteria 1.4.5 (Level AA) http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-text-presentation.html<br />
*Visual Presentation: Understanding Success Criteria 1.4.8 (Level AAA)http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-visual-presentation.html<br />
*link to {BAD example} No specific BAD examples – some reference to Text as image in relation to the phone number, and column width.<br />
<br />
<br /><br />
<hr /><br />
<br />
===<span style="color:#808080;">EOWG notes on zoom and enlarge</span>===<br />
[See [http://lists.w3.org/Archives/Public/w3c-wai-eo/2013JanMar/0010.html e-mail thread on zoom & resize] ]<br />
<br />
<span style="color:#808080;">[done - 1 Feb agreed to include it] We previously thought we wouldn't include this in the easy checks. One of the issues was conflicting perspectives in forums and critiques that 200% is too hard to meet. Ian has re-drafted this section. <br /><br />
Please comment on reasons to include it or not. Feel free to edit the main text as well.</span><br />
<br />
* <span style="color:#808080;">@@comment {name}</span><br />
<br />
* <span style="color:#808080;">@@comment {Vicki} I would include this as it's well explained and sounds simple :) Often, this is a check which is quite difficult to understand but as it's explained quite clearly here, I would include it. One comment: at the end of the first section (just before "What to do"), there are two bullet points on the browsers and zooming. Shouldn't this be removed and left (as currently duplicated) in the "What to do" section?</span><br />
<hr/><br />
<br/><br />
<br />
So, you've spent a little time getting a sense of the accessibility issues that need to be addressed, but what do you do next? How can you flag the problems and solutions, while being sure that the information reaches those who can make the changes happen?<br />
<br />
If you have a bug-tracking/helpdesk system, you might use that. Or you might decide it would be more effective to write a report in which you group problems and solutions in terms of people's roles and responsibilities. [@@ JS: maybe link to WAI-Engage, even though it's in progress?]<br />
<br />
What works best will depend on your circumstances. Regardless, you'll want to describe the issues clearly. For examples of recommendations we have developed to guide site visitors who experience difficulty accessing a web site, see a section of [Contacting Organizations about Inaccessible Websites http://www.w3.org/WAI/users/inaccessible] called [http://www.w3.org/WAI/users/inaccessible#report "Describe the Problem]." In addition, these [http://www.w3.org/WAI/users/inaccessible#pointers Sources for More Information] will help your colleagues familiarize themselves with additional information.<br />
<br />
When you're ready to conduct a more thorough evaluation,either internally or by hiring a qualified contractor, the [WCAG- Evaluation Methodology Overview] (coming soon) and accompanying documents will help you develop your plans as you continue your efforts to provide a more accessible web for all.<br />
<br />
<br />
<br />
<br />
<br />
==Next Steps==<br />
<br />
@@ What to do with what you find -- point to [http://www.w3.org/WAI/users/inaccessible Contacting Organizations about Inaccessible Websites] overall and even if internal reporting, see [http://www.w3.org/WAI/users/inaccessible#report Describe the Problem section]<br />
<br />
@@ Doing more thorough evaluation -- point to WCAG-EM Overview (coming soon)<br />
<br />
<br /><br />
<hr/><br />
==Next Steps==<br />
<br />
=Contributors=<br />
Thanks to:<br />
* Those who edited in December and January: Suzette (forms, @@), Sharron (Intro, @@), Shawn (Intro, page titles, headings, alt text), Ian (zoom n text resize).<br />
* Those who commented in December and January: Sylvie, Wayne, Anna Belle, ...<br />
* Those who drafted checks 16-28 November:<br />
** Sharron for drafting {list sections!}<br />
** Suzette for drafting : Check usable with page zoomed and text enlarged, Check color contrast, Check color coding and shape coding, {?other sections}<br />
** Wayne for drafting {list sections!}<br />
* Andrew & Shawn for editing the [http://www.w3.org/WAI/EO/wiki/Web_Accessibility_Preliminary_Evaluation#Check_keyboard_access_and_visual_focus_.5Bmostly_drafted.5D keyboard access & visual focus section] in early Nov.<br />
* Ian, Suzette, Vicki, Sylvie, Helle, Shawn for working on an early draft at the [http://www.w3.org/2012/11/02-eo-minutes f2f in Nov].<br />
* Sharron for help making all the early drafts and versions less confusing.<br />
* Wayne and Ian for sharing colleagues' related work.<br />
* Denis for edits to the old page content.<br />
<br />
<br /><hr /><br />
<span style="background:yellow;">'''''Important Note''''': For this draft we have some tool-specific guidance. However, there are potential issues with vendor-neutraility and we might need to address this a different way &mdash; for example, moving tool-specific guidance to WebPlatform Docs or the WAI-Engage wiki where people can easily add other tools.</span></div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Web_Accessibility_Preliminary_Evaluation&diff=3134Web Accessibility Preliminary Evaluation2013-01-24T02:12:02Z<p>Jsutton2: /* EOWG Notes on alt text */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]] > [[Main_Page#Evaluation_pages | Evaluation Pages ]]<br/><br />
Old page on WAI website: [http://www.w3.org/WAI/eval/preliminary.html Prelim Eval]<br/><br />
<br />
Note:<br />
* '''For tasks, example use cases with audience, and focus for this and related documents, see the [[Eval Analysis]] page, including the table at the top and the specific [http://www.w3.org/WAI/EO/wiki/Eval_Analysis#Preliminary_Evaluation_Analysis Analysis] section at the bottom'''<br />
* A template for the check items is at the top of the [http://www.w3.org/WAI/EO/wiki/Talk:Web_Accessibility_Preliminary_Evaluation discussion tab].<br />
* For previous drafts and contributed material, see:<br />
** '''[[Prelim Eval 2013-Jan-17]] - snapshot of draft on 17 January 2013'''<br />
** Old page with Denis' edits and Ian's input in [[Preliminary Eval - old notes]]<br />
** Extensive revisions and suggestions at [[Archived_Work_on_PreLimEval]]<br />
** From Wayne & Tom [[Prelim Eval input: Smart analysis simplified]]<br />
<br />
__NOTOC__<br />
<br />
<span style="background:yellow;">'''''Important Note''''': For this draft we have some tool-specific guidance. However, there are potential issues with vendor-neutraility and we might need to address this a different way &mdash; for example, moving tool-specific guidance to WebPlatform Docs or the WAI-Engage wiki where people can easily add other tools.</span><br />
<br />
= Easy Checks - A First Look at Web Accessibility=<br />
[http://www.w3.org/WAI/EO/wiki/Eval_Analysis#Title_ideas title ideas]<br />
<br />
==Contents==<br />
* [[#Introduction]] - updated 23 Jan<br />
* [[#Check image text alternatives ("alt text")]] - updated 23 Jan<br />
* [[#Check headings]] - updated 23 Jan<br />
* [[#Check keyboard access, labels, content order, visual focus]] - '''Sharron & Suzette updating'''<br />
* [[#Check page title]] - updated 23 Jan<br />
* [[#Check color contrast]] - '''NEEDS UPDATING'''<br />
* [[#Check video, sound, (multimedia)]] - '''Sharron updating'''<br />
* [[#Check forms]] - '''Suzette & Sharron''' consider if most moves to keyboard access, etc. section and what if anything is left here<br />
* [Page zoom, text enlarge, window size - '''Ian''' rough drafting to see how it would fit]<br />
* [? Links - some strong reasons not to (including false negatives & positives), but '''Suzette''' really wants :-]<br />
* [[#More Thorough Evaluation]]<br />
* [[#Contributors]]<br />
<br />
==Introduction==<br />
<span style="color: #808080;">[previous wording drafts: [http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Jan-17#Intro_text_before_editing_23_January Intro text from 22 January], [http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Jan-17#Introduction Introduction from 17 January].]</span><br />
<br />
<p>These easy checks guide non-experts to gauge the accessibility of a web page. With these few simple steps, you can get an idea whether or not accessibility was addressed in even the most rudimentary way.</p><br />
<br />
<p>These checks are designed to be quick and easy, rather than definitive. A web page could seem to pass these checks, yet still have accessibility barriers.</p><br />
<br />
<p>These checks cover just a few accessibility issues. More robust evaluation would be needed to check all issues comprehensively. However, these easy checks will give you a good idea if the page has significant accessibility barriers, and find some things that need to be fixed.</p><br />
<br />
===Using this page===<br />
<br />
====Tools====<br />
<br />
Most of these checks you can do with any browser, that is, you do '''not''' need to download anything.<br />
<br />
However, some checks are easier if you can download tools. To keep it simple, we've included instructions for just one tool - the Firefox Developer Toolbar, which is free. (Note that we're not endorsing that tool over others.) There are other useful [http://www.w3.org/WAI/eval/selectingtools tools to help with evaluation].<br />
<br />
To learn how to do these checks with other tools, see [TBD either Web Platform Docs -or- WAI-Engage wiki].<br />
<br />
====FF Toolbar====<br />
[@@ how to download Firefox browser, then the Firefox Web Developer Toolbar...]<br />
<br />
====WCAG Links====<br />
These checks are based on the Web Content Accessibility Guidelines ([http://www.w3.org/WAI/intro/wcag WCAG]) 2.0. The main points in WCAG are called "Success Criteria". In the "Learn more from|References" sections of this page, there are links to pages that explain the relevant success criteria in the "Understanding WCAG 2.0" document. <br />
<br />
====Visual and Non-Visual Checks====<br />
<br />
Some checks require you to be able to see the visual rendering of the page. These are marked ''[visual]''. We've indicated checks that do not require seeing the page with ''[non-visual]''.<br />
<br />
====Practicing with BAD, the Before-After Demo====<br />
<br />
<p>The Before and After Demonstration (BAD) shows an inaccessible website and a retrofitted version of this same website. You can use the BAD pages to learn how to do these checks. <span style="color:#808080;">[@@maybe delete this if we have the instructions in each section] First, do the check on a good demo page ("after") to see what it should look like if accessibility is handled well. Then, do the check on the corresponding bad demo page ("before") to see what it looks like when accessibility is not handled well.[@@end delete]</span></p><br />
<br />
===Little Background===<br />
<br />
These checks are designed for anyone who knows how to use websites. You don't need much knowledge or skill. There are a couple things to know that will help you understand the explanations in the checks:<br />
* ''Screen readers'' read aloud the information in a web page. They are used by people who are blind and by some people with reading disabilities.<br />
* Some people use ''voice input'' instead of a keyboard and mouse. For example, ...@@<br />
* [@@anything else needed?]<br />
<br />
If you want to learn more, see:<br />
* [http://www.w3.org/WAI/intro/people-use-web/ How People with Disabilities Use the Web]<br />
* [http://www.w3.org/standards/webdesign/accessibility Introduction to Accessibility]<br />
* [http://www.w3.org/WAI/yourWAI Other WAI resources]<br />
<br />
<br /><br />
<hr /><br />
<br />
===<span style="color: #808080;">EOWG Comments on the Introduction</span>===<br />
* <span style="color: #808080;">@@ comment {name}</span><br />
<br /><br />
<hr /><br />
<br /><br />
<br />
==Quick Checks==<br />
<br />
<p>Here are 5 things you can do to quickly check for accessibility barriers on a web page:<br /><br />
<span style="color:#808080;">{EOWG note: Let's work on the longer section first, then decide what we can move up to the quick checks section later.</span></p><br />
#First thing.<br />
#Second thing.<br />
#Third thing. <br />
#Fourth thing. <br />
#Fifth thing.<br />
<br />
Once you have taken this quick dip you may be ready to dive a bit deeper. The next section provides more context and additional things you can do to check for accessibility barriers.<br />
<br />
==A Deeper Look==<br />
<p>If you are interested in a more comprehensive look at the page(s), here more tests that require a little more time, skills, and/or tools.</p><br />
<br />
===Check image text alternatives ("alt text")===<br />
<span style="color:#808080;">''[updated 23 January]''</span><br />
<br />
<p>Text alternatives (&quot;alt text&quot;) convey the purpose of an image. They are used by people who cannot see the image. (For example, people who are blind and use screen readers can hear the alt text read out; people who have turned off images to speed download or save bandwidth can see the alt text.)</p><br />
<p>The text should be functional and provide an equivalent user experience, not necessarily describe the image. (For example, appropriate text alternative for a search button (<span style="color:#808080;">[/WAI/images/search-icon.png]</span>) would be &quot;search&quot;, not &quot;magnifying glass&quot;.)</p><br />
<br />
<p>Automated tests can tell you if alt text is missing. To determine if the alt text is appropriate , you need to see the image and judge it in context.</p><br />
<br />
<strong>What to check for:</strong><br />
* Important images have appropriate text alternatives.<br />
<br />
====<strong>To check if any images are missing alt text with the W3C Validator</strong>: <em>[non-visual]</em>====<br />
<ol><br />
<li>In any browser, open the [http://validator.w3.org/ W3C HTML Validator (The W3C Markup Validation Service)].</li><br />
<li>In the Address field, type the URI (e.g., www.w3.org).</li><br />
<li>Click the Check button.<br />
<br />''The results page appears (with title starting either [Valid] or [Invalid]).''</li><br />
<li>Search for &quot;required attribute &quot;alt&quot; not specified&quot;. If you find any, that means there are images without alt text.</li><br />
</ol><br />
[@@ will give line number - however, need to figure out what the image is - whether it's an important image of something like spacer gif - to determine severity of barrier...]<br />
<br />
====<span style="color:#808080;">[+/-]</span> <strong>To check if alt text is appropriate <em>- with FF toolbar:</em></strong><em> [visual]</em>====<br />
<ol><br />
<li>Open the web page you are checking.</li><br />
<li>In the toolbar, select "Images", then "Display Alt Attributes". <span style="color:#808080;">[image]</span> Or, with the keyboard: [@@keyboard shortcut]<br /><br />
''The alt text will be displayed before the images.''</li><br />
<li>[@@ no indication of missing alt?]</li><br />
<li>Before the images it shows the alt text as white letters on a red background. See if that text adequately conveys the information in the image it is next to, per the Tips below.</li><br />
</ol><br />
<br />
====<span style="color:#808080;">[+/-]</span> <strong>To check if alt text is appropriate <em>- with any browser</em></strong><em>: [visual]</em>====<br />
<ol><br />
<li>Open [http://wave.webaim.org/ WAVE] web accessibility evaluation tool.</li><br />
<li>Type the website address in the box after &quot;Enter the URL of the web site you want to evaluate:&quot;</li><br />
<li>Click the &quot;WAVE this page!&quot; button.<br /><br />
''Your web page will show up in the browser with lots of little icons on it.''</li><br />
<li>Look for the red icon <span style="color:#808080;">[image]</span>. It is next to any image that is missing alt text.</li><br />
<li>Look for the green alt icon <span style="color:#808080;">[image]</span>. Next to it is text on a light blue background; the alt text is inbetween the asterisks (*). See if that text adequately conveys the information in the image it is next to, per the Tips below.</li><br />
</ol><br />
<br />
====<strong>Tips:</strong>====<br />
<ul><br />
<li>What is appropriate alt text?<br />
<ul><br />
<li>The text conveys the same meaning as the image. That is, if someone cannot see the image, they get the important information from the image in the alt text. It depends on the context. For example, for an image of a dog on a kennel club website, the alt text might include the breed of the dog; however, for the same image that is just decorative on a dog park website, the image might not need any alt text at all.</li><br />
<li>If the image is not important &mdash; for example, it is just decoration &mdash; it should have null alt text (<code>alt=&quot;&quot;</code>).</li><br />
<li>The alt text does not need to include &quot;button&quot;, &quot;link&quot;, or &quot;image of&quot;.</li><br />
<li>If there is text in the image &mdash; for example, it is an ad with a picture &mdash; the text from the image should be included in the alt text.</li><br />
<li>If the image has complex information &mdash; such as charts or graphs &mdash; the image should have a short alt text, and then the detailed description of the information should be provided elsewhere.</li><br />
</ul><br />
</li><br />
<li><em>In HTML:</em> Alt is an attribute of the image tag, and other tags. It looks like this in markup: <code>&lt;img alt=&quot;WAI logo&quot; src=&quot;/wai/logo.png&quot;&gt;</code></li><br />
</ul><br />
<br />
====<span style="color:#808080;">[+/-]</span> <strong>To try checking the alt text in BAD:</strong>====<br />
<br />
=====Checking if any images are missing alt text in BAD: <em>[non-visual]</em>=====<br />
Follow the instructions for "To check if any images are missing alt text" above and use the bad ("before") home page: <code>www.w3.org/WAI/demos/bad/before/home</code>. Notice there are lots of images without alt text. (Many of these are just decorative and should have null alt text, per the Tips above.)<br />
<br />
=====Checking if alt text is appropriate in BAD: <em> [visual]</em>=====<br />
<br />
<p>With one of the "To check if alt text is appropriate" checks above, use the inaccessible ("before") home page <code>www.w3.org/WAI/demos/bad/before/home</code> Notice:<br />
<ul><br />
<li>Missing alt: The weather image of the cloud and sun is missing alt.</li><br />
<li>Inappropriate alt text:<br />
<ul><br />
<li>Near the top, left, see the long alt text starting with "Red dot with...". That description is way too detailed and includes unimportant information. The appropriate alt text in the good ("after") page is: "Citylights: your access to the city."</li><br />
<li>Near the bottom in the middle, see the image of text: &quot;(1)269C-H-O-K-E&quot;. The alt is 123456789, which is not equivalent.</li><br />
</ul><br />
</li><br />
<li>Appropriate alt text: Near the top, see the W3C image; the alt text is: "W3C logo".</li><br />
</li><br />
</ul><br />
<br />
====<strong>Learn more from:</strong>====<br />
<ul><br />
<li>[http://www.w3.org/WAI/intro/people-use-web/principles#alternatives Text alternatives for non-text content] is an easy introduction with links to more details</li><br />
<li>[http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html Non-text Content] - Understanding Success Criteria 1.1.1 for WCAG 2.0 (Level A)</li><br />
</ul><br />
<br />
<br/><br />
<hr/><br />
====<span style="color:#808080;">EOWG Notes on alt text</span>====<br />
<span style="color:#808080;">importance: HIGH.<br />
<br/>5min: yes, at least the easy part.<br />
<br />15min: yes. might want additional checks here.<br />
<br/>Without visual rendering: can check that description exist, can check that they are not too verbose, can check that they are appropriate to the general content of the page, but not necessarily appropriate to a specific image.</span><br />
<br />
<span style="color:#808080;">Would like to be able to use FF Toolbar select "Images", then "View Image Information" to check for missing alt, but null alt is not listed; therefore, you cannot use it to check for missing alt...</span><br />
<br />
<span style="color:#808080;">[http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Jan-17#Check_text_descriptions_for_images 17 Jan 2013 draft of Check text descriptions for images]</span><br />
<br />
<p>[@@ JS on 23 Jan.: Do we want to use "salt text" throughout? Isn't alt attribute more correct? I understand the idea of using the word alt, as short for alternative, but . . . Maybe this is just a personal pet peeve of mine, but based on the Twittersphere, I'm not the only one.]<br />
<hr/><br />
<br/><br />
<br />
===Check headings===<br />
<span style="color:#808080;">''[updated 23 Jan]''</span><br />
<br />
Web pages often have sections of information separated by visual headings, for example, heading text is bigger and bold (like "Check headings" right above this sentence :-). To make these work for all users, the headings need to be "marked up" in the web page "code" (e.g., HTML). That way people can navigate to the headings &mdash; including people who cannot use a mouse and use only the keyboard, and people who use a screen reader.<br />
<br />
Heading levels should have a meaningful hierarchy, e.g.:<br />
<ul><br />
<li>Heading Level 1 &lt;h1&gt;<br />
<ul><br />
<li>Heading Level 2 &lt;h2&gt;<br />
<ul><br />
<li>Heading Level 3 &lt;h3&gt;</li><br />
<li>Heading Level 3 &lt;h3&gt;</li><br />
</ul><br />
</li><br />
<li>Heading Level 2 &lt;h2&gt;<br />
<ul><br />
<li>Heading Level 3 &lt;h3&gt;<br />
<ul><br />
<li>Heading Level 4 &lt;h4&gt;</li><br />
<li>Heading Level 4 &lt;h4&gt;</li><br />
</ul><br />
</li><br />
</ul><br />
</li><br />
<li>Heading Level 2 &lt;h2&gt; </li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<br />
<strong>What to check for:</strong><br />
<ul><br />
<li>Are there headings marked up?</li><br />
<li>Is the hierarchy meaningful? (Ideally the page starts with an "h1" &mdash; which is usually similar to the page title &mdash; and does not skip levels; however, this is not an absolute requirement.)</li><br />
<li>Is there text that looks like headings but is not marked up as a heading?</li><br />
<li>Is there text that is marked up as headings that is not really a section heading?</li><br />
</ul><br />
<br />
====<strong>To check headings outline with the W3C Validator:</strong> <em>[non-visual & visual]</em>====<br />
<ol><br />
<li>In any browser, open the [http://validator.w3.org/ W3C HTML Validator (The W3C Markup Validation Service)].</li><br />
<li>In the Address field, type the URI (e.g., www.w3.org).</li><br />
<li>Click the More Options link.</li><br />
<li>Select the Outline checkbox.</li><br />
<li>Click the Check button.<br />
<br />''The results page appears (with title starting either [Valid] or [Invalid]).''</li><br />
<li>In the results page, near the top, at the end of the "Jump to:" line, click the Outline text link.</li><br />
<li>Non-visual checks:<br />
<ul><br />
<li>Is there anything there? If there is no text between "Below is an outline for this document, automatically generated from the heading tags (&lt;h1&gt; through &lt;h6&gt;.)" and "If this does not look like a real outline..." it means there are no headings marked up on the page.</li><br />
<li>Does the outline start with [H1] and follow a meaningful hierarchy? (That's not required, but strongly suggested.)</li><br />
</ul><br />
</li><br />
<li>Visual checks: Compare the Document Outline to the visual rendering of the page.<br />
<ul><br />
<li>Are the things that look like headings on the page listed in the Document Outline?</li><br />
<li>Are there things in the Document Outline that aren't really headings? </li><br />
</ul><br />
</li><br />
</ol><br />
<br />
====<span style="color:#808080;">[+/-]</span> <strong>To check heading markup is appropriate <em>- with FF toolbar:</em> </strong><em>[visual]</em>====<br />
<ol><br />
<li>Open the web page you are checking.</li><br />
<li>In the toolbar, select "Outline", then "Show Element Tags Names When Outlining". <span style="color:#808080;">[image]</span> Or, with the keyboard: [@@keyboard shortcut]<br /></li><br />
<li>In the toolbar, select "Outline", then "Outline Headings". <span style="color:#808080;">[image]</span> Or, with the keyboard: [@@keyboard shortcut]<br /><br />
''The headings will be outlined and &lt;h1&gt;, &lt;h2&gt;, etc. icons will be before the headings.''</li><br />
<li>Anything that is a functional heading should have a heading icon before it.</li><br />
<li>Anything that is a '''not''' functional heading should '''not''' have a heading icon before it.</li><br />
</ol><br />
<br />
====<span style="color:#808080;">[+/-]</span> <strong>To check heading markup is appropriate <em>- with any browser:</em> </strong><em>[visual]</em>====<br />
<ol><br />
<li>Open [http://wave.webaim.org/ WAVE] web accessibility evaluation tool.</li><br />
<li>Type the website address in the box after &quot;Enter the URL of the web site you want to evaluate:&quot;</li><br />
<li>Click the &quot;WAVE this page!&quot; button.<br /><br />
''Your web page will show up in the browser with lots of little icons on it.''</li><br />
<li>Anything that is a functional heading should have a heading icon (<span style="color:#808080;">[image]</span>, <span style="color:#808080;">[image]</span>, ...) before it.</li><br />
<li>Anything that is a '''not''' functional heading should '''not''' have a heading icon before it.</li><br />
</ol><br />
<br />
====<span style="color:#808080;">[+/-]</span> <strong>To try checking headings in BAD:</strong>====<br />
<br />
<span style="background:yellow;">OPEN: Does BAD have example of text that is marked up as a heading but should not be?</span><br />
<br />
<span style="background:yellow;">OPEN:</span> [@@ can we find an appropriate example of a web page with no headings at all? to show what you get in the Validator outline]<br />
<br />
=====Checking headings outline with the W3C Validator in BAD <em>[non-visual]</em>=====<br />
<br />
<ul><br />
<br />
<li>Follow the instructions under "To check headings outline with the W3C Validator" above and use the good ("after") News page: <code>www.w3.org/WAI/demos/bad/after/news</code>. Notice there is a nice hierarchical outline.</li><br />
<br />
<li>Next, follow the instructions under "To check headings outline with the W3C Validator" above and use the after ("before") News page: <code>www.w3.org/WAI/demos/bad/before/news</code>. (The "Check" button might now say "Revalidate".) Notice there is just one heading.</li><br />
<br />
</ul><br />
<br />
=====Checking heading markup is appropriate in BAD <em>[visual]</em>=====<br />
<br />
<ul><br />
<br />
<li>Start by visually looking at the [http://www.w3.org/WAI/demos/bad/before/news.html Bad ("after") news page]. What looks like headings? ''(Citylights News, Heat wave linked to temperatures, Man Gets Nine Months in Violin Case, ...)''</li><br />
<br />
<li>Next, see how it should look. Follow one the the instructions for "To check heading markup is appropriate" above on the good ("after") News page: <code>www.w3.org/WAI/demos/bad/after/home</code>. Notice the headings have icons next to them.</li><br />
<br />
<li>Next, see what it looks like when headings are not marked up. Follow one the the instructions for "To check heading markup is appropriate" above on the bad ("before") News page: <code>www.w3.org/WAI/demos/bad/before/home</code>. Notice there is text that visually looks like headings, but does not have headings icons next to it. (With WAVE, there are yellow icons with "h?" because it thinks these might be headings.)</li><br />
</ul><br />
<br />
====<strong>Learn more from:</strong>====<br />
<ul><br />
<li>[http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-descriptive.html Headings and Labels] - Understanding Success Criteria 2.4.6 for WCAG 2.0 (Level AA)</li><br />
<li>[http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-headings.html Section Headings] - Understanding Success Criteria 2.4.10 for WCAG 2.0 (Level AAA)</li><br />
<li>[@@how screen reader users navigate with headings... not much detail in [http://www.w3.org/WAI/intro/people-use-web/principles accessibility principles] ... ]</li><br />
</ul><br />
<br />
<br /><br />
<hr /><br />
====<span style="color:#808080;">EOWG Notes on Headings</span>====<br />
<br />
<span style="color:#808080;">importance: HIGH.<br />
<br/> 5min: maybe. fairly easy to check if there are at least some headings.<br />
<br /> 15min: yes.<br />
<br />Without visual rendereing: can check headings exist and make sense, but can't tell that all headings are styled appropriately or that text styled as a heading is marked up as one.</span><br />
<br />
<span style="color:#808080;">title was: Check headings and other semantic structure</span><br />
<br />
[http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Jan-17#Check_headings_and_other_semantic_structure 17 Jan draft of Check headings and other semantic structure]<br />
<hr /><br />
<br /><br />
<br />
===Check keyboard access, labels, content order, visual focus===<br />
<span style="color:#808080;">EOWG notes - importance: HIGH.<br />
<br/> 5min: maybe.<br />
<br />15min: yes, at least part of it.<br />
<br />Without visual rendering: @@</span><br />
<br />
Many people do not use the mouse and rely on the keyboard to interact with the Web. This requires keyboard access to all functionality, including links, form controls, input, and other user interface components. While screen reader users rely on the keyboard, they are not the only ones. In addition, sighted users with mobility impairments may rely on the keyboard or have assistive technologies that are controlled through keyboard actions. Therefore, key components of effective keyboard access include visible focus indication and a logical tab order.<br />
====What To Do====<br />
* Click in the address bar, then put your mouse aside and don't use it. <br />
* Press the 'tab' key to move around the page.<br />
* Use the keyboard to set the focus to all focusable elements on the page.<br />
====What To Look For====<br />
* Can you tab to all the elements, including links, form fields, buttons, and media player controls? Are there any actions you can't get to (e.g., if they are only available on mouse hover)?<br />
* Does the tab order follow the logical reading order, top to bottom, left to right in sequence?<br />
* Does the focus get stuck anywhere - that is, you can tab into a control but not out? (called a "keyboard trap")?<br />
* Does the order that items get focus make sense to sighted users? (e.g., you don't jump around the page out of order logically)<br />
* Can you tab right through to the bottom of the page and then resume again from the top? (e.g. you don't get stuck anywhere and can't move on)<br />
* If there is a drop-down box (for example, for navigating to a different page): If you tab into the drop-down box, can you use the down/up arrow keys to move through the options, and @@use 'tab' to the following item@@? (Make sure it doesn't automatically select the first item.)<br />
*Visually examine progress through elements and verify that the focus indicator is clearly visible (i.e. you can see where you've 'tabbed' to).<br />
*Common failures occur when the default focus indicator is turned off in CSS or when the element is styled with borders that occlude the focus indicator.<br />
*Verify that any visual changes that occur with mouse hover also are triggered with keyboard focus<br />
<br />
====References====<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#keyboard Functionality is available from a keyboard]<br />
* [http://www.w3.org/WAI/users/browsing#keyboard Browsing the Web by Keyboard] section in [http://www.w3.org/WAI/users/browsing Better Web Browsing: Tips for Customizing Your Computer]<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html Focus Visible - Understanding Success Criteria 2.4.7 (Level A)]<br />
*[http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html Focus Order - Understanding Success Criteria 2.4.3] <br />
* Example: [http://www.w3.org/WAI/demos/bad/before/survey.html web page template that does not enable keyboard access] from the WAI Before and After Demo (BAD)<br />
<br />
====Notes====<br />
* Mac browsers by default only tab through forms, will need to turn on...<br />
* not work easily in Opera...<br />
* ...<br />
<br />
<br /><br />
<hr /><br />
<br />
===Check page title===<br />
<br />
<span style="color:#808080;">''[updated 23 January 2013]''</span><br />
<br />
[image: top of browser showing full title of current page, and multiple page tabs showing abbreviated titles.]<br />
<br />
Good page titles are particularly useful when people have multiple web pages open at the same time (as shown in the above image). They are also used for bookmarks/favorites and in search engine results. The first thing screen readers say when the user goes to a different web page is the page title.<br />
<br />
====What to do ''[non-visual]''====<br />
# Choose a browser that displays page titles. Most do by default, except Chrome and IE #.<br />
# Look at the browser's window title bar (or with a screen reader, listen to it).<br />
# Look at titles of other pages within the website.<br />
<br />
====What to look for ''[non-visual]''====<br />
<br />
* Check that the title adequately and briefly describes the content of the page.<br />
* Check that the title is different from other pages on the website, and adequately distinguishes the page from other web pages.<br />
<br />
=====Tips=====<br />
* There is some flexibility on what makes a good page title. Some guidance is linked from the [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html#navigation-mechanisms-title-resources-head Related Resources section of Understanding Success Criteria 2.4.2].<br />
* A common mistake is to put the website name first and then the specific page title, for example:<br />
** Poor titles:<br />
*** Acme Web Solutions, Inc. - About Us<br />
*** Acme Web Solutions, Inc. - Contact Us<br />
*** Acme Web Solutions, Inc. - History<br />
** Better page titles:<br />
*** About Acme Web Solutions<br />
*** Contact Acme Web Solutions<br />
*** History of Acme Web Solutions<br />
* Consider how the page title will be used in context; for example, the title of a page in the middle of a multi-step process probably does not need the website name in the title. <span style="color:#808080;">''[@@ maybe it's not worth the clutter to include this point?]''</span><br />
* <em>In HTML:</em> The page title is near the top of the web page markup ("code"), in the &lt;head&gt; area. It looks like this in markup: <code>&lt;title&gt;Acme Web Solutions home page&lt;/title&gt;</code><br />
<br />
====BAD Example====<br />
In [http://www.w3.org/WAI/demos/bad/ BAD], all of the bad ("before") pages have the title "Welcome to CityLights!" (plus a description in brackets that is necessary for people using them demo). The page titles are not unique. Whereas, the good ("after") pages are titled: Welcome to CityLights!, Citylights News, Citylights Tickets, and Citylights Survey.<br />
<br />
====References====<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html Page Titled ]- Understanding Success Criteria 2.4.2 for WCAG 2.0 (Level A)<br />
<br />
<br /><br />
<hr /><br />
<br />
====<span style="color:#808080;">EOWG Notes on Page Title</span>====<br />
<br />
<span style="color:#808080;">importance: medium.<br />
<br/> 5min: maybe not. it is easy to check, but a little more complicated to explain what makes a good title. Also not the most vital to lots of users.<br />
<br />15min: probably.<br />
<br />Without visual rendering: can check</span><br />
<br />
<span style="color:#808080;">IMPORTANT! - Some browsers don't show title in browser title bar (Chrome, IE) ''{does this mean it doesn't meet our criteria for including in the 5 min list?}''</span><br />
<br />
[http://www.w3.org/WAI/EO/wiki/Prelim_Eval_2013-Jan-17#Check_the_page_title 17 Jan draft of Check the page title]<br />
<hr /><br />
<br /><br />
<br />
===Check color contrast===<br />
<span style="color:#808080;">EOWG notes.<br />
<br/> 5min: maybe.<br />
<br /> 15min: yes.<br />
<br /> Without visual rendering: yes, with tools</span><br />
<br />
Good contrast between the text and background is very important to people with visual impairments and older people who experience loss of contrast sensitivity. This includes the default black text on white background as well as colour combinations. <br />
<br />
Some users may have requirements for very high or very low contrast, or a particular colour combination and they may choose to vary your colour choice by using their own preferred style sheet.<br />
<br />
<br />
Remember that not all users will have high resolution screens and subtle colour combinations may not be rendered properly if the user is using a reduced colour set.<br />
<br />
<br />
Screen reader users will hear the text even if the contrast is poor, or deliberately hidden as white on white or black on black!<br />
====First stage: What to do====<br />
* Inspect the text in the main content, menu tabs, links and selected links and in buttons, labels and captions. <br />
====Common failures====<br />
* Look out for instances of pale text that might blend into the background eg grey on the default off-white background. Other common combinations are light green, yellow or blue text on the default background or a background that is a slightly darker shade of the same colour. <br />
* Look for instances of dark colours on a dark background eg purple, red or dark blue on black<br />
* Any suspect instances need to be investigated further.<br />
<br />
====Second stage: What to do====<br />
A number of on-line tools can be used to compare the exact ratio of text and background. There are two types:<br />
* A lexical tool can test the declared colour values set in the style sheet and provide a report on contrast. This is useful for checking across the whole website<br />
** list named tools<br />
* A live online colour analyser allows you to select samples of the text and background colours for analysis. Use zoom to increase the font size and follow the tool instructions to pick up a sample of the text colour and a sample of the background colour. If the background is patterned take a sample at different points. <br />
** list named tools<br />
<br />
====Common failures====<br />
* The contrast ratio for normal sized text is less than the minimum recommendation of 4.5:1<br />
* The contrast ration for large, bold text such as a page heading level set at 150% (1.5ems) is less than the minimum recommendation of 3:1<br />
<br />
====References====<br />
Contrast (minimum) Understanding success criteria 1.4.3 (AA) http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html<br />
<br />
Contrast (enhanced) Understanding success criteria 1.4.6 (AAA).<br />
<br />
BAD example: http://www.w3.org/WAI/demos/bad/before/annotated/tickets.html Note 6, text in some rows is set dark grey on a light grey background.<br />
<br />
====Notes==== <br />
There are some exceptions such as large text passing at 3:1 ratio, and special requirements to achieve full conformance. The understanding document contains detailed information on text size that would be useful in understanding text resize.<br />
<br />
<insert from Wayne Dick><br />
<p> There are two types of color contrast testers: The first type, a<br />
lexical evaluator, looks at styles in web page code and<br />
computes color contrasts based on coded values. The second type,<br />
run time tester, simply allows the user to sample what is on the<br />
screen and computes contrast based on samples. </p><br />
<p> The lexical evaluator examines what the author declares. It<br />
gives a full page report based color contrasts declared by the<br />
programmer. These tests are quick and efficient. They break down<br />
when run time values change due to actions taken by active<br />
content.</p><br />
<p> The run time tester requires more hands on work. The evaluator<br />
can take samples as the web site runs and determine actual<br />
contrasts. The problem here is that as contrasts change over time<br />
the tester must sample many states of the page. </p><br />
<p> Both types of test are important. If any active content changes<br />
color during run time then WAI advises run time testing. Lexical<br />
testing can be very useful and save time with items with static <br />
color. </p><br />
<br />
<end Wayne's insert>{thanks-you, Suzette}<br />
<br />
<br />
<br />
[Yesterday's version<br />
First pass - I'm working on this:<br />
<br />
Good colour contrast between the text and background is very important to people with visual impairements. Some users may chose to vary your colour choice by using their own preferred style sheet. <br />
<br />
Screen reader users will hear the text even if the contrast is poor, or deliberately hidden as white on white or black on black!<br />
<br />
* First stage - look out for instances of pale text that might blend into the background eg grey on the default off-white background. Other common combinations are pale green, yellow or blue text on a background of a slightly darker shade of the same colour. Check the text in the main content, menu tabs, links and selected links and in buttons, labels and captions. Any suspect instances need to be investigated. <br />
<br />
Remember that not all users will have high resolution screens and subtle colour combinations may not be rendered properly if the user is using a reduced colour set.<br />
<br />
* Second stage - a number of on-line tools can be used to compare the exact ratio of text and background. Use zoom to increase the font size and follow the tool instructions to pick up a sample of the text colour and a sample of the background colour. If the background is patterned take a sample at different points. The minimum contrast (level AA) is 4.5:1.]<br />
<br />
====Comments 2012-Nov-30====<br />
Shawn: Definite yes<br />
<br />
===Video, Sound, (multimedia) ===<br />
<span style="color:#808080;">EOWG notes.<br />
<br/> 5min: maybe. vital for some uses, through maybe not really easy to check thoroughly<br />
<br /> 15min: yes.<br />
<br /> Without visual rendering: can check for presense of alt content, but not quality</span><br />
<br />
====What to do====<br />
# Follow the steps for keyboard access to ensure that the media player controls are labeled and operable by all users.<br />
# Play the audio content<br />
# Play the video content<br />
# Toggle closed captions on (if available) <br />
# Toggle audio description on (if available)<br />
# If no captions or audio description options are provided, check page for transcript or link to transcript<br />
<br />
====What to look for====<br />
* Captions:<br />
** Verify that captions are synchronized to the spoken content<br />
** Ensure they are accurate and complete and that no content is omitted.<br />
** Verify that they are properly formed with correct spelling, sentence structure, and punctuation.<br />
** Make sure that audio content other than dialogue is included (music, relevant ambient sounds, etc)<br />
* Audio Description<br />
** '''(Judgement call)''' Watch the video content to verify that audio description is needed for complete understanding.<br />
** If needed, verify that they are provided in a separate track that can be toggled on and that they provide context for those who do not see the video.<br />
* Transcript: As a fall-back when captions and audio descriptions are not provided, check to see if there is text-based content that contains dialogue, any other audio content, and any necessary description of video content. Check for spelling and accuracy. <br />
<br />
''(see also text alternatives for graphic content)''<br />
<br />
====References====<br />
* [http://www.w3.org/2008/06/video-notes Multi Media FAQs] from the W3C<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-captions.html Understanding WCAG SC 1.2.2 Captions](Level A)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-audio-desc.html Understanding 1.2.5 Audio Description](Level A) <br />
====Notes====<br />
<span style="color:#808080;">[can be internal notes for now or maybe will be included in final doc]</span><br />
*...<br />
<br />
====Comments 2012-Nov-30====<br />
Shawn: Vital that transcripts are available, so should be included. Rewrite to simplify checks based on presences of alt content rather than checking quality. Leave this for complex check.<br />
<br />
===Check forms===<br />
<br />
[15: maybe not]<br />
<br />
[drafted, edited, needs review - move keyboard access, visual focus, content order with other section ?Sharron ?Suzette]<br />
<br />
<span style="color:#808080;">EOWG notes.<br />
<br/> 5min: no, too complicated.<br />
<br /> 15min: not sure</span><br />
<br />
''Note: Some aspects will be integrated with keyboard access, visual focus, content order.''<br />
<br />
<p>Forms are everywhere on the web and successful user interaction relies on clear, understandable, and accessible form controls. Several principles of accessibility should be kept in mind when testing forms. Labels for form controls, input, and other user interface components must be provided. Many people do not use the mouse and rely on the keyboard to interact with the Web. This requires visible keyboard access to all functionality, including form controls. Forms may be confusing or difficult to use for many people, and, as a result, they may be more likely to make mistakes. Clear recovery mechanisms must be provided.</p> <br />
<br />
====Forms - simplified====<br />
[Edited by Suzette, is this sufficiently simplified?]<br />
<br />
Note: Some aspects of Forms will be integrated with keyboard access, visual focus, content order. {SK - Also have removed references to colour coding and graphics/non text content and CAPTCHA.} <br />
<br />
Forms are everywhere on the web and successful user interaction relies on clear, understandable, and accessible form controls. Forms are complex and need in depth assessment. <br />
<br />
Some critical elements which can affect screen reader users are much easier to detect using an automatic tool to check the HTML and CSS, or as a user trial with an experienced screen reader user. <br />
<br />
The following visual checks can identify some common problems which are particularly important when testing forms.<br />
<br />
{There 10 Success criteria references are included to help editorial choices – is this too many? SK}<br />
<br />
* Labels for form controls, input, and other user interface components must be provided. (Labels and Instructions 3.3.2 A)<br />
* Keyboard access for people who do not use the mouse and rely on the keyboard to interact with the Web. This requires visible keyboard access to all functionality, including form controls. (Keyboard 2.1.1 A, No keyboard trap 2.1.2 A, Focus visible 2.4.7 AA)<br />
* Information needs to be in a logical order which is followed when tabbing through the input fields. (Meaningful sequence 1.3.2 A, Focus order 2.4.3 A) <br />
* Error correction: Forms may be confusing or difficult to use for many people, and, as a result, they may need more time and be more likely to make mistakes. Clear recovery mechanisms must be provided. (Error identification 3.3.1 A, Error suggestion 3.3.3.AA, Error prevention (legal, financial, data) 3.3.4 AA. Timing 2.2.1 A)<br />
<br />
<br />
<br />
=====Are there any forms=====<br />
Check through the web pages to look for examples of forms.<br />
<br />
What to look for: <br />
**Forms include registration forms, contact forms, booking and purchase details which include text entry fields, radio buttons, dropdown boxes and submit buttons and also single text entry boxes such as login or search box.<br />
<br />
=====Visually examine the instructions for the form and input fields=====<br />
Check over each form.<br />
<br />
What to look for: <br />
**Are there text instructions at the beginning of the form including if any elements are essential?<br />
**Are there text labels (before/after?) the input fields that describe what to do and if any elements are essential<br />
**{Exclude? If required fields are indicated by use of color cues, ensure that additional, alternative methods are also used – Use of colour 1.4.1 A)<br />
<br />
=====Keyboard access=====<br />
Use the Tab key to move through form controls, text boxes, radio buttons, drop down box and submit button. (Use shift tab to go back). Use the cursor (arrow) keys to access selection box content.<br />
<br />
What to look for:<br />
**Is the focus visible on all form controls, including inputs, submit mechanisms, and check boxes and radio buttons?<br />
**If the form control is a check box or radio button, ensure that focus indication includes form label as well as the actual control (SK –can you do this visually?)<br />
**If the form control is a select box, ensure that arrow keys can move focus between select options and that selection is made by user action and not by default focus. (SK – can you do the second part of this visually?)<br />
<br />
=====Logical sequence=====<br />
Compare the sequence of information presented visually with the tab through order.<br />
<br />
What to look for:<br />
**Ensure that focus moves logically between the fields. <br />
**Enter correct and false data in form input fields <br />
<br />
=====Use the keyboard to enter data into the text field.=====<br />
Enter correct and incorrect data – eg incorrectly formatted telephone numbers and email addresses.<br />
<br />
What to look for:<br />
** Ensure that focus does not automatically advance to the next field, but requires user input to advance (SK – is this easy or advanced, what success criteria?)<br />
** When erroneous data is entered and form submitted: <br />
** Ensure that error message is clear and specific about the nature of the error and the field in which it was made <br />
** Ensure that focus moves to the error message <br />
** Ensure that guidance is provided to help user understand and fix the error.<br />
<br />
{BROWSER TYPE - are some browsers more helpful than others when tabbing through forms and do you need to set any preferences about tabbing?- SK}<br />
<br />
====References====<br />
<p>Several Accessibility Principles are relevant to the accessibility of forms, including these:<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#alternatives Text alternatives to non-text content]<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#keyboard Functionality is available from a keyboard]<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#navigable Users can easily navigate, find content, and determine where they are]<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#predictable Content appears and operates in predictable ways]<br />
* [http://www.w3.org/WAI/intro/people-use-web/principles#tolerant Users are helped to avoid and correct mistakes]</p><br />
<p>WCAG2 Guidelines and Success Criteria that may be applied to determining the accessibility of forms include these:<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html Non-text Content]: Understanding Success Criteria 1.1.1 (Level A)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html Keyboard]: Understanding Success Criteria 2.1.1 (Level A)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html Focus Order]: Understanding Success Criteria 2.4.3 (Level A)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-descriptive.html Headings and Labels]: Understanding Success Criteria 2.4.6 (Level AA)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html Visible Focus]: Understanding Success Criteria 2.4.7 (Level AA)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html Predictable]: Understanding Guideline 3.2 (Level A and AA)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error.html Input Assistance]: Understanding Guideline 3.3 (Level A and AA)<br />
* [http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html Name, Role, Value]: Understanding Success Criteria 4.1.2 (level A)</p><br />
<br />
<p>WAI's Before and After Demo (BAD)includes examples of forms that have been made accessible:<br />
* [http://www.w3.org/WAI/demos/bad/before/survey.html Inaccessible forms page]<br />
* [http://www.w3.org/WAI/demos/bad/after/survey.html Accessible forms page]<br />
<br />
====Notes====<br />
<span style="color:#808080;">[can be internal notes for now or maybe will be included in final doc]</span><br />
*...<br />
* Is it possible to have a 'first glance' option to identify potential trouble spots and very common problems, which can then be examined in more depth? {Suzette}<br />
* I have noticed some developers having trouble with single fields such as search boxes or login details, or simple little contact forms - perhaps we could expand the opening description to suggest looking for these. It is not just dedicated forms such as membership details, job applications, tax returns, travel booking and shopping etc.{Suzette}<br />
<br />
====Comments 2012-Nov-30====<br />
Shawn: Maybe, a couple of things are easy, some are complex. We could use the nice writeup somewhere else if not used here.<br />
Suzette: I can try and pick the easy bits out of Sharron's content to see if we can get this in.<br />
Shawn: Or add notes on forms to Keyboard Access and Visible Focus sections.<br />
<br />
===Check usable with page zoomed and text enlarged [15 min: maybe] [Ian to try write up of simple approach to address related issues]===<br />
<span style="color:#808080;">EOWG notes.<br />
<br/> 5min: no<br />
<br /> 15min: maybe not. maybe too complex? some conflicting perspectives in forums.<br />
<br />Without visual rendering: cannot be tested</span><br />
<br />
* Zoom to 200%<br />
* Text-only enlargement... (e.g., text actually changes in IE)<br />
<br />
People with mild to moderate visual impairments may need to enlarge text in order to read it, or read it without straining. This simple requirement is mostly achieved by the functionality of the browser and ensuring that the page design supports that functionality. <br />
<br />
The text should be resizable up to 200% without losing information, using a standard browse. Additionally any images of text should also be resizable or replaced with actual text. <br />
<br />
Most modern browsers now offer a zoom function which enlarges both text and other content together. Some older browsers do not resize text if it was set using fixed units – such as points or pixels. <br />
<br />
====What to do====<br />
* Open your preferred browsers. Internet Explorer, Firefox, Chrome and Opera all offer zoom as a function of View or Function menus, or as a keyboard shortcut (usually, Control +, or for Mac Command +). <br />
* Set the screen window to full width<br />
* Use the zoom function or keyboard shortcut repeatedly to step up to a 200% increase. <br />
* Look at the main content, buttons, tabs and text entry fields and field labels.<br />
* Repeat with a different browser.<br />
====Common failures====<br />
* Is the default body text unusually small?<br />
* Does the main heading and body text increase in size? <br />
* Has any text that is part of a control, button, menu item or label increased in size? <br />
* Does any text overflow its space – for example, the text is too big for the button or menu tab, or width or depth of the column?<br />
* Can you read to the end of the line, or does some text disappear off the screen so that you have to scroll right to the end of the line?<br />
=====Note=====<br />
Some browsers can expand the text beyond 200% - this is not covered by the resize requirement as it is recognised that this will cause some of the failures described. It is also accepted that some horizontal scrolling may be necessary but see also 1.4.8 which is a AAA requirement. <br />
Users with more severe visual impairments who need larger text are likely to use screen magnifiers to increase text size above 200%. <br />
====References====<br />
*link to {appropriate section in Accessibility Requirements page http://www.w3.org/WAI/intro/people-use-web/principles#distinguishable} (doesn’t have a lot to say)<br />
*Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background. <br />
*Resize text: Understanding Success Criteria 1.4.4 (Level AA) {http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html}<br />
*Images of Text: Understanding Success Criteria 1.4.5 (Level AA) http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-text-presentation.html<br />
*Visual Presentation: Understanding Success Criteria 1.4.8 (Level AAA)http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-visual-presentation.html<br />
*link to {BAD example} No specific BAD examples – some reference to Text as image in relation to the phone number, and column width.<br />
<br />
===Window resize [15: probably not] [Ian to consider]===<br />
<span style="color:#808080;">EOWG notes.<br />
<br/> 5min: no.<br />
<br /> 15min: no. probably too complex an issue from preliminary eval</span><br />
...<br />
<br />
====Comments 2012-Nov-30====<br />
Ian to look into including this with the zoom one<br />
<br />
====Notes for discussion====<br />
*Scrolling: see Visual Presentation: Understanding Success Criteria 1.4.8 (Level AAA) includes:<br />
** Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.<br />
*Do we need to spell out the difference between zooming and resizing? Is resizing still important for people who use style sheets?<br />
*Do we still need to worry about IE6 which didn’t resize fixed font sizes?<br />
*Browsers are now hiding their menus – eg under the cogwheel icon, which is making it harder to know where to find the zoom option, however they seem to be reasonably consistent on keyboard shortcuts. Other options include pinch and zoom on trackpad or intellimouse<br />
<br />
====Comments 2012-Nov-30====<br />
There are two things to test:<br />
# Does text enlarge;<br />
# Don't controls remain accessible and content not overlap;<br />
Shawn: This is a maybe, conflicting views in forums and a hot topic, might be complicated to test.<br />
<br />
==More Thorough Evaluation==<br />
<br />
or: Next Steps<br />
<br />
or: Beyond Easy Checks<br />
<br />
or:...<br />
<br />
@@ point to WCAG-EM overview<br />
<br />
==Contributors==<br />
Thanks to:<br />
* Those who edited in December and January: Suzette, Sharron, Shawn, ...<br />
* Those who drafted checks 16-28 November:<br />
** Sharron for drafting {list sections!}<br />
** Suzette for drafting : Check usable with page zoomed and text enlarged, Check color contrast, Check color coding and shape coding, {?other sections}<br />
** Wayne for drafting {list sections!}<br />
** <span style="background:yellow;">{name} for drafting {section}</span><br />
* Andrew & Shawn for editing the [http://www.w3.org/WAI/EO/wiki/Web_Accessibility_Preliminary_Evaluation#Check_keyboard_access_and_visual_focus_.5Bmostly_drafted.5D keyboard access & visual focus section] in early Nov.<br />
* Ian, Suzette, Vicki, Sylvie, Helle, Shawn for working on an early draft at the [http://www.w3.org/2012/11/02-eo-minutes f2f in Nov].<br />
* Sharron for help making all the drafts and versions less confusing.<br />
* Wayne and Ian for sharing colleagues' related work.<br />
* Denis for edits to the old page content.<br />
<br />
<br /><hr /><br />
<span style="background:yellow;">'''''Important Note''''': For this draft we have some tool-specific guidance. However, there are potential issues with vendor-neutraility and we might need to address this a different way &mdash; for example, moving tool-specific guidance to WebPlatform Docs or the WAI-Engage wiki where people can easily add other tools.</span></div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Basics_with_Notes&diff=2485Basics with Notes2012-12-04T18:18:35Z<p>Jsutton2: /* Summary */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]] > [[Curriculum & Course Materials]] > [[Web Accessibility Basics]]<br />
<br />
__TOC__<br />
<br />
<span style="color: #808080;">{@@editorial notes: '''See the Discussion tab''' for audience analysis, etc.}</span><br />
<br />
<span style="color: #808080;">{@@ markup comments and notes like this...}</span><br />
<br />
<span style="color: #808080;">{@@editorial note: We'd like to '''use wording from approved WAI publications where it works''', rather than using lots of new wording on this page. (for consistency and to shortcut additional vetting needed)}</span><br />
<br />
<hr /><br />
<br /><br />
==Summary==<br />
<span style="color: #808080;">''[For [http://docs.webplatform.org/wiki/concepts/accessibility Web accessibility basics] page on Web Platform Docs]''</span><br />
<br />
<br />
Accessibility is making the Web work for people with a diverse range of abilities. Accessibility is essential for developers and organizations that want to create high quality websites and web tools, and not exclude people from using their products and services. Accessibility is vital to enable people with disabilities to participate equally on the Web. It is a legal requirement in some cases, and a best practice in all cases.<br />
<br />
<br />
'''Comments:'''<br />
* synonyms: essential, vital, crucial, critical<br />
* ...<br />
* @@ <span style="color: #808080;">I assume that starting each sentence with "Accessibility is" is intentional. This can certainly be effective, but I wonder if, rather than repeating the phrase, it might be better to write "Accessibility is," and then have a set of bullets. This could be done with slight, if any, modifications to current wording. {Jennifer}</span><br />
<br />
* ...@@ comment template <span style="color: #808080;">{name}</span><br />
<br />
==Disposition of Comments from survey==<br />
[https://www.w3.org/2002/09/wbs/35532/basics1/results July-Aug Survey results]<br />
<br />
* [SD] Editor's discretion:<br /> Location: h2 "Understand how people use the Web" secon bullet on Ms Laitinen<br /> Actual wording: "Ms. Laitinen is the chief accountant at an insurance company that uses web-based documents and forms over a corporate intranet. She is blind and, like many other people who are blind, she does not read braille." <br /> Proposed change: check that this description corresponds to the modified version of this storry, as, if I remember correctly, Ms Laitinen reads braille but she uses it only to check things, like spelling.<br />'''Disposition''': This matches the latest published draft. When we update that, we'll need to update that to match it. (I added comments to help us remember to do that.)<br />
* [SD] Editor's discretion:<br /> Location: h2 "Understand how people use the Web"In the following paragraphs, check that if the links to diversityof Web users or the following link text correspond to the agreed title, when it has been agreed.<br />'''Disposition''': This matches the latest published draft. When we update that, we'll need to update that to match it. (I added comments to help us remember to do that.)<br />
* [HB] Really good content whish I had time to translate it and use here.<br /> Priority: Editors discression.<br /> Location: Under h2 The web is for all people and especially under h3 "What is web accessibility"<br /> Suggested revision: Make this section shorter by removing 2nd paragraph: Web accessibility encompasses all disabilities that affect access to the Web, including people with auditory, cognitive, neurological, physical, speech, and visual disabilities. Accessibility includes people with impairments due to ageing."<br /> Rationale: When reading this intro section I feel that we are really saying the same thing in many different ways, and maybe too many<br /> I relly had to tell myself to continue reading. But I can live with it - not all people have heard this as many times as we have... <br />'''Disposition''': left it because we really need to counter the myth that accessibility is just about "blind people" by listing other disabilities. :)<br />
<br />
=Web Accessibility Basics - Version with Notes=<br />
<br />
On this page:<br />
*[[#The Web is for all people]]<br />
*[[#Understand how people use the Web]]<br />
*[[#Accessibility requirements]]<br />
*[[#The components of web accessibility]]<br />
*[[#Business case]]<br />
*[[#Learn more from W3C WAI]]<br />
*[[#References and acknowledgements]]<br />
<br />
<br />
<p>This page provides an overview of web accessibility and links to resources for more information. We suggest that you read through this whole page first, then go back and follow the links to learn more.</p><br />
<br />
==The Web is for all people==<br />
The Web is fundamentally designed to work for all people, whatever their hardware, software, language, culture, location, or physical or mental ability.<br />
<br />
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.<br />
<br />
However, when websites, web technologies, or web tools are badly designed, they can create barriers that exclude people from using the Web. For example, an inaccessible website could:<br />
* prevent people who are deaf from getting information from a podcast or video<br />
* prevent people with cognitive impairments from reading the content because of moving, blinking, or flickering images<br />
* prevent people with physical impairments from completing a transaction because they cannot use a mouse.<br />
<br />
===What is web accessibility===<br />
<p>Web accessibility means that people with disabilities can use the Web. More specifically, it means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web. For an introduction to <strong>why</strong> - the case for web accessibility, <strong>what</strong> - examples of web accessibility, and <strong>how</strong> to make your website and web tools accessible, see [http://www.w3.org/standards/webdesign/accessibility Accessibility - W3C].</p><br />
<br />
<p>Web accessibility encompasses all disabilities that affect access to the Web, including people with auditory, cognitive, neurological, physical, speech, and visual disabilities. Accessibility includes people with impairments due to ageing.</p><br />
<br />
<p>While accessibility focuses on people with disabilities, it also benefits others, such as people using mobile devices and people in limiting situations (e.g., a loud environment where they cannot hear audio). <strong>Accessibility supports social inclusion</strong> for people with disabilities, older people, mobile users, people in rural areas, people with low bandwidth connections, people with low literacy, etc. More information is in [[#Mobile users]] below, [[#Older people]] below, and [http://www.w3.org/WAI/bcase/soc.html#groups Web Accessibility Benefits People With and Without Disabilities].</p><br />
<br />
===Web accessibility is essential for equal opportunity===<br />
<p>The Web is increasingly an essential resource for many aspects of life: education, employment, government, commerce, health care, recreation, social interaction, and more. The Web is used not only for receiving information, but also for providing information and interacting with society. Therefore, it is essential that the Web be accessible in order to provide equal access and equal opportunity to people with disabilities. Indeed, the United Nations recognizes web accessibility as a basic human right. Learn more from [http://www.w3.org/WAI/bcase/soc#social Web Accessibility is a Social Issue] in the Social Factors page.</p><br />
<br />
==Understand how people use the Web==<br />
<p>Stories about people using the Web help to illustrate the everyday needs of people with disabilities. For example:</p><br />
<br />
<ul><br />
<li>Ms. Olsen attends middle school, and particularly likes her literature class. She has attention deficit hyperactivity disorder (ADHD) and dyslexia, and the combination leads to substantial difficulty in reading.</li><br />
<li>Ms. Laitinen is the chief accountant at an insurance company that uses web-based documents and forms over a corporate intranet. She is blind and, like many other people who are blind, she does not read braille.</li><br />
<li>Mr. Yunus is 85 years old and started to use the Web several years ago to stay in touch with family and friends, and to read about art history. He has reduced vision, hand tremor, and mild short-term memory loss due to ageing.</li><br />
</ul><br />
<p>More details on how these and others use the Web are in [http://www.w3.org/WAI/intro/people-use-web/stories Stories of Web Users].</p><br />
<br />
<p>People have a diverse range of abilities that impact how they use the Web. Some people have temporary impairments, some have age-related impairments, some have disabilities from birth, some develop disabilities from injuries or health conditions, and some have multiple disabilities. Some people's abilities change based on fatigue, inflammation, medication, etc. To learn about the diversity of abilities, and about the types of web accessibility barriers that people commonly encounter from poorly designed websites and web tools, see [http://www.w3.org/WAI/intro/people-use-web/diversity Diversity of Web Users].</p><br />
<p>People with disabilities access and navigate the Web in different ways. Sometimes people configure standard software and hardware according to their needs, and sometimes people use specialized software or hardware that help them perform certain tasks. To learn about the techniques and tools that people with disabilities use to interact with the Web, such as browser settings, text-to-speech, voice recognition, see [http://www.w3.org/WAI/intro/people-use-web/browsing Tools|Techniques|Diversity in Web Use].</p><br />
<br />
==Accessibility requirements==<br />
<p>In order for people with disabilities to be able to use the Web, there are certain things that websites and web tools need to do. These accessibility requirements fulfill four underlying principles:</p><br />
<br />
<ol><br />
<li style="padding-bottom:11px;"><strong>Perceivable</strong> information and user interface.<br />Accessibility requirements include: providing text alternative for images, providing captions or transcripts for video and audio, and providing sufficient color contrast between text and background.</li><br />
<li style="padding-bottom:11px;"><strong>Operable</strong> user interface and navigation.<br />Accessibility requirements include: enabling navigation using only a keyboard, providing meaningful hyperlinks, and allowing enough time for users to complete a task.</li><br />
<li style="padding-bottom:11px;"><strong>Understandable</strong> information and user interface.<br />Accessibility requirements include: making content readable, providing predictable functionality, and helping users avoid and correct mistakes.</li><br />
<li style="padding-bottom:11px;"><strong>Robust</strong> content and reliable interpretation.<br />Accessibility requirements include: maximizing compatibility with current and future tools (web browsers, assistive technologies, etc.).</li><br />
</ol><br />
<br />
<p><strong>To learn more about these web accessibility principles and requirements, see [http://www.w3.org/WAI/intro/people-use-web/principles Accessibility Principles].</strong></p><br />
<br />
<p>For a short introduction to 3 web accessibility issues (alternative text for images, keyboard input, and transcripts), see [http://www.w3.org/standards/webdesign/accessibility#examples What: Examples of Web Accessibility].</p><br />
<br />
==The components of web accessibility==<br />
The accessibility principles apply to the components introduced below. It is essential that the components of web development and interaction work together in order for the Web to be accessible to people with disabilities. The W3C Web Accessibility Initiative (WAI) provides guidelines that cover the accessibility requirements of the technical components.<br />
<br />
===Web Content===<br />
<p>Content is the information in a web page or web <strong>application</strong>, including: natural information such as text, images, and sounds; code or markup that defines structure, presentation, interaction, etc. Content requirements are covered in Web Content Accessibility Guidelines (<strong>WCAG</strong>).</p><br />
<br />
<p>The WCAG documents explain how to make web content (including web applications) more accessible to people with disabilities. To learn more about how WCAG is structured and about the supporting documents that provide practical advice for meeting accessibility requirements, see the <strong>[http://www.w3.org/WAI/intro/wcag.php WCAG Overview]</strong>.</p><br />
<br />
===Tools===<br />
The tools that we use to create and use web content can help or hinder web accessibility.<br />
<ul><br />
<li style="padding-bottom:11px;"><strong>Authoring tools</strong> are software and services that are used to create and edit websites; for example, content management systems (CMS), HTML editors, websites that let users add content (such as social media), and other tools. Tools should support people in making their web content accessible, and the tools should be accessible so that people with disabilities can use them. This is covered in Authoring Tool Accessibility Guidelines, see <strong>[http://www.w3.org/WAI/intro/atag.php ATAG Overview]</strong>.</li><br />
<li style="padding-bottom:11px;"><strong>Evaluation tools</strong> help check if websites meet standards. (Relevant information is in [http://www.w3.org/WAI/eval/selectingtools.html Selecting Web Accessibility Evaluation Tools].) </li><br />
<li style="padding-bottom:11px;"><strong> Web browsers</strong>, media players, and other &quot;user agents&quot; that access web content are covered in User Agent Accessibility Guidelines, see <strong>[http://www.w3.org/WAI/intro/uaag.php UAAG Overview]</strong>. </li><br />
<li style="padding-bottom:11px;"><strong>Assistive technologies</strong> are software or hardware that people with disabilities use to improve interaction with the Web, e.g., screen readers that read aloud web pages, voice recognition software, alternative keyboards, etc. (Introduced in [http://www.w3.org/WAI/intro/people-use-web/browsing.html Tools|Techniques|Diversity in Web Use].) </li><br />
</ul><br />
<br />
===People - web content creators and web users===<br />
<br />
<p>In addition to web content and tools, people are an important component of web accessibility.</p><br />
<br />
<p><strong>People who create content</strong> need to understand and implement accessibility. This includes developers, designers, authors, managers, etc., anyone who is involved with developing content (including applications), authoring tools, evaluation tools, browsers and other user agents.</p><br />
<br />
<p><strong>People who use the Web</strong> have different knowledge, experiences, and skill levels that affect accessibility; for example, how well a person knows how to use assistive technologies or adaptive strategies, and if they can get tools to meet their needs.</p><br />
<br />
<p>For more information on these web content, tools, and people components, see the [http://www.w3.org/WAI/presentations/components/Overview.php &quot;Components of Web Accessibility&quot; Presentation] or [http://www.w3.org/WAI/intro/components.php Essential Components of Web Accessibility].</p><br />
<br />
==Business case==<br />
<br />
In order for organizations to be willing to make the initial investment in accessibility, many need to understand the financial benefits of web accessibility. For an introduction, see [http://www.w3.org/WAI/presentations/bcase/Overview.php &quot;Web Accessibility is Smart Business&quot; Presentation].<br />
<br />
To learn more about the social, technical, financial, and legal and policy factors, see [http://www.w3.org/WAI/bcase/Overview.html Developing a Web Accessibility Business Case for Your Organization]. This set of pages presents different aspects of web accessibility along with guidance on developing a customized business case.<br />
<br />
For example, one aspect of the business case is reaching more users, including older users and mobile users.<br />
<br />
===Older users===<br />
<p>Older web users are an increasing market segment and an important target group for many businesses, governments, and other organizations. Many older people have age-related impairments that can affect how they use the Web, such as declining vision, physical ability, hearing, and cognitive ability. These issues overlap with the accessibility needs of people with disabilities. Thus, websites and tools that are accessible to people with disabilities are more accessible to older users as well. For more information, see [http://www.w3.org/WAI/older-users/Overview.php Web Accessibility and Older People: Meeting the Needs of Ageing Web Users].</p><br />
<br />
===Mobile Web===<br />
<p>With global mobile phone use at an all time high, there has been a surge of interest in developing websites that are accessible from a mobile device. Users of mobile devices and people with disabilities experience similar barriers when interacting with Web content. Websites can more efficiently meet both goals when developers understand the significant overlap between making a website accessible for a mobile device and for people with disabilities. For more information, see [http://www.w3.org/WAI/mobile/ Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices].</p><br />
<br />
==Learn more from W3C WAI==<br />
<br />
The W3C Web Accessibility Initiative (WAI) brings together people from industry, disability organizations, government, and research labs from around the world to develop guidelines and resources to help make the Web accessible to people with disabilities. We encourage you to look around the [http://www.w3.org/WAI/ WAI website] and find more information that is useful to you. See [http://www.w3.org/WAI/yourWAI Finding Your WAI ("way") to New Web Accessibility Resources].<br />
<br />
==References and acknowledgements==<br />
<p>Referencing this information: Most of the text on this page comes from other documents, which are linked within each section. For references, please use the source document. (See [http://www.w3.org/WAI/about/usingWAImaterial.html Using WAI Material: Permission to Use with Attribution].)</p><br />
<br />
<p>Editors: Shawn Lawton Henry, Shadi Abou-Zahra, Suzette Keith, Vicki Menezes Miller.</p><br />
<p>Contributors: Denis Boudreau, Sharron Rush, and other W3C WAI Education and Outreach Working Group ([http://www.w3.org/WAI/EO/ EOWG]) [http://www.w3.org/WAI/EO/EOWG-members participants].</p><br />
<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_WCAG_as_ISO&diff=1805Promoting WCAG as ISO2012-10-15T21:13:59Z<p>Jsutton2: </p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* [http://www.w3.org/QA/2012/10/wcag_20_is_now_also_isoiec_405.html blog post]<br />
* [http://www.w3.org/2012/07/wcag2pas-pr.html press release]<br />
* [https://twitter.com/w3c_wai/status/257842562205904896 tweet]<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012OctDec/0016.html WAI IG e-mail]<br />
* [http://www.w3.org/WAI/intro/wcag.php#iso ISO section in WCAG Overview]<br />
* [http://www.w3.org/WAI/WCAG20/wcag2faq#iso ISO section in WCAG FAQ]<br />
* [http://www.w3.org/News/2012#entry-9590 W3C news]<br />
<br />
== Audience & Messages ==<br />
...<br />
<br />
== Tweet ideas you can use==<br />
[https://twitter.com/w3c_wai/status/257842562205904896 w3c_wai tweet]<br />
<br />
WCAG 2.0 Approved as ISO/IEC 40500:2012 International Standard! blog post: http://bit.ly/wcag2isoB<br />
<br />
== Blog, newsletter, e-mail ideas you can use ==<br />
[http://www.w3.org/QA/2012/10/wcag_20_is_now_also_isoiec_405.html W3C Q&A blog post]<br />
<br />
<br /><br /><br />
<hr /><hr /><br />
<br />
== EOWG record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
* [http://www.w3.org/QA/2012/10/wcag_20_is_now_also_isoiec_405.html W3C Q&A blog post]<br />
...<br />
<br />
=== Mailing lists, Groups (e.g., LinkedIn, Google, etc) ===<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012OctDec/0016.html WAI IG e-mail]<br />
* On October 15, I posted the WAI-IG message to two mailing lists. The references are:<br />
** [WebAIM post http://webaim.org/discussion/mail_thread?thread=5556]<br />
and<br />
** [Public WAI-Engage post http://lists.w3.org/Archives/Public/public-wai-engage/2012Oct/0000.html]<br />
(Jennifer)<br />
<br />
=== Tweets ===<br />
* [https://twitter.com/w3c_wai/status/257842562205904896 w3c_wai tweet]<br />
...<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
...<br />
<br />
==== To Do: ====<br />
...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Accessibility_in_Courses&diff=1774Promoting Accessibility in Courses2012-10-09T23:08:38Z<p>Jsutton2: /* 2012 EOWG Recent Contacts */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">'''IMPORTANT:''' The Training pages are ''not ready for promotion yet''! We still need to approve and publish them.<br/>When they are ready, we'll send e-mail to WAI IG list and [http://www.w3.org/WAI/about/announcements other announcements].</span><br />
<br />
<br />
== Resources & Pointers ==<br />
<br />
* Main document: [http://www.w3.org/WAI/training/ Developing Web Accessibility Presentations and Training]<br />
* Old draft: [http://www.w3.org/WAI/EO/Drafts/promos/courses.php Integrating Web Accessibility in Courses] <br />
* Related Materials: [http://www.w3.org/WAI/EO/Drafts/training/ Training Resource Suite]; [http://www.w3.org/community/webed/wiki/Main_Page#Accessibility Accessibility Modules on Web Education Community Group]<br />
<br />
== Audience & Messages ==<br />
=== Audience ===<br />
<p>We have identified <strike> two </strike> three main audience types. First is the general public which includes providers of informal meet-ups and continuing education of the kind that occurs at conferences and "unconferences." The second is the academic community. Messaging will overlap, but in some instances will be specific to one group or the other.</p><br />
* General Audience - may need foundational messaging about accessibility issues as well as specifics about the materials available. May not know much about how PWD use the web or the need for accessibility. <br />
* Professional Audience - May have strong understanding of one or two aspects of web accessibility, but requires focused training to meet the accessibility requirements of their job. This group includes advocates, managers, developers, graphic artists etc. Focus is on missing knowledge: accessibility techniques for web developers, technology issues for disability advocates, social responsibility and requirement issues for managers. <br />
* Academic Audience - should be more aware of need for educational inclusion. Messaging may be more focused on industry trends, skills development, creating technical graduates who are ready to meet requirements of the information technology industry.<br />
<br />
=== Messages ===<br />
<p>An important aspect of high quality Web courses is making the Web accessible to people with disabilities. [or: An important aspect of high quality Web courses is including instruction on developing Web sites that are accessible to people with disabilities.] ''This principle applies whether the audience consists of web developers, graphic designers, managers, advocates or college students.''</p><br />
<br />
<p> ''The Suite provides several presentation outlines that enable the presenter to address a variety of skill levels, interests and time constraints.''</p><br />
<br />
== Tweet ideas you can use==<br />
...<br />
<br />
== Blog, newsletter, e-mail ideas you can use ==<br />
Subject/Headline: '''W3C WAI materials to help you update your web course for accessibility'''<br />
<br />
@@ students get current info, zingy @@<br /><br />
An important aspect of high quality Web courses is making the Web accessible to people with disabilities. [<em>or:</em> An important aspect of high quality Web courses is including instruction on developing Web sites that are accessible to people with disabilities.] To help you integrate accessibility in your Web courses, W3C WAI provides materials that you can use for lecture, activities, and student study.<br />
See Developing Web Accessibility Presentations and Training at http://www.w3.org/WAI/training/<br />
<br />
@@ It's like open source courseware @@<br />
<br />
'''Web accessibility is an important social, technical, and business issue.<br />
'''<br />
<p>Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web. Currently most Web sites and Web software have accessibility barriers that make it difficult or impossible for many people with disabilities to use the Web. Teaching Web designers, developers, and authors accessibility is a key factor in making Web sites and software accessible, so that people with disabilities can use and contribute to the Web more effectively.</p><br />
<p>@@consider integrating shorter in first bit @@<br /> Web courses that are up-to-date with the latest trends in the industry include accessibility. Accessibility is being requested more and more in Web site development, as people realize the many benefits of making the Web accessible&mdash;for people with and without disabilities, and for Web site owners&mdash;and as legal requirements increase. Social, technical, financial, and legal factors of Web accessibility are described in the Web Accessibility Business Case at: http://www.w3.org/WAI/bcase/Overview.html</p><br />
<br />
'''W3C WAI provides material to support Web accessibility.'''<br />
...<br />
<br />
'''You can use WAI material for your Web accessibility instruction.'''<br />
<br />
<p>To help you incorporate accessibility in your upcoming Web design and development courses, we put together a resource suite @@<br />
<p>* @@use it - make your students happy</p><br />
<p> We hope that you will @@bookmark &quot;@@training resource suite&quot; and come back to it as you prepare Web course syllabus and materials.</p><br />
<p>Thank you for your attention to Web accessibility.</p><br />
<br />
<br />
@@'' College Instructors of Web Technologies, User Interface Design or Human Factors''@@<br />
<p>Do you want to integrate accessibility for people with disabilities into your core curriculum, but are not sure where to start? Consider using, [http://www.w3.org/WAI/training/ Developing Web Accessibility Presentations and Training], a W3C publications. This resource provides several detailed presentation outlines. These can be used for a variety of audiences, skill levels and time constraints. </p><br />
<p>The outline, [http://www.w3.org/WAI/training/presentation-outlines#design Web Accessibility Design], is an excellent one-week introduction to accessibility for students in computer science, information technology or human factors psychology. It can be presented in two lecture hours with an optional 2 to 3 hour lab. This resource comes with several suggested readings for the instructor's preparation. Many of these are excellent reading assignments for students. Web standards originate at the W3C, so many of the referenced documents are primary source materials.</p><br />
<br />
== Conference Presentation Possibilities==<br />
[http://www.w3.org/WAI/EO/wiki/Contacts_for_promotion Overall Contacts for Promotion]<br />
* [http://www.colorado.edu/ATconference/ Accessing Higher Ground] in November in Colorado. Any more room? See if anyone we know has had a paper accepted who could mention the training suite. Howard Kramer and Glenda S. may have ideas. See [http://www.colorado.edu/ATconference/about2012.html#contactus Accessing Higher Ground - Accessible Media, Web and Technology ConferenceContact page] -- November 12 - 16, 2012 (Note that Derek is keynoting; perhaps he might mention the training suite) (JS)<br />
* Maybe a [http://www.csun.edu/cod/conference/index.php CSUN] presentation for 2013<br />
* AccessU for 2013 could do a "train the trainers" track and use the training suite (SR)<br />
* South by Southwest (SR)<br />
* South by Southwest Edu open for papers until the end of this year, helping K -- 12 teachers too, focuses on those who are making curriculum products (SR)<br />
* [http://www.ozewai.org/ OZeWAI conference] - annually in December<br />
* Meetups and unconferences for short workshops -- especially start with these two, at the general level (JS):<br />
** [http://www.a11ycamp.org/ a11y Camp] <br />
** [http://www.accessibilitycamp.org/ Accessibility Camp]<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== Old and related material ===<br />
* Old material:<br />
** [http://www.w3.org/WAI/EO/Drafts/promos/courses.php Integrating Web Accessibility in Courses]<br />
** [http://www.w3.org/WAI/EO/changelogs/cl-promo-courses.html Requirements and Changelog for Promotional Campaign to Web Development Course Instructors]<br />
* '''Non-W3C''' related info:<br />
** [http://uiaccess.com/teachDI.html Teach Digital Inclusion] presentation (with draft video) encouraging instructors to teach digital inclusion in their ICT courses<br />
<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
UN Enable Newsletter (VMM)<br />
<br />
=== Mailing lists ===<br />
* Access Technology Higher Education Network [http://mailman1.u.washington.edu/mailman/listinfo/athen-list ATHEN email list]<br />
* Association on Higher Education and Disability [http://www.ahead.org/membership/mailing-list-policy | AHEAD email list]<br />
* US Federal Government Webmaster lists [http://www.howto.gov/communities How-To.Gov Communities]<br />
* WAI-Engage Community Group [mailto:public-wai-engage@w3.org WAI-Engage Group List]<br />
* Leadership Exchange in Arts and Disability [mailto:culturalartsaccess@yahoogroups.com LEAD mailing list]<br />
* Web Accessibility Network of Australian Universities [http://wanau.org/ WANAU]<br />
<br />
=== Tweets ===<br />
...<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
To do:<br />
* Contact University of Geneva (VMM)<br />
* Contact set of UN organizations in Geneva (VMM)<br />
* WebAim Thread from October 2012: [http://webaim.org/discussion/mail_thread?thread=5548 Web accessibility included in a college degree curriculum] (Jennifer, 2012_10_09)<br />
==== Done: ====<br />
...<br />
<br />
==== To Do: ====<br />
<p>Outcome of brainstorming of Outreach Subcommittee Meeting Aug 15, 2012 plus additions. Note that many of these ideas are U.S.-centric and we will ask EO for more global perspective</p><br />
<br />
* Finalize outreach plan and present to EO by Aug 24, 2012 (JS, WD, SR)<br />
* Glenda Sims -- any associations? Suggestions of newsletters or conferences? (SR)<br />
* [http://www.webteacher.ws/ Web Teacher -- Virginia DeBolt] (SR)<br />
* [http://www.mediaaccess.org.au/learn 6-week course on building websites with WCAG 2.0 compliance] Professional Certificate in Web Accessibility from Media Access Australia. <br />
* Terry Thompson<br />
* Sarah Bourne in MA for government curricula connections<br />
* CA system -- both UC and state (WD)<br />
* Ideas about TX systems? (SR)<br />
* Maybe set up an online one-hour seminar to go over how to use this training suite? Volunteer(s) to teach? How to arrange payments and assure platform accessibility?<br />
* Post announcement to both the ATHEN and AHEAD email Lists (JS)<br />
* Craft email message for the WAI-Engage email list encouraging discussion of the training suite on the [http://www.w3.org/community/wai-engage/ WAI-Engage Wiki]. Capture tips and tricks for conducting effective training sessions using the suite. (SR with help from EO)<br />
* Getting materials adopted into an official curriculum -- Wayne can offer guidance about that; what they did at Long Beach, integrated into learning materials and modules<br />
* Develop a press release draft related to Longbeach and saying: "Here is what they did at Long Beach, if you want to do the same, use these resources." (SR)<br />
* [http://www.rit.edu/%7Eeasi/index.htm Norm Coombs and EASI]<br />
* John Gunderson at U. of IL<br />
<br />
===== Additional Ideas extracted/Copied from EO WG Promotion Wiki Pages =====<br />
<br />
* WSG Announcements (If you have an event, resource or relevant job you'd like posted (from any country), please let me know - russ at maxdesign.com.au)<br />
[http://www.maxdesign.com.au/category/light-reading/ Links for light reading] Max Design / Russ Weakley - distributed through [http://webstandardsgroup.org/ Web Standards Group]<br />
* [http://www.webstandards.org/ Web Standards Project (WasP)]<br />
* [http://www.d.umn.edu/itss/training/online/webdesign/ Web Design References, UMD] - Laura Carlson. [http://www.d.umn.edu/itss/training/online/webdesign/urlform.html<br />
form to Suggest a Link]<br />
* WritersUA monthly user assistance update resource_directory@writersua.com contact: Joe W.<br />
* LinkedIn Groups - Jennison A.<br />
* [http://webaim.org/discussion/ The WebAIM Email Discussion List]<br />
* [http://webaim.org/newsletter/ The WebAIM Newsletter] (Jared Smith) <br />
* [http://blog.knowbility.org/ Knowbility Blog, Universally Designed] - posters: Sharron, Wayne<br />
* [http://accessibilityindia.wordpress.com/ Accessibility India Maxability blog] accessibilityindia @ gmail.com<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (has contact info: Jennifer, Shawn)<br />
* [http://www.paciellogroup.com/blog/ The Paciello Group Blog]<br />
* [http://www.highedweb.org/<br />
Higher Education Web Professionals Association (HighEdWeb)]<br />
* [http://www.iwanet.org/ International Webmasters Association/HTML Writers Guild (IWA/HWG) Is this still active enough?<br />
* [http://www.wdda.org/ Web Design and Developers Association]<br />
* [http://wipa.org.au/ Web Industry Professionals Association Incorporated (WIPA) of Australia]<br />
* [http://webprofessionals.org/ World Organization of Webmasters (WOW)] <br />
* [http://www.wait-till-i.com Chris Heilmann's site]<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=WCAG-EM_review&diff=1697WCAG-EM review2012-09-29T19:59:04Z<p>Jsutton2: /* Comments that probably don't need discussion */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
__TOC__<br />
Links:<br />
* [http://www.w3.org/TR/WCAG-EM/ WCAG-EM document]<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0414.html Call for Review e-mail 20 Sept]<br />
* [http://www.w3.org/WAI/ER/2011/eval/track/issues/open Open Issues]<br />
<br />
Reminder: EOWG will focus on the types of questions below. If you have comments on specific technical points in the document, you can submit them directly yourself -- that is, e-mail them to public-wai-evaltf@w3.org by 20 October.<br />
<br />
If you're not sure, feel free to put your comments here and the Group will decide if they are ones you should send yourself.<br />
<br />
==EOWG Comments specifically requested==<br />
The following questions have been asked by the WCAG-EM Working Group for consideration and comment from EOWG. Please consider these items and comment below.<br />
#Is it clear that this set of methodologies is only for websites after they are built and does not address methodologies that might be used prior to and during development? If not, please suggest ways to clarify the scope.<br />
#How should we communicate the importance of evaluating throughout website development, not just at the end?<br />
#How much should we refer to and link to existing material as reference and how much should we include directly in the new material? Balance the inconvenience of jumping back and forth between existing documents against our reluctance to unnecessarily duplicate information.<br />
#What specific revisions will make the document more readable and usable?<br />
#Are there any major considerations that we have overlooked or misrepresented?<br />
#How should we align the WCAG-EM work with the [http://www.w3.org/WAI/EO/wiki/Web_Accessibility_Preliminary_Evaluation Preliminary Evaluation document] now in process at EOWG?<br />
<br />
(Note: We plan to separately provide guidance for the developers of evaluation tools.)<br />
<br />
==Comments for discussion==<br />
* ...comment <span style="color: #808080;">{Wayne Dick}</span><br />
(minor) Relied Upon - Just hangs there without inclusion in the context of accessibility supported.<br />
<br />
(Med) The note to (Web Applications): It may not be feasible to exhaustively examine all possible settings, but sampling should apply just as any website.<br />
<br />
(Very Important) Methodology Requirement 1.d: This requirement appears to claim that the website owner and evaluator are free to<br />
choose which users may be excluded. Human rights do not work that way. What reasonable base technologies are required<br />
for conformance? This is particularly disturbing within the context of intranets where employers may choose to limit users to assistive technologies the employer can purchase cheaply. The note at the end is not sufficient.<br />
<br />
Example, many sites prescribe large print with high contrast to be a universal cure for low vision. This discounts the need for albinos to have lower luminosity. Without high luminosity, high contrast is not possible.<br />
<br />
* ...comment <span style="color: #808080;">{Wayne Dick}</span><br />
(important) 3.1.5 Step d, appeared to invite employer determined prescription of assistive techonolgy and accessibility support. The result will be employer defined necessary<br />
employment discrimination.<br />
<br />
* ...comment <span style="color: #808080;">{Wayne Dick}</span><br />
3.1.5 Step 3. The evaluation commissioner, must be informed that if the self defined sufficient techniques are used then a future accessibility audit may ask for a proof of<br />
sufficiency.<br />
<br />
* ...comment <span style="color: #808080;">{Wayne Dick}</span><br />
Throughout 3.1.5 PDF and Silver light are <br />
basic web technologies. They are no more <br />
technologie than docx or raw text. They <br />
as basic web technologies. The accessibility <br />
open question.<br />
<br />
This issue is particularly important if this document is going to be normative. I do specific reference to Adobe or Microsoft products as basic web technologies is serious vendor preference.<br />
<br />
* ...comment <span style="color: #808080;">{Vicki}</span><br />
3.3 Step 3: Select a Representative Sample<br />
(First sentence)<br />
"While ideally every web page of a web site is evaluated, usually this is not possible on most web sites."<br />
<br />
I think it is too strong to say "usually this is not possible". It may sound like we are contradicting what we are hoping to achieve. Suggested text:<br />
"While ideally every web page of a website should be evaluated, this may not be possible for very large websites."<br />
* ...comment <span style="color: #808080;">{Vicki}</span><br />
Responding to the term "with reasonable confidence": I have no problem with the term. Alternatively, if the above term is a point of discussion, you could simply modify the sentence to "that is representative of the entire target website".<br />
<br />
* ...comment <span style="color: #808080;">{Wayne Dick}</span><br />
3.3 Step 3: Select a Representative Sample <br />
website with many heterogeneous sub-<br />
university example, the sample selection <br />
include users. Focus groups are an effective <br />
probably necessary.<br />
<br />
Large heterogenous sites behave more like a set of independent sites placed under one URL. As such it is important to organize focus groups within the different autonomous site owners to determine usage patterns and prioritize pages for evaluation. When organizing the CSU System, 23 Campuses, each having more than 50 academic departments, and more administrative departments, we found that the IT unit could not get a handle on usage patterns on its own. Individual site owners had to give direct input on priority and usage. Example: At CSU Long Beach the Computer Science lab invokes the Computer Science Department Website every time a student logs into a lab machine. That makes the Computer Science Department the most referenced site on the Campus. But it is not the most important.<br />
<br />
* ...comment <span style="color: #808080;">{Vicki}</span><br />
2.5 Involving Users (Optional)<br />
Second last sentence.<br />
"While not required, it is strongly recommended to involve real people covering a wide range of abilities...."<br />
Suggest removing "real".<br />
<br />
* ...comment <span style="color: #808080;">{Vicki}</span><br />
3.1.4 Methodology Requirement 1.d: <br />
<br />
Third paragraph: second last sentence.<br />
"For example, ….., then the website is effectively not accessible for some users."<br />
Suggest adding something about conformance for emphasis e.g., "and therefore does not conform to the specified conformance level of WCAG 2.0. (3.1.3 Step 1.c.)"<br />
<br />
* ...comment <span style="color: #808080;">{Vicki}</span><br />
Feedback requested on the definition on "Common Functionality". <br />
<br />
Having read through the document, I don’t have a problem with the term "common functionality. However, it might pose a question mark to some. Therefore, I’ve put forth a few options below depending on what you mean and if you wish to be more specific:<br />
<br />
If it is the general functionality of the site, you could simply leave out the word "common" or use "basic functionality"<br />
<br />
If "common functionality" has a more technical connotation (referring to the style sheets, javascript, classes, i.e., the technical mandatory requirements for multiple device support and functionality), leave it as "common"<br />
<br />
Another suggestion in the line of "common" and "key" is “core”.<br />
<br />
Suggestion to modify the description (in line with the "Note"):<br />
Functionality of a website includes tasks that users of a website perform in order to achieve a goal.<br />
<br />
<br />
* ...comment <span style="color: #808080;">{Suzette - readability}</span><br />
Re point 4: readability and usability, plus section 1.1 scope and 1.2 audience. I think this is a difficult read for the intended audience. I have no problem with clarifying the scope that this is what educationalists call summative assessment (like the final exam!) rather that formative assessment (feedback you can learn from. To improve usability I would suggest there is a need for better tailored use cases that match 1.2 and are then addressed consistently. There seem to be some examples included about commerce but I think it needs to use a better defined range - that better capture the context of the audience be it large scale government sites, large commercial sites, banks and utilities, and big agencies through to smaller operators eg a local school, a local charity, small organic food retailer.<br />
<br />
==Comments that probably don't need discussion==<br />
* ...comment <span style="color: #808080;">{Vicki}</span><br />
3.1.2 Step 1.b.<br />
<br />
In-Depth Analysis.<br />
<br />
End of last sentence is missing a fullstop.<br />
<br />
* ...comment <span style="color: #808080;">{Vicki}</span><br />
3.2.3<br />
"Note: This step is intended to identify groups of web page instances, including in web applications."<br />
<br />
Suggest drop the "in" as in "including web applications" or add "including those in web applications".<br />
<br />
<br />
* Jennifer (2012_09_29): Submitted this [http://lists.w3.org/Archives/Public/public-wai-evaltf/2012Sep/0088.html comment on WACEM 1.0 -- use of internal links] independently -- meaning that I did not post on behalf of EOWG.<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=1625Promoting Make Presentations Accessible2012-09-21T00:04:57Z<p>Jsutton2: /* To Do: */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French: [http://www.braillenet.org/accessibilite/wcag20/accessible_fr.html <span lang="fr">Comment rendre des présentations accessibles à tous]<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L - 20 Feb, Jennifer<br />
<br />
=== Tweets ===<br />
<br />
* #w4a2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265062935044098 WAI tweeted 26 March 2012)<br />
* #www2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265412890988544 WAI tweeted 26 March 2012)<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
* [https://twitter.com/#!/shawn_slh/status/175672283216621568 #CSUN12 (2 March, shawn_slh)] in reply to tweet about inaccessible presentations<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://www.w4a.info/2012/open-data/crc-instructions W4A instructions (8th step)]<br />
* [http://sxsw.com/interactive SXSW interactive] more than 1500 Speakers and Panelists - 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* AccessU at CSUN presenters by email from Sharron, Feb 2012 Jennifer<br />
<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* eAccess 12 - sent to organizer, 16 April , Jennifer<br />
* W4A 2012 - sent email to General Co-Chairs Julio Abascal & Markel Vigo, 26 March, Shawn (and Shadi before that :/<br />
* WWW 20120 - sent e-mail to conference contact, 20 Feb, Shawn<br />
* ICCHP - ?, Shadi<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
* UN Enable Newsletter - 27 February 2012 - Vicki<br />
* Promoting the use in own organisation (National Board of Social Services) planning to expand to rest of organization: Ministry of Social Affairs and Integration and translate into Danish - 16 March - Helle<br />
* presented at [http://barcampcanberra.org/ Canberra Barcamp 2012] - 17 March - Andrew<br />
* Noticed this recent project, [http://www.scie.org.uk/publications/accessibleevents/index.asp Making Events Accessible] launched by Social Care Institute for Excellence. On March 25, sent Feedback to request that "Making Presentations..." be included (Jennifer).<br />
Note that some of this information was taken from [http://g3ict.org/resource_center/newsletter/news/p/newsletterId_/id_376 a G3ICT post] and initially posted to this Wiki page on August 21, 2012 by Jennifer. Then, Jennifer sent individual emails to organizers of these conferences on August 22, 2012:<br />
* [http://a11y-bos.org/ Boston Accessibility Conference], September 15, 2012<br />
* [http://a11yldn.org.uk/ Accessibility Camp London UK], September 19, 2012<br />
* [http://www.twitter.com/a11ycampnyc Accessibility Camp New York City] (on Twitter), September 22, 2012<br />
* [http://a11yldn.org.uk/ Accessibility Camp DC], October 13, 2012 (contact is John Croston -- Jennifer)<br />
* [http://www.accessibilitycampla.org/ Accessibility Camp Los Angeles], October 20, 2012<br />
* [http://www.accessibilitycampto.org/ Accessibility Camp Toronto], November 17, 2012<br />
* [http://a11ymtl.org/en Accessibility Camp Montreal], November 23, 2012 <br />
<br />
Jennifer also sent the same [http://lists.w3.org/Archives/Public/public-wai-engage/2012Aug/0003.html message] to the public WAI-Engage email list on august 22, 2012.<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* AccessU conferences held by Knowbility next: May 15 to 17 in Austin<br />
* ATIA, Jennifer, Feb 22, 2012 - but would be good to follow up later<br />
* European eAccessibility Forum<br />
* Accessibility barcamps/unconferences including these two main sites:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.facebook.com/events/255649237860688/ A11y Camp Tokyo on Facebook], Contact is Makoto Ueki -- April 19, 2012 (Jennifer)<br />
*** Via Makoto Ueki: The 3rd Accessibility Camp Tokyo will be held on 12th October. See [https://www.facebook.com/a11ytokyo?ref=ts this page on Facebook] (Jennifer, 2012_09_20)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Via @a11ysea, the 2nd #Accessibility Camp Seattle is June 2 & 3rd (Jennifer, March 9, 2012)<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=1624Promoting Make Presentations Accessible2012-09-21T00:02:56Z<p>Jsutton2: /* Conferences */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French: [http://www.braillenet.org/accessibilite/wcag20/accessible_fr.html <span lang="fr">Comment rendre des présentations accessibles à tous]<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L - 20 Feb, Jennifer<br />
<br />
=== Tweets ===<br />
<br />
* #w4a2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265062935044098 WAI tweeted 26 March 2012)<br />
* #www2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265412890988544 WAI tweeted 26 March 2012)<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
* [https://twitter.com/#!/shawn_slh/status/175672283216621568 #CSUN12 (2 March, shawn_slh)] in reply to tweet about inaccessible presentations<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://www.w4a.info/2012/open-data/crc-instructions W4A instructions (8th step)]<br />
* [http://sxsw.com/interactive SXSW interactive] more than 1500 Speakers and Panelists - 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* AccessU at CSUN presenters by email from Sharron, Feb 2012 Jennifer<br />
<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* eAccess 12 - sent to organizer, 16 April , Jennifer<br />
* W4A 2012 - sent email to General Co-Chairs Julio Abascal & Markel Vigo, 26 March, Shawn (and Shadi before that :/<br />
* WWW 20120 - sent e-mail to conference contact, 20 Feb, Shawn<br />
* ICCHP - ?, Shadi<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
* UN Enable Newsletter - 27 February 2012 - Vicki<br />
* Promoting the use in own organisation (National Board of Social Services) planning to expand to rest of organization: Ministry of Social Affairs and Integration and translate into Danish - 16 March - Helle<br />
* presented at [http://barcampcanberra.org/ Canberra Barcamp 2012] - 17 March - Andrew<br />
* Noticed this recent project, [http://www.scie.org.uk/publications/accessibleevents/index.asp Making Events Accessible] launched by Social Care Institute for Excellence. On March 25, sent Feedback to request that "Making Presentations..." be included (Jennifer).<br />
Note that some of this information was taken from [http://g3ict.org/resource_center/newsletter/news/p/newsletterId_/id_376 a G3ICT post] and initially posted to this Wiki page on August 21, 2012 by Jennifer. Then, Jennifer sent individual emails to organizers of these conferences on August 22, 2012:<br />
* [http://a11y-bos.org/ Boston Accessibility Conference], September 15, 2012<br />
* [http://a11yldn.org.uk/ Accessibility Camp London UK], September 19, 2012<br />
* [http://www.twitter.com/a11ycampnyc Accessibility Camp New York City] (on Twitter), September 22, 2012<br />
* [http://a11yldn.org.uk/ Accessibility Camp DC], October 13, 2012 (contact is John Croston -- Jennifer)<br />
* [http://www.accessibilitycampla.org/ Accessibility Camp Los Angeles], October 20, 2012<br />
* [http://www.accessibilitycampto.org/ Accessibility Camp Toronto], November 17, 2012<br />
* [http://a11ymtl.org/en Accessibility Camp Montreal], November 23, 2012 <br />
<br />
Jennifer also sent the same [http://lists.w3.org/Archives/Public/public-wai-engage/2012Aug/0003.html message] to the public WAI-Engage email list on august 22, 2012.<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* AccessU conferences held by Knowbility next: May 15 to 17 in Austin<br />
* ATIA, Jennifer, Feb 22, 2012 - but would be good to follow up later<br />
* European eAccessibility Forum<br />
* Accessibility barcamps/unconferences including these two main sites:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.facebook.com/events/255649237860688/ A11y Camp Tokyo on Facebook], Contact is Makoto Ueki -- April 19, 2012 (Jennifer)<br />
<br />
*** Via Makoto Ueki: The 3rd Accessibility Camp Tokyo will be held on 12th October. See [https://www.facebook.com/a11ytokyo?ref=ts this page on Facebook]** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Via @a11ysea, the 2nd #Accessibility Camp Seattle is June 2 & 3rd (Jennifer, March 9, 2012)<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Mobile_Accessibility&diff=1595Promoting Mobile Accessibility2012-09-17T23:48:34Z<p>Jsutton2: </p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling everyone about the updated Mobile Accessibility information.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
=== Resources & Pointers ===<br />
<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0351.html e-mail 10 Sept]<br />
* [https://twitter.com/w3c_wai/status/245154087677595648 tweet 10 Sept]<br />
* [http://www.w3.org/QA/2009/12/share_resources_supporting_the.html Share Resources Supporting the Web Accessibility Business Case] blog post from a while ago<br />
<br />
=== Audiences & Messages for Outreach ===<br />
<br />
...<br />
<br />
=== Blog & newsletter ideas you can use ===<br />
...<br />
<br />
The W3C Web Accessibility initiative (WAI) has published updated documents related to mobile accessibility. They cover how mobile web accessibility is addressed in existing W3C standards/guidelines, and how the overlap between mobile web design/development and accessibility strengthens the business case. See the Mobile Accessibility Resources e-mail at http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0351.html<br />
<br />
=== Tweet ideas you can use ===<br />
Mobile #Accessibility - making mobile web & apps work for people with disabilities http://bit.ly/maWAI (plus business case updates)<br />[https://twitter.com/w3c_wai/status/245154087677595648 WAI tweet 10 Sept]<br />
<br />
=== E-mail ideas you can use ===<br />
<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0351.html WAI-IG e-mail 10 Sept]<br />
<br />
=== EOWG planning & record keeping ===<br />
<br />
On September 10, 2012, Jennifer sent:<br />
* WAI-IG email message to the WebAIM list<br />
* WAI-IG email message to 17 "undisclosed recipients."<br />
* One of those recipients was Henny Swan. This message was a start toward my Action item 208. I then followed up, about three hours later, with a more personal message.<br />
* WAI-IG message to the Public WAI-Engage email list; I highlighted the mobile business case.<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Mobile_Accessibility&diff=1590Promoting Mobile Accessibility2012-09-11T14:29:09Z<p>Jsutton2: /* EOWG planning & record keeping */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
=== Resources & Pointers ===<br />
<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0351.html e-mail 10 Sept]<br />
* [https://twitter.com/w3c_wai/status/245154087677595648 tweet 10 Sept]<br />
* [http://www.w3.org/QA/2009/12/share_resources_supporting_the.html Share Resources Supporting the Web Accessibility Business Case] blog post from a while ago<br />
<br />
=== Audiences & Messages for Outreach ===<br />
<br />
...<br />
<br />
=== Blog & newsletter ideas you can use ===<br />
...<br />
<br />
The W3C Web Accessibility initiative (WAI) has published updated documents related to mobile accessibility. They cover how mobile web accessibility is addressed in existing W3C standards/guidelines, and how the overlap between mobile web design/development and accessibility strengthens the business case. See the Mobile Accessibility Resources e-mail at http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0351.html<br />
<br />
=== Tweet ideas you can use ===<br />
Mobile #Accessibility - making mobile web & apps work for people with disabilities http://bit.ly/maWAI (plus business case updates)<br />[https://twitter.com/w3c_wai/status/245154087677595648 WAI tweet 10 Sept]<br />
<br />
=== E-mail ideas you can use ===<br />
<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0351.html WAI-IG e-mail 10 Sept]<br />
<br />
=== EOWG planning & record keeping ===<br />
<br />
On September 10, 2012, Jennifer sent:<br />
* WAI-IG email message to the WebAIM list<br />
* WAI-IG email message to 17 "undisclosed recipients," including Henny. This is a start toward my Action item 208.<br />
* WAI-IG message to the Public WAI-Engage email list; I highlighted the mobile business case.<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Mobile_Accessibility&diff=1589Promoting Mobile Accessibility2012-09-10T22:48:21Z<p>Jsutton2: /* EOWG planning & record keeping */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
=== Resources & Pointers ===<br />
<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0351.html e-mail 10 Sept]<br />
* [https://twitter.com/w3c_wai/status/245154087677595648 tweet 10 Sept]<br />
* [http://www.w3.org/QA/2009/12/share_resources_supporting_the.html Share Resources Supporting the Web Accessibility Business Case] blog post from a while ago<br />
<br />
=== Audiences & Messages for Outreach ===<br />
<br />
...<br />
<br />
=== Blog & newsletter ideas you can use ===<br />
...<br />
<br />
The W3C Web Accessibility initiative (WAI) has published updated documents related to mobile accessibility. They cover how mobile web accessibility is addressed in existing W3C standards/guidelines, and how the overlap between mobile web design/development and accessibility strengthens the business case. See the Mobile Accessibility Resources e-mail at http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0351.html<br />
<br />
=== Tweet ideas you can use ===<br />
Mobile #Accessibility - making mobile web & apps work for people with disabilities http://bit.ly/maWAI (plus business case updates)<br />[https://twitter.com/w3c_wai/status/245154087677595648 WAI tweet 10 Sept]<br />
<br />
=== E-mail ideas you can use ===<br />
<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JulSep/0351.html WAI-IG e-mail 10 Sept]<br />
<br />
=== EOWG planning & record keeping ===<br />
<br />
On September 10, 2012, Jennifer sent:<br />
* WAI-IG email message to the WebAIM list<br />
* WAI-IG email message to 17 "undisclosed recipients," including Henny. This is a start toward my Action item 208.<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=1397Promoting Make Presentations Accessible2012-08-22T23:27:33Z<p>Jsutton2: /* Done: */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French: [http://www.braillenet.org/accessibilite/wcag20/accessible_fr.html <span lang="fr">Comment rendre des présentations accessibles à tous]<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L - 20 Feb, Jennifer<br />
<br />
=== Tweets ===<br />
<br />
* #w4a2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265062935044098 WAI tweeted 26 March 2012)<br />
* #www2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265412890988544 WAI tweeted 26 March 2012)<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
* [https://twitter.com/#!/shawn_slh/status/175672283216621568 #CSUN12 (2 March, shawn_slh)] in reply to tweet about inaccessible presentations<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://www.w4a.info/2012/open-data/crc-instructions W4A instructions (8th step)]<br />
* [http://sxsw.com/interactive SXSW interactive] more than 1500 Speakers and Panelists - 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* AccessU at CSUN presenters by email from Sharron, Feb 2012 Jennifer<br />
<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* eAccess 12 - sent to organizer, 16 April , Jennifer<br />
* W4A 2012 - sent email to General Co-Chairs Julio Abascal & Markel Vigo, 26 March, Shawn (and Shadi before that :/<br />
* WWW 20120 - sent e-mail to conference contact, 20 Feb, Shawn<br />
* ICCHP - ?, Shadi<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
* UN Enable Newsletter - 27 February 2012 - Vicki<br />
* Promoting the use in own organisation (National Board of Social Services) planning to expand to rest of organization: Ministry of Social Affairs and Integration and translate into Danish - 16 March - Helle<br />
* presented at [http://barcampcanberra.org/ Canberra Barcamp 2012] - 17 March - Andrew<br />
* Noticed this recent project, [http://www.scie.org.uk/publications/accessibleevents/index.asp Making Events Accessible] launched by Social Care Institute for Excellence. On March 25, sent Feedback to request that "Making Presentations..." be included (Jennifer).<br />
Note that some of this information was taken from [http://g3ict.org/resource_center/newsletter/news/p/newsletterId_/id_376 a G3ICT post] and initially posted to this Wiki page on August 21, 2012 by Jennifer. Then, Jennifer sent individual emails to organizers of these conferences on August 22, 2012:<br />
* [http://a11y-bos.org/ Boston Accessibility Conference], September 15, 2012<br />
* [http://a11yldn.org.uk/ Accessibility Camp London UK], September 19, 2012<br />
* [http://www.twitter.com/a11ycampnyc Accessibility Camp New York City] (on Twitter), September 22, 2012<br />
* [http://a11yldn.org.uk/ Accessibility Camp DC], October 13, 2012 (contact is John Croston -- Jennifer)<br />
* [http://www.accessibilitycampla.org/ Accessibility Camp Los Angeles], October 20, 2012<br />
* [http://www.accessibilitycampto.org/ Accessibility Camp Toronto], November 17, 2012<br />
* [http://a11ymtl.org/en Accessibility Camp Montreal], November 23, 2012 <br />
<br />
Jennifer also sent the same [http://lists.w3.org/Archives/Public/public-wai-engage/2012Aug/0003.html message] to the public WAI-Engage email list on august 22, 2012.<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* AccessU conferences held by Knowbility next: May 15 to 17 in Austin<br />
* ATIA, Jennifer, Feb 22, 2012 - but would be good to follow up later<br />
* European eAccessibility Forum<br />
* Accessibility barcamps/unconferences including these two main sites:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.facebook.com/events/255649237860688/ A11y Camp Tokyo on Facebook], Contact is Makoto Ueki -- April 19, 2012 (Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Via @a11ysea, the 2nd #Accessibility Camp Seattle is June 2 & 3rd (Jennifer, March 9, 2012)<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=1396Promoting Make Presentations Accessible2012-08-22T23:21:39Z<p>Jsutton2: /* Conferences */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French: [http://www.braillenet.org/accessibilite/wcag20/accessible_fr.html <span lang="fr">Comment rendre des présentations accessibles à tous]<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L - 20 Feb, Jennifer<br />
<br />
=== Tweets ===<br />
<br />
* #w4a2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265062935044098 WAI tweeted 26 March 2012)<br />
* #www2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265412890988544 WAI tweeted 26 March 2012)<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
* [https://twitter.com/#!/shawn_slh/status/175672283216621568 #CSUN12 (2 March, shawn_slh)] in reply to tweet about inaccessible presentations<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://www.w4a.info/2012/open-data/crc-instructions W4A instructions (8th step)]<br />
* [http://sxsw.com/interactive SXSW interactive] more than 1500 Speakers and Panelists - 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* AccessU at CSUN presenters by email from Sharron, Feb 2012 Jennifer<br />
<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* eAccess 12 - sent to organizer, 16 April , Jennifer<br />
* W4A 2012 - sent email to General Co-Chairs Julio Abascal & Markel Vigo, 26 March, Shawn (and Shadi before that :/<br />
* WWW 20120 - sent e-mail to conference contact, 20 Feb, Shawn<br />
* ICCHP - ?, Shadi<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
* UN Enable Newsletter - 27 February 2012 - Vicki<br />
* Promoting the use in own organisation (National Board of Social Services) planning to expand to rest of organization: Ministry of Social Affairs and Integration and translate into Danish - 16 March - Helle<br />
* presented at [http://barcampcanberra.org/ Canberra Barcamp 2012] - 17 March - Andrew<br />
* Noticed this recent project, [http://www.scie.org.uk/publications/accessibleevents/index.asp Making Events Accessible] launched by Social Care Institute for Excellence. On March 25, sent Feedback to request that "Making Presentations..." be included (Jennifer).<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* AccessU conferences held by Knowbility next: May 15 to 17 in Austin<br />
* ATIA, Jennifer, Feb 22, 2012 - but would be good to follow up later<br />
* European eAccessibility Forum<br />
* Accessibility barcamps/unconferences including these two main sites:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.facebook.com/events/255649237860688/ A11y Camp Tokyo on Facebook], Contact is Makoto Ueki -- April 19, 2012 (Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Via @a11ysea, the 2nd #Accessibility Camp Seattle is June 2 & 3rd (Jennifer, March 9, 2012)<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=1395Promoting Make Presentations Accessible2012-08-22T23:11:04Z<p>Jsutton2: /* To Do: */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French: [http://www.braillenet.org/accessibilite/wcag20/accessible_fr.html <span lang="fr">Comment rendre des présentations accessibles à tous]<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L - 20 Feb, Jennifer<br />
<br />
=== Tweets ===<br />
<br />
* #w4a2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265062935044098 WAI tweeted 26 March 2012)<br />
* #www2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265412890988544 WAI tweeted 26 March 2012)<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
* [https://twitter.com/#!/shawn_slh/status/175672283216621568 #CSUN12 (2 March, shawn_slh)] in reply to tweet about inaccessible presentations<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://www.w4a.info/2012/open-data/crc-instructions W4A instructions (8th step)]<br />
* [http://sxsw.com/interactive SXSW interactive] more than 1500 Speakers and Panelists - 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* AccessU at CSUN presenters by email from Sharron, Feb 2012 Jennifer<br />
<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* eAccess 12 - sent to organizer, 16 April , Jennifer<br />
* W4A 2012 - sent email to General Co-Chairs Julio Abascal & Markel Vigo, 26 March, Shawn (and Shadi before that :/<br />
* WWW 20120 - sent e-mail to conference contact, 20 Feb, Shawn<br />
* ICCHP - ?, Shadi<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
* UN Enable Newsletter - 27 February 2012 - Vicki<br />
* Promoting the use in own organisation (National Board of Social Services) planning to expand to rest of organization: Ministry of Social Affairs and Integration and translate into Danish - 16 March - Helle<br />
* presented at [http://barcampcanberra.org/ Canberra Barcamp 2012] - 17 March - Andrew<br />
* Noticed this recent project, [http://www.scie.org.uk/publications/accessibleevents/index.asp Making Events Accessible] launched by Social Care Institute for Excellence. On March 25, sent Feedback to request that "Making Presentations..." be included (Jennifer).<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* AccessU conferences held by Knowbility next: May 15 to 17 in Austin<br />
* ATIA, Jennifer, Feb 22, 2012 - but would be good to follow up later<br />
* European eAccessibility Forum<br />
* Accessibility barcamps/unconferencesincluding:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.facebook.com/events/255649237860688/ A11y Camp Tokyo on Facebook], Contact is Makoto Ueki -- April 19, 2012 (Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Via @a11ysea, the 2nd #Accessibility Camp Seattle is June 2 & 3rd (Jennifer, March 9, 2012)<br />
** [http://a11y-bos.org/ Boston Accessibility Conference], September 15, 2012<br />
** [http://a11yldn.org.uk/ Accessibility Camp London UK], September 19, 2012<br />
** [http://www.twitter.com/a11ycampnyc Accessibility Camp New York City] (on Twitter), September 22, 2012<br />
** [http://a11yldn.org.uk/ Accessibility Camp DC], October 13, 2012 (contact is John Croston -- Jennifer)<br />
** [http://www.accessibilitycampla.org/ Accessibility Camp Los Angeles], October 20, 2012<br />
** [http://www.accessibilitycampto.org/ Accessibility Camp Toronto], November 17, 2012<br />
** [http://a11ymtl.org/en Accessibility Camp Montreal], November 23, 2012<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=1388Promoting Make Presentations Accessible2012-08-21T23:27:39Z<p>Jsutton2: /* Conferences */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French: [http://www.braillenet.org/accessibilite/wcag20/accessible_fr.html <span lang="fr">Comment rendre des présentations accessibles à tous]<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L - 20 Feb, Jennifer<br />
<br />
=== Tweets ===<br />
<br />
* #w4a2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265062935044098 WAI tweeted 26 March 2012)<br />
* #www2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265412890988544 WAI tweeted 26 March 2012)<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
* [https://twitter.com/#!/shawn_slh/status/175672283216621568 #CSUN12 (2 March, shawn_slh)] in reply to tweet about inaccessible presentations<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://www.w4a.info/2012/open-data/crc-instructions W4A instructions (8th step)]<br />
* [http://sxsw.com/interactive SXSW interactive] more than 1500 Speakers and Panelists - 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* AccessU at CSUN presenters by email from Sharron, Feb 2012 Jennifer<br />
<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* eAccess 12 - sent to organizer, 16 April , Jennifer<br />
* W4A 2012 - sent email to General Co-Chairs Julio Abascal & Markel Vigo, 26 March, Shawn (and Shadi before that :/<br />
* WWW 20120 - sent e-mail to conference contact, 20 Feb, Shawn<br />
* ICCHP - ?, Shadi<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
* UN Enable Newsletter - 27 February 2012 - Vicki<br />
* Promoting the use in own organisation (National Board of Social Services) planning to expand to rest of organization: Ministry of Social Affairs and Integration and translate into Danish - 16 March - Helle<br />
* presented at [http://barcampcanberra.org/ Canberra Barcamp 2012] - 17 March - Andrew<br />
* Noticed this recent project, [http://www.scie.org.uk/publications/accessibleevents/index.asp Making Events Accessible] launched by Social Care Institute for Excellence. On March 25, sent Feedback to request that "Making Presentations..." be included (Jennifer).<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Note that some of this information was taken from [http://g3ict.org/resource_center/newsletter/news/p/newsletterId_/id_376 a G3ICT post] and posted to this Wiki page on August 21, 2012 by Jennifer. Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* AccessU conferences held by Knowbility next: May 15 to 17 in Austin<br />
* ATIA, Jennifer, Feb 22, 2012 - but would be good to follow up later<br />
* European eAccessibility Forum<br />
* Accessibility barcamps/unconferences (NOTE: Jennifer emailed Jennison directly about this on Feb. 22, but individual follow-ups would be good, closer to the dates), including:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.facebook.com/events/255649237860688/ A11y Camp Tokyo on Facebook], Contact is Makoto Ueki -- April 19, 2012 (Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Via @a11ysea, the 2nd #Accessibility Camp Seattle is June 2 & 3rd (Jennifer, March 9, 2012)<br />
** [http://a11y-bos.org/ Boston Accessibility Conference], September 15, 2012<br />
** [http://a11yldn.org.uk/ Accessibility Camp London UK], September 19, 2012<br />
** [http://www.twitter.com/a11ycampnyc Accessibility Camp New York City] (on Twitter), September 22, 2012<br />
** [http://a11yldn.org.uk/ Accessibility Camp DC], October 13, 2012 (contact is John Croston -- Jennifer)<br />
** [http://www.accessibilitycampla.org/ Accessibility Camp Los Angeles], October 20, 2012<br />
** [http://www.accessibilitycampto.org/ Accessibility Camp Toronto], November 17, 2012<br />
** [http://a11ymtl.org/en Accessibility Camp Montreal], November 23, 2012<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=1387Promoting Make Presentations Accessible2012-08-21T23:21:34Z<p>Jsutton2: /* Conferences */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French: [http://www.braillenet.org/accessibilite/wcag20/accessible_fr.html <span lang="fr">Comment rendre des présentations accessibles à tous]<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L - 20 Feb, Jennifer<br />
<br />
=== Tweets ===<br />
<br />
* #w4a2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265062935044098 WAI tweeted 26 March 2012)<br />
* #www2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265412890988544 WAI tweeted 26 March 2012)<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
* [https://twitter.com/#!/shawn_slh/status/175672283216621568 #CSUN12 (2 March, shawn_slh)] in reply to tweet about inaccessible presentations<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://www.w4a.info/2012/open-data/crc-instructions W4A instructions (8th step)]<br />
* [http://sxsw.com/interactive SXSW interactive] more than 1500 Speakers and Panelists - 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* AccessU at CSUN presenters by email from Sharron, Feb 2012 Jennifer<br />
<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* eAccess 12 - sent to organizer, 16 April , Jennifer<br />
* W4A 2012 - sent email to General Co-Chairs Julio Abascal & Markel Vigo, 26 March, Shawn (and Shadi before that :/<br />
* WWW 20120 - sent e-mail to conference contact, 20 Feb, Shawn<br />
* ICCHP - ?, Shadi<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
* UN Enable Newsletter - 27 February 2012 - Vicki<br />
* Promoting the use in own organisation (National Board of Social Services) planning to expand to rest of organization: Ministry of Social Affairs and Integration and translate into Danish - 16 March - Helle<br />
* presented at [http://barcampcanberra.org/ Canberra Barcamp 2012] - 17 March - Andrew<br />
* Noticed this recent project, [http://www.scie.org.uk/publications/accessibleevents/index.asp Making Events Accessible] launched by Social Care Institute for Excellence. On March 25, sent Feedback to request that "Making Presentations..." be included (Jennifer).<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* AccessU conferences held by Knowbility next: May 15 to 17 in Austin<br />
* ATIA, Jennifer, Feb 22, 2012 - but would be good to follow up later<br />
* European eAccessibility Forum<br />
* Accessibility barcamps/unconferences (NOTE: Jennifer emailed Jennison directly about this on Feb. 22, but individual follow-ups would be good, closer to the dates), including:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.facebook.com/events/255649237860688/ A11y Camp Tokyo on Facebook], Contact is Makoto Ueki -- April 19, 2012 (Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Via @a11ysea, the 2nd #Accessibility Camp Seattle is June 2 & 3rd (Jennifer, March 9, 2012)<br />
** [http://a11y-bos.org/ Boston Accessibility Conference], September 15, 2012<br />
** [http://a11yldn.org.uk/ Accessibility Camp London UK, September 19, 2012<br />
** [http://www.twitter.com/a11ycampnyc Accessibility Camp New York City] (on Twitter), September 22, 2012<br />
** [http://a11yldn.org.uk/ Accessibility Camp DC], October 13, 2012 (contact is John Croston -- Jennifer)<br />
** [http://www.accessibilitycampla.org/ Accessibility Camp Los Angeles, October 20, 2012<br />
** [http://www.accessibilitycampto.org/ Accessibility Camp Toronto, November 17, 2012<br />
** [http://a11ymtl.org/en Accessibility Camp Montreal, November 23, 2012<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Contacts_for_promotion&diff=1386Contacts for promotion2012-08-17T21:12:22Z<p>Jsutton2: /* General Web designer & developer */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
__TOC__<br />
<br />
'''Suggested format for listings:'''<br />
* What it is - contact person (who knows how to contact them). Notes on what types of material is most relevant for it/them.<br />
<br />
== General Web designer & developer ==<br />
<br />
NOTE: One contact for each document being promoted may wish to set up a few Google Alerts with relevant phrases in order to monitor and document where references to that document are being made.<br />
Lists & Misc:<br />
* WSG Announcements (If you have an event, resource or relevant job you'd like posted (from any country), please let me know - russ at maxdesign.com.au )<br />
* [http://www.d.umn.edu/itss/training/online/webdesign/ Web Design References, UMD] - Laura Carlson. [http://www.d.umn.edu/itss/training/online/webdesign/urlform.html form to Suggest a Link]<br />
* [http://www.alistapart.com/articles/ A List Apart] (tech notes?)<br />
* [http://www.smashingmagazine.com Smashing Magazine]<br />
* [http://www.netmagazine.com Net Magazine]<br />
* [http://www.sitepoint.com/ SitePoint]<br />
* [http://radar.oreilly.com OReilly Radar]<br />
* WritersUA monthly user assistance update resource_directory@writersua.com contact: Joe W.<br />
* [http://www.maxdesign.com.au/category/light-reading/ Links for light reading] Max Design / Russ Weakley - distributed through [http://webstandardsgroup.org/ Web Standards Group]<br />
* [http://www.highedweb.org/ Higher Education Web Professionals Association (HighEdWeb)]<br />
* [http://www.iwanet.org/ International Webmasters Association/HTML Writers Guild (IWA/HWG)] Is this still active enough?<br />
* [http://www.wdda.org/ Web Design and Developers Association]<br />
* [http://wipa.org.au/ Web Industry Professionals Association Incorporated (WIPA) of Australia]<br />
* [http://webprofessionals.org/ World Organization of Webmasters (WOW)]<br />
<br />
== Web Accessibility focused ==<br />
<br />
Lists & Misc:<br />
* LinkedIn Groups - Jennison A.<br />
* [http://webaim.org/discussion/ The WebAIM Email Discussion List]<br />
<br />
Blogs:<br />
* [http://blog.knowbility.org/ Knowbility Blog, Universally Designed] - posters: Sharron, Wayne<br />
* [http://accessibilityindia.wordpress.com/ Accessibility India Maxability blog] accessibilityindia @ gmail.com<br />
* Do It Myself Blog - Glenda Watson-Hyatt<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (has contact info: Jennifer, Shawn)<br />
* [http://dboudreau.posterous.com/ accessiWatch v0.1 (2011)] (Denis B.)<br />
* [http://www.paciellogroup.com/blog/ The Paciello Group Blog] (Tech Notes?)<br />
* [http://www.stc-access.org/ STC Accessibility Sig]<br />
* [http://www.coataccess.org Coalition of Organizations for Accessible Technology<br />
(COAT)]<br />
<br />
<br />
Newsletters:<br />
* [http://www.knowbility.org/v/newsletter/ Knowbility] - Sharron R.<br />
* [http://webaim.org/newsletter/ The WebAIM Newsletter] (Jared Smith)<br />
<br />
== Disability focused ==<br />
<br />
Organizations that have blogs, newsletters, lists, etc.:<br />
* [http://www.HumanCenteredDesign.org Institute for Human Centered Design (IHCD)] - Jennifer O. (has contact info: Shawn)<br />
* [http://www.afb.org American Foundation for the Blind] - Paul S. (has contact info: Jennifer, Shawn)<br />
* Royal National Institute for the Blind (has contact info: Vicki)<br />
* [http://www.nfb.org/nfb/access_technology_blog.asp NFB Technology Access Blog] - Mark R & Clara V (has contact info: Jennifer, Shawn)<br />
* [http://www.acb.org The American Council of the Blind] - Melanie B. (has contact info: Jennifer)<br />
* [http://www.visionaware.org Visionaware] - ?name (has contact info: Jennifer)<br />
* [http://www.lighthouse-sf.org/ San Francisco Lighthouse] - ?name (has contact info: Jennifer)<br />
* [http://www.eastersealstech.com/content.aspx?pId=682 Podcast - Assistive Technology Update] produced by [http://www.eastersealstech.com/Default.aspx Easter Seals indata Indiana Assistive Technology Act]: The publication is "AT Update" and consists of Fast-paced news, tips, and interviews for AT professionals and enthusiasts. While services are provided throughout Indiana, information seems wide-ranging. Here's the [http://www.eastersealstech.com/content.aspx?pId=87 Contact page].<br />
<br />
<br />
<br />
Blogs:<br />
* [http://www.lflegal.com LF Legal] [especially for policies and standards harmonization)<br />
<br />
Newsletters:<br />
* HeadStar [http://www.headstar.com/eablive/ E-Access Live] and [http://www.headstar.com/site/scripts/documents_info.php?categoryID=1&documentID=11 E-Access Bulletin] - Dan J. (has contact info: Jennifer, Shawn)<br />
* [http://www.un.org/disabilities/default.asp?PID=312 United Nations Department of Economic and Social Affairs (DESA)] (has contact info: Vicki)<br />
<br />
E-mail lists:<br />
* webwatch@accessplace.net (subscribed: Jennifer)<br />
* VICUG-L@LISTSERV.ICORS.ORG 285 members (subscribed: Jennifer)<br />
<br />
Other:<br />
* ...<br />
<br />
== Miscellaneous Items That Need Closer Review/Consideration ==<br />
<br />
*See if any of these [http://www.d.umn.edu/itss/training/online/webdesign/sites.html blogs] seem worth hand-picking<br />
*See if any of these [http://www.d.umn.edu/itss/training/online/webdesign/associations.html associations] seem worth targeting<br />
<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Contacts_for_promotion&diff=1385Contacts for promotion2012-08-17T21:07:45Z<p>Jsutton2: /* General Web designer & developer */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
__TOC__<br />
<br />
'''Suggested format for listings:'''<br />
* What it is - contact person (who knows how to contact them). Notes on what types of material is most relevant for it/them.<br />
<br />
== General Web designer & developer ==<br />
<br />
NOTE: One contact for each document being promoted may wish to set up a few Google Alerts with relevant phrases in order to monitor and document where references to that document are being made.<br />
Lists & Misc:<br />
* WSG Announcements (If you have an event, resource or relevant job you'd like posted (from any country), please let me know - russ at maxdesign.com.au )<br />
* [http://www.d.umn.edu/itss/training/online/webdesign/ Web Design References, UMD] - Laura Carlson. [http://www.d.umn.edu/itss/training/online/webdesign/urlform.html form to Suggest a Link]<br />
* [http://www.alistapart.com/articles/ A List Apart] (tech notes?)<br />
* [http://www.smashingmagazine.com Smashing Magazine]<br />
* [http://www.netmagazine.com Net Magazine]<br />
* [http://www.sitepoint.com/ SitePoint]<br />
* [http://radar.oreilly.com OReilly Radar]<br />
* WritersUA monthly user assistance update resource_directory@writersua.com contact: Joe W.<br />
* [http://www.maxdesign.com.au/category/light-reading/ Links for light reading] Max Design / Russ Weakley - distributed through [http://webstandardsgroup.org/ Web Standards Group]<br />
* [http://www.highedweb.org/<br />
Higher Education Web Professionals Association (HighEdWeb)]<br />
* [http://www.iwanet.org/ International Webmasters Association/HTML Writers Guild (IWA/HWG) Is this still active enough?<br />
* [http://www.wdda.org/ Web Design and Developers Association]<br />
* [http://wipa.org.au/ Web Industry Professionals Association Incorporated (WIPA) of Australia]<br />
* [http://webprofessionals.org/ World Organization of Webmasters (WOW)]<br />
<br />
== Web Accessibility focused ==<br />
<br />
Lists & Misc:<br />
* LinkedIn Groups - Jennison A.<br />
* [http://webaim.org/discussion/ The WebAIM Email Discussion List]<br />
<br />
Blogs:<br />
* [http://blog.knowbility.org/ Knowbility Blog, Universally Designed] - posters: Sharron, Wayne<br />
* [http://accessibilityindia.wordpress.com/ Accessibility India Maxability blog] accessibilityindia @ gmail.com<br />
* Do It Myself Blog - Glenda Watson-Hyatt<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (has contact info: Jennifer, Shawn)<br />
* [http://dboudreau.posterous.com/ accessiWatch v0.1 (2011)] (Denis B.)<br />
* [http://www.paciellogroup.com/blog/ The Paciello Group Blog] (Tech Notes?)<br />
* [http://www.stc-access.org/ STC Accessibility Sig]<br />
* [http://www.coataccess.org Coalition of Organizations for Accessible Technology<br />
(COAT)]<br />
<br />
<br />
Newsletters:<br />
* [http://www.knowbility.org/v/newsletter/ Knowbility] - Sharron R.<br />
* [http://webaim.org/newsletter/ The WebAIM Newsletter] (Jared Smith)<br />
<br />
== Disability focused ==<br />
<br />
Organizations that have blogs, newsletters, lists, etc.:<br />
* [http://www.HumanCenteredDesign.org Institute for Human Centered Design (IHCD)] - Jennifer O. (has contact info: Shawn)<br />
* [http://www.afb.org American Foundation for the Blind] - Paul S. (has contact info: Jennifer, Shawn)<br />
* Royal National Institute for the Blind (has contact info: Vicki)<br />
* [http://www.nfb.org/nfb/access_technology_blog.asp NFB Technology Access Blog] - Mark R & Clara V (has contact info: Jennifer, Shawn)<br />
* [http://www.acb.org The American Council of the Blind] - Melanie B. (has contact info: Jennifer)<br />
* [http://www.visionaware.org Visionaware] - ?name (has contact info: Jennifer)<br />
* [http://www.lighthouse-sf.org/ San Francisco Lighthouse] - ?name (has contact info: Jennifer)<br />
* [http://www.eastersealstech.com/content.aspx?pId=682 Podcast - Assistive Technology Update] produced by [http://www.eastersealstech.com/Default.aspx Easter Seals indata Indiana Assistive Technology Act]: The publication is "AT Update" and consists of Fast-paced news, tips, and interviews for AT professionals and enthusiasts. While services are provided throughout Indiana, information seems wide-ranging. Here's the [http://www.eastersealstech.com/content.aspx?pId=87 Contact page].<br />
<br />
<br />
<br />
Blogs:<br />
* [http://www.lflegal.com LF Legal] [especially for policies and standards harmonization)<br />
<br />
Newsletters:<br />
* HeadStar [http://www.headstar.com/eablive/ E-Access Live] and [http://www.headstar.com/site/scripts/documents_info.php?categoryID=1&documentID=11 E-Access Bulletin] - Dan J. (has contact info: Jennifer, Shawn)<br />
* [http://www.un.org/disabilities/default.asp?PID=312 United Nations Department of Economic and Social Affairs (DESA)] (has contact info: Vicki)<br />
<br />
E-mail lists:<br />
* webwatch@accessplace.net (subscribed: Jennifer)<br />
* VICUG-L@LISTSERV.ICORS.ORG 285 members (subscribed: Jennifer)<br />
<br />
Other:<br />
* ...<br />
<br />
== Miscellaneous Items That Need Closer Review/Consideration ==<br />
<br />
*See if any of these [http://www.d.umn.edu/itss/training/online/webdesign/sites.html blogs] seem worth hand-picking<br />
*See if any of these [http://www.d.umn.edu/itss/training/online/webdesign/associations.html associations] seem worth targeting<br />
<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Accessibility_in_Courses&diff=1384Promoting Accessibility in Courses2012-08-17T20:51:18Z<p>Jsutton2: /* Additional Ideas extracted/Copied from EO WG Promotion Wiki Pages */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
== Resources & Pointers ==<br />
<br />
* Main document: [http://www.w3.org/WAI/training/ Developing Web Accessibility Presentations and Training]<br />
* Old draft: [http://www.w3.org/WAI/EO/Drafts/promos/courses.php Integrating Web Accessibility in Courses] <br />
* Related Materials: [http://www.w3.org/WAI/EO/Drafts/training/ Training Resource Suite]; [http://www.w3.org/community/webed/wiki/Main_Page#Accessibility Accessibility Modules on Web Education Community Group]<br />
<br />
== Audience & Messages ==<br />
=== Audience ===<br />
<p>We have identified two main audience types. First is the general public which includes providers of informal meet-ups and continuing education of the kind that occurs at conferences and "unconferences." The second is the academic community. Messaging will overlap, but in some instances will be specific to one group or the other.</p><br />
* General Audience - may need foundational messaging about accessibility issues as well as specifics about the materials available. May not know much about how PWD use the web or the need for accessibility. <br />
* Academic Audience - should be more aware of need for educational inclusion. Messaging may be more focused on industry trends, skills development, creating technical graduates who are ready to meet requirements of the information technology industry. <br />
<br />
=== Messages ===<br />
<p>An important aspect of high quality Web courses is making the Web accessible to people with disabilities. [or: An important aspect of high quality Web courses is including instruction on developing Web sites that are accessible to people with disabilities.] ''This principle applies whether the audience consists of web developers, graphic designers, managers, advocates or college students.''</p><br />
<br />
<p> ''The Suite provides several presentation outlines that enable the presenter to address a variety of skill levels, interests and time constraints.''</p><br />
<br />
== Tweet ideas you can use==<br />
...<br />
<br />
== Blog, newsletter, e-mail ideas you can use ==<br />
Subject/Headline: '''W3C WAI materials to help you update your web course for accessibility'''<br />
<br />
@@ students get current info, zingy @@<br /><br />
An important aspect of high quality Web courses is making the Web accessible to people with disabilities. [<em>or:</em> An important aspect of high quality Web courses is including instruction on developing Web sites that are accessible to people with disabilities.] To help you integrate accessibility in your Web courses, W3C WAI provides materials that you can use for lecture, activities, and student study.<br />
See Developing Web Accessibility Presentations and Training at http://www.w3.org/WAI/training/<br />
<br />
@@ It's like open source courseware @@<br />
<br />
'''Web accessibility is an important social, technical, and business issue.<br />
'''<br />
<p>Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web. Currently most Web sites and Web software have accessibility barriers that make it difficult or impossible for many people with disabilities to use the Web. Teaching Web designers, developers, and authors accessibility is a key factor in making Web sites and software accessible, so that people with disabilities can use and contribute to the Web more effectively.</p><br />
<p>@@consider integrating shorter in first bit @@<br /> Web courses that are up-to-date with the latest trends in the industry include accessibility. Accessibility is being requested more and more in Web site development, as people realize the many benefits of making the Web accessible&mdash;for people with and without disabilities, and for Web site owners&mdash;and as legal requirements increase. Social, technical, financial, and legal factors of Web accessibility are described in the Web Accessibility Business Case at: http://www.w3.org/WAI/bcase/Overview.html</p><br />
<br />
'''W3C WAI provides material to support Web accessibility.'''<br />
...<br />
<br />
'''You can use WAI material for your Web accessibility instruction.'''<br />
<br />
<p>To help you incorporate accessibility in your upcoming Web design and development courses, we put together a resource suite @@<br />
<p>* @@use it - make your students happy</p><br />
<p> We hope that you will @@bookmark &quot;@@training resource suite&quot; and come back to it as you prepare Web course syllabus and materials.</p><br />
<p>Thank you for your attention to Web accessibility.</p><br />
<br />
<br />
@@'' College Instructors of Web Technologies, User Interface Design or Human Factors''@@<br />
<p>Do you want to integrate accessibility for people with disabilities into your core curriculum, but are not sure where to start? Consider using, [http://www.w3.org/WAI/training/ Developing Web Accessibility Presentations and Training], a W3C publications. This resource provides several detailed presentation outlines. These can be used for a variety of audiences, skill levels and time constraints. </p><br />
<p>The outline, [http://www.w3.org/WAI/training/presentation-outlines#design Web Accessibility Design], is an excellent one-week introduction to accessibility for students in computer science, information technology or human factors psychology. It can be presented in two lecture hours with an optional 2 to 3 hour lab. This resource comes with several suggested readings for the instructor's preparation. Many of these are excellent reading assignments for students. Web standards originate at the W3C, so many of the referenced documents are primary source materials.</p><br />
<br />
== Conference Presentation Possibilities==<br />
[http://www.w3.org/WAI/EO/wiki/Contacts_for_promotion Overall Contacts for Promotion]<br />
* [http://www.colorado.edu/ATconference/ Accessing Higher Ground] in November in Colorado. Any more room? See if anyone we know has had a paper accepted who could mention the training suite. Howard Kramer and Glenda S. may have ideas. See [http://www.colorado.edu/ATconference/about2012.html#contactus Accessing Higher Ground - Accessible Media, Web and Technology ConferenceContact page] -- November 12 - 16, 2012 (Note that Derek is keynoting; perhaps he might mention the training suite) (JS)<br />
* Maybe a [http://www.csun.edu/cod/conference/index.php CSUN] presentation for 2013<br />
* AccessU for 2013 could do a "train the trainers" track and use the training suite (SR)<br />
* South by Southwest (SR)<br />
* South by Southwest Edu open for papers until the end of this year, helping K -- 12 teachers too, focuses on those who are making curriculum products (SR)<br />
* [http://www.ozewai.org/ OZeWAI conference] - annually in December<br />
* Meetups and unconferences for short workshops -- especially start with these two, at the general level (JS):<br />
** [http://www.a11ycamp.org/ a11y Camp] <br />
** [http://www.accessibilitycamp.org/ Accessibility Camp]<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== Old and related material ===<br />
* Old material:<br />
** [http://www.w3.org/WAI/EO/Drafts/promos/courses.php Integrating Web Accessibility in Courses]<br />
** [http://www.w3.org/WAI/EO/changelogs/cl-promo-courses.html Requirements and Changelog for Promotional Campaign to Web Development Course Instructors]<br />
* '''Non-W3C''' related info:<br />
** [http://uiaccess.com/teachDI.html Teach Digital Inclusion] presentation (with draft video) encouraging instructors to teach digital inclusion in their ICT courses<br />
<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* Access Technology Higher Education Network [http://mailman1.u.washington.edu/mailman/listinfo/athen-list ATHEN email list]<br />
* Association on Higher Education and Disability [http://www.ahead.org/membership/mailing-list-policy | AHEAD email list]<br />
* US Federal Government Webmaster lists [http://www.howto.gov/communities How-To.Gov Communities]<br />
* WAI-Engage Community Group [mailto:public-wai-engage@w3.org WAI-Engage Group List]<br />
* Leadership Exchange in Arts and Disability [mailto:culturalartsaccess@yahoogroups.com LEAD mailing list]<br />
<br />
<br />
=== Tweets ===<br />
...<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
...<br />
<br />
==== To Do: ====<br />
<p>Outcome of brainstorming of Outreach Subcommittee Meeting Aug 15, 2012 plus additions. Note that many of these ideas are U.S.-centric and we will ask EO for more global perspective</p><br />
<br />
* Finalize outreach plan and present to EO by Aug 24, 2012 (JS, WD, SR)<br />
* Glenda Sims -- any associations? Suggestions of newsletters or conferences? (SR)<br />
* [http://www.webteacher.ws/ Web Teacher -- Virginia DeBolt] (SR)<br />
* [http://www.mediaaccess.org.au/learn 6-week course on building websites with WCAG 2.0 compliance] Professional Certificate in Web Accessibility from Media Access Australia. <br />
* Terry Thompson<br />
* Sarah Bourne in MA for government curricula connections<br />
* CA system -- both UC and state (WD)<br />
* Ideas about TX systems? (SR)<br />
* Maybe set up an online one-hour seminar to go over how to use this training suite? Volunteer(s) to teach? How to arrange payments and assure platform accessibility?<br />
* Post announcement to both the ATHEN and AHEAD email Lists (JS)<br />
* Craft email message for the WAI-Engage email list encouraging discussion of the training suite on the [http://www.w3.org/community/wai-engage/ WAI-Engage Wiki]. Capture tips and tricks for conducting effective training sessions using the suite. (SR with help from EO)<br />
* Getting materials adopted into an official curriculum -- Wayne can offer guidance about that; what they did at Long Beach, integrated into learning materials and modules<br />
* Develop a press release draft related to Longbeach and saying: "Here is what they did at Long Beach, if you want to do the same, use these resources." (SR)<br />
* [http://www.rit.edu/%7Eeasi/index.htm Norm Coombs and EASI]<br />
* John Gunderson at U. of IL<br />
<br />
===== Additional Ideas extracted/Copied from EO WG Promotion Wiki Pages =====<br />
<br />
* WSG Announcements (If you have an event, resource or relevant job you'd like posted (from any country), please let me know - russ at maxdesign.com.au)<br />
[http://www.maxdesign.com.au/category/light-reading/ Links for light reading] Max Design / Russ Weakley - distributed through [http://webstandardsgroup.org/ Web Standards Group]<br />
* [http://www.webstandards.org/ Web Standards Project (WasP)]<br />
* [http://www.d.umn.edu/itss/training/online/webdesign/ Web Design References, UMD] - Laura Carlson. [http://www.d.umn.edu/itss/training/online/webdesign/urlform.html<br />
form to Suggest a Link]<br />
* WritersUA monthly user assistance update resource_directory@writersua.com contact: Joe W.<br />
* LinkedIn Groups - Jennison A.<br />
* [http://webaim.org/discussion/ The WebAIM Email Discussion List]<br />
* [http://webaim.org/newsletter/ The WebAIM Newsletter] (Jared Smith) <br />
* [http://blog.knowbility.org/ Knowbility Blog, Universally Designed] - posters: Sharron, Wayne<br />
* [http://accessibilityindia.wordpress.com/ Accessibility India Maxability blog] accessibilityindia @ gmail.com<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (has contact info: Jennifer, Shawn)<br />
* [http://www.paciellogroup.com/blog/ The Paciello Group Blog]<br />
* [http://www.highedweb.org/<br />
Higher Education Web Professionals Association (HighEdWeb)]<br />
* [http://www.iwanet.org/ International Webmasters Association/HTML Writers Guild (IWA/HWG) Is this still active enough?<br />
* [http://www.wdda.org/ Web Design and Developers Association]<br />
* [http://wipa.org.au/ Web Industry Professionals Association Incorporated (WIPA) of Australia]<br />
* [http://webprofessionals.org/ World Organization of Webmasters (WOW)] <br />
* [http://www.wait-till-i.com Chris Heilmann's site]<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Accessibility_in_Courses&diff=1383Promoting Accessibility in Courses2012-08-17T20:45:17Z<p>Jsutton2: /* To Do: */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
== Resources & Pointers ==<br />
<br />
* Main document: [http://www.w3.org/WAI/training/ Developing Web Accessibility Presentations and Training]<br />
* Old draft: [http://www.w3.org/WAI/EO/Drafts/promos/courses.php Integrating Web Accessibility in Courses] <br />
* Related Materials: [http://www.w3.org/WAI/EO/Drafts/training/ Training Resource Suite]; [http://www.w3.org/community/webed/wiki/Main_Page#Accessibility Accessibility Modules on Web Education Community Group]<br />
<br />
== Audience & Messages ==<br />
=== Audience ===<br />
<p>We have identified two main audience types. First is the general public which includes providers of informal meet-ups and continuing education of the kind that occurs at conferences and "unconferences." The second is the academic community. Messaging will overlap, but in some instances will be specific to one group or the other.</p><br />
* General Audience - may need foundational messaging about accessibility issues as well as specifics about the materials available. May not know much about how PWD use the web or the need for accessibility. <br />
* Academic Audience - should be more aware of need for educational inclusion. Messaging may be more focused on industry trends, skills development, creating technical graduates who are ready to meet requirements of the information technology industry. <br />
<br />
=== Messages ===<br />
<p>An important aspect of high quality Web courses is making the Web accessible to people with disabilities. [or: An important aspect of high quality Web courses is including instruction on developing Web sites that are accessible to people with disabilities.] ''This principle applies whether the audience consists of web developers, graphic designers, managers, advocates or college students.''</p><br />
<br />
<p> ''The Suite provides several presentation outlines that enable the presenter to address a variety of skill levels, interests and time constraints.''</p><br />
<br />
== Tweet ideas you can use==<br />
...<br />
<br />
== Blog, newsletter, e-mail ideas you can use ==<br />
Subject/Headline: '''W3C WAI materials to help you update your web course for accessibility'''<br />
<br />
@@ students get current info, zingy @@<br /><br />
An important aspect of high quality Web courses is making the Web accessible to people with disabilities. [<em>or:</em> An important aspect of high quality Web courses is including instruction on developing Web sites that are accessible to people with disabilities.] To help you integrate accessibility in your Web courses, W3C WAI provides materials that you can use for lecture, activities, and student study.<br />
See Developing Web Accessibility Presentations and Training at http://www.w3.org/WAI/training/<br />
<br />
@@ It's like open source courseware @@<br />
<br />
'''Web accessibility is an important social, technical, and business issue.<br />
'''<br />
<p>Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web. Currently most Web sites and Web software have accessibility barriers that make it difficult or impossible for many people with disabilities to use the Web. Teaching Web designers, developers, and authors accessibility is a key factor in making Web sites and software accessible, so that people with disabilities can use and contribute to the Web more effectively.</p><br />
<p>@@consider integrating shorter in first bit @@<br /> Web courses that are up-to-date with the latest trends in the industry include accessibility. Accessibility is being requested more and more in Web site development, as people realize the many benefits of making the Web accessible&mdash;for people with and without disabilities, and for Web site owners&mdash;and as legal requirements increase. Social, technical, financial, and legal factors of Web accessibility are described in the Web Accessibility Business Case at: http://www.w3.org/WAI/bcase/Overview.html</p><br />
<br />
'''W3C WAI provides material to support Web accessibility.'''<br />
...<br />
<br />
'''You can use WAI material for your Web accessibility instruction.'''<br />
<br />
<p>To help you incorporate accessibility in your upcoming Web design and development courses, we put together a resource suite @@<br />
<p>* @@use it - make your students happy</p><br />
<p> We hope that you will @@bookmark &quot;@@training resource suite&quot; and come back to it as you prepare Web course syllabus and materials.</p><br />
<p>Thank you for your attention to Web accessibility.</p><br />
<br />
<br />
@@'' College Instructors of Web Technologies, User Interface Design or Human Factors''@@<br />
<p>Do you want to integrate accessibility for people with disabilities into your core curriculum, but are not sure where to start? Consider using, [http://www.w3.org/WAI/training/ Developing Web Accessibility Presentations and Training], a W3C publications. This resource provides several detailed presentation outlines. These can be used for a variety of audiences, skill levels and time constraints. </p><br />
<p>The outline, [http://www.w3.org/WAI/training/presentation-outlines#design Web Accessibility Design], is an excellent one-week introduction to accessibility for students in computer science, information technology or human factors psychology. It can be presented in two lecture hours with an optional 2 to 3 hour lab. This resource comes with several suggested readings for the instructor's preparation. Many of these are excellent reading assignments for students. Web standards originate at the W3C, so many of the referenced documents are primary source materials.</p><br />
<br />
== Conference Presentation Possibilities==<br />
[http://www.w3.org/WAI/EO/wiki/Contacts_for_promotion Overall Contacts for Promotion]<br />
* [http://www.colorado.edu/ATconference/ Accessing Higher Ground] in November in Colorado. Any more room? See if anyone we know has had a paper accepted who could mention the training suite. Howard Kramer and Glenda S. may have ideas. See [http://www.colorado.edu/ATconference/about2012.html#contactus Accessing Higher Ground - Accessible Media, Web and Technology ConferenceContact page] -- November 12 - 16, 2012 (Note that Derek is keynoting; perhaps he might mention the training suite) (JS)<br />
* Maybe a [http://www.csun.edu/cod/conference/index.php CSUN] presentation for 2013<br />
* AccessU for 2013 could do a "train the trainers" track and use the training suite (SR)<br />
* South by Southwest (SR)<br />
* South by Southwest Edu open for papers until the end of this year, helping K -- 12 teachers too, focuses on those who are making curriculum products (SR)<br />
* [http://www.ozewai.org/ OZeWAI conference] - annually in December<br />
* Meetups and unconferences for short workshops -- especially start with these two, at the general level (JS):<br />
** [http://www.a11ycamp.org/ a11y Camp] <br />
** [http://www.accessibilitycamp.org/ Accessibility Camp]<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== Old and related material ===<br />
* Old material:<br />
** [http://www.w3.org/WAI/EO/Drafts/promos/courses.php Integrating Web Accessibility in Courses]<br />
** [http://www.w3.org/WAI/EO/changelogs/cl-promo-courses.html Requirements and Changelog for Promotional Campaign to Web Development Course Instructors]<br />
* '''Non-W3C''' related info:<br />
** [http://uiaccess.com/teachDI.html Teach Digital Inclusion] presentation (with draft video) encouraging instructors to teach digital inclusion in their ICT courses<br />
<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* Access Technology Higher Education Network [http://mailman1.u.washington.edu/mailman/listinfo/athen-list ATHEN email list]<br />
* Association on Higher Education and Disability [http://www.ahead.org/membership/mailing-list-policy | AHEAD email list]<br />
* US Federal Government Webmaster lists [http://www.howto.gov/communities How-To.Gov Communities]<br />
* WAI-Engage Community Group [mailto:public-wai-engage@w3.org WAI-Engage Group List]<br />
* Leadership Exchange in Arts and Disability [mailto:culturalartsaccess@yahoogroups.com LEAD mailing list]<br />
<br />
<br />
=== Tweets ===<br />
...<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
...<br />
<br />
==== To Do: ====<br />
<p>Outcome of brainstorming of Outreach Subcommittee Meeting Aug 15, 2012 plus additions. Note that many of these ideas are U.S.-centric and we will ask EO for more global perspective</p><br />
<br />
* Finalize outreach plan and present to EO by Aug 24, 2012 (JS, WD, SR)<br />
* Glenda Sims -- any associations? Suggestions of newsletters or conferences? (SR)<br />
* [http://www.webteacher.ws/ Web Teacher -- Virginia DeBolt] (SR)<br />
* [http://www.mediaaccess.org.au/learn 6-week course on building websites with WCAG 2.0 compliance] Professional Certificate in Web Accessibility from Media Access Australia. <br />
* Terry Thompson<br />
* Sarah Bourne in MA for government curricula connections<br />
* CA system -- both UC and state (WD)<br />
* Ideas about TX systems? (SR)<br />
* Maybe set up an online one-hour seminar to go over how to use this training suite? Volunteer(s) to teach? How to arrange payments and assure platform accessibility?<br />
* Post announcement to both the ATHEN and AHEAD email Lists (JS)<br />
* Craft email message for the WAI-Engage email list encouraging discussion of the training suite on the [http://www.w3.org/community/wai-engage/ WAI-Engage Wiki]. Capture tips and tricks for conducting effective training sessions using the suite. (SR with help from EO)<br />
* Getting materials adopted into an official curriculum -- Wayne can offer guidance about that; what they did at Long Beach, integrated into learning materials and modules<br />
* Develop a press release draft related to Longbeach and saying: "Here is what they did at Long Beach, if you want to do the same, use these resources." (SR)<br />
* [http://www.rit.edu/%7Eeasi/index.htm Norm Coombs and EASI]<br />
* John Gunderson at U. of IL<br />
<br />
===== Additional Ideas extracted/Copied from EO WG Promotion Wiki Pages =====<br />
<br />
* WSG Announcements (If you have an event, resource or relevant job you'd like posted (from any country), please let me know - russ at maxdesign.com.au)<br />
* [http://www.maxdesign.com.au/category/light-reading/ Links for light reading] Max Design / Russ Weakley - distributed through [http://webstandardsgroup.org/ Web Standards Group]<br />
* [http://www.webstandards.org/ Web Standards Project (WasP)]<br />
* [http://www.d.umn.edu/itss/training/online/webdesign/ Web Design References, UMD] - Laura Carlson. [http://www.d.umn.edu/itss/training/online/webdesign/urlform.html<br />
form to Suggest a Link]<br />
* WritersUA monthly user assistance update resource_directory@writersua.com contact: Joe W.<br />
* LinkedIn Groups - Jennison A.<br />
* [http://webaim.org/discussion/ The WebAIM Email Discussion List]<br />
* [http://webaim.org/newsletter/ The WebAIM Newsletter] (Jared Smith) <br />
* [http://blog.knowbility.org/ Knowbility Blog, Universally Designed] - posters: Sharron, Wayne<br />
* [http://accessibilityindia.wordpress.com/ Accessibility India Maxability blog] accessibilityindia @ gmail.com<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (has contact info: Jennifer, Shawn)<br />
* [http://www.paciellogroup.com/blog/ The Paciello Group Blog]<br />
* [http://www.highedweb.org/<br />
Higher Education Web Professionals Association (HighEdWeb)]<br />
* [http://www.iwanet.org/ International Webmasters Association/HTML Writers Guild (IWA/HWG) Is this still active enough?<br />
* [http://www.wdda.org/ Web Design and Developers Association]<br />
* [http://wipa.org.au/ Web Industry Professionals Association Incorporated (WIPA) of Australia]<br />
* [http://webprofessionals.org/ World Organization of Webmasters (WOW)] <br />
* [http://www.wait-till-i.com Chris Heilmann's site]<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=484Promoting Make Presentations Accessible2012-03-26T17:21:41Z<p>Jsutton2: /* Conferences */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French in progress<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L - 20 Feb, Jennifer<br />
<br />
=== Tweets ===<br />
<br />
* #w4a2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265062935044098 WAI tweeted 26 March 2012)<br />
* #www2012 Presenters: as you prepare, see “How to Make Presentations Accessible to All” from #W3C WAI http://bit.ly/YourPreso #a11y (https://twitter.com/#!/w3c_wai/status/184265412890988544 WAI tweeted 26 March 2012)<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
* [https://twitter.com/#!/shawn_slh/status/175672283216621568 #CSUN12 (2 March, shawn_slh)] in reply to tweet about inaccessible presentations<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://www.w4a.info/2012/open-data/crc-instructions W4A instructions (8th step)]<br />
* [http://sxsw.com/interactive SXSW interactive] more than 1500 Speakers and Panelists - 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* AccessU at CSUN presenters by email from Sharron, Feb 2012 Jennifer<br />
<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* W4A 2012 - sent email to General Co-Chairs Julio Abascal & Markel Vigo, 26 March, Shawn (and Shadi before that :/<br />
* WWW 20120 - sent e-mail to conference contact, 20 Feb, Shawn<br />
* ICCHP - ?, Shadi<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
* UN Enable Newsletter - 27 February 2012 - Vicki<br />
* Promoting the use in own organisation (National Board of Social Services) planning to expand to rest of organization: Ministry of Social Affairs and Integration and translate into Danish - 16 March - Helle<br />
* presented at [http://barcampcanberra.org/ Canberra Barcamp 2012] - 17 March - Andrew<br />
* Noticed this recent project, [http://www.scie.org.uk/publications/accessibleevents/index.asp Making Events Accessible] launched by Social Care Institute for Excellence. On March 25, sent Feedback to request that "Making Presentations..." be included (Jennifer).<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* AccessU conferences held by Knowbility next: May 15 to 17 in Austin<br />
* ATIA, Jennifer, Feb 22, 2012 - but would be good to follow up later<br />
* European eAccessibility Forum<br />
* Accessibility barcamps/unconferences (NOTE: Jennifer emailed Jennison directly about this on Feb. 22, but individual follow-ups would be good, closer to the dates), including:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.facebook.com/events/255649237860688/ A11y Camp Tokyo on Facebook], Contact is Makoto Ueki -- April 19, 2012 (Jennifer)<br />
** [http://www.accessibilitycampdc.org/ Accessibility Camp DC] (October 13, 2012, contact is John Croston -- Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Via @a11ysea, the 2nd #Accessibility Camp Seattle is June 2 & 3rd (Jennifer, March 9, 2012)<br />
** Accessibility Camp Montreal, August 31, 2012 (Jennifer)<br />
** Accessibility Camp Los Angeles - October 20, 2012 (no link, yet -- Jennifer)<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=477Promoting Make Presentations Accessible2012-03-25T20:48:48Z<p>Jsutton2: /* Done: */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French in progress<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L - 20 Feb, Jennifer<br />
<br />
=== Tweets ===<br />
<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
* [https://twitter.com/#!/shawn_slh/status/175672283216621568 #CSUN12 (2 March, shawn_slh)] in reply to tweet about inaccessible presentations<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://sxsw.com/interactive SXSW interactive] more than 1500 Speakers and Panelists - 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* AccessU at CSUN presenters by email from Sharron, Feb 2012 Jennifer<br />
<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
* UN Enable Newsletter - 27 February 2012 - Vicki<br />
* Promoting the use in own organisation (National Board of Social Services) planning to expand to rest of organization: Ministry of Social Affairs and Integration and translate into Danish - 16 March - Helle<br />
* presented at [http://barcampcanberra.org/ Canberra Barcamp 2012] - 17 March - Andrew<br />
* Noticed this recent project, [http://www.scie.org.uk/publications/accessibleevents/index.asp Making Events Accessible] launched by Social Care Institute for Excellence. On March 25, sent Feedback to request that "Making Presentations..." be included (Jennifer).<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* AccessU conferences held by Knowbility next: May 15 to 17 in Austin<br />
* ATIA, Jennifer, Feb 22, 2012 - but would be good to follow up later<br />
* European eAccessibility Forum<br />
* ICCHP<br />
* Accessibility barcamps/unconferences (NOTE: Jennifer emailed Jennison directly about this on Feb. 22, but individual follow-ups would be good, closer to the dates), including:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.accessibilitycampdc.org/ Accessibility Camp DC] (October 13, 2012, contact is John Croston -- Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Via @a11ysea, the 2nd #Accessibility Camp Seattle is June 2 & 3rd (Jennifer, March 9, 2012)<br />
** Accessibility Camp Montreal, August 31, 2012 (Jennifer)<br />
** Accessibility Camp Los Angeles - October 20, 2012 (no link, yet -- Jennifer)<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.w4a.info/2012/ W4A]<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_BAD&diff=444Promoting BAD2012-03-16T01:13:05Z<p>Jsutton2: /* 2012 EOWG Recent Contacts */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, developers, teachers, trainers, and advocates about BAD.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)], short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare<br />
<br />
* Jan 2012 [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html WAI IG e-mail], [https://twitter.com/#!/w3c_wai/status/164452260707975168 tweet], [http://www.w3.org/WAI/highlights/archive#x20120131a WAI highlight & RSS feed]<br />
<br />
* <del>Supporting document http://www.w3.org/WAI/EO/2005/Demo/ About BAD </del> {this is old, don't point to it.}<br />
* Oct 2011 [http://twitter.com/#!/w3c_wai/status/124504842004742144 Tweet], [http://www.w3.org/WAI/highlights/archive#x20111013a WAI highlight & rss feed], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2011OctDec/0003.html WAI IG email]<br />
* Translations: (none)<br />
<br />
== Audiences ==<br />
<br />
* Teachers, trainers<br />
* Conference presenters<br />
* Web developers<br />
* Accessibility advocates<br />
* Web accessibility evaluators and testers<br />
* ([http://www.w3.org/WAI/EO/Drafts/retrofit/requ-basite.html old audience analysis])<br />
<br />
== Tweet ideas ==<br />
''(Note: short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare )''<br />
* BAD to Good: Demo shows example website with #accessibility barriers and fixes http://bit.ly/BADshare Useful for presentations. #a11y<br />
* BAD to Good: WAI demo website with #accessibility barriers and fixes http://bit.ly/BADdemo Useful for presentations. #a11y<br />
* Need to show web devs how to fix #accessibility issues without sacrificing visual style? http://bit.ly/BADdemo #a11y <br />
* Read about WAI's Before and After Demo (BAD) and use it to show #accessibility at work http://bit.ly/aboutBAD #a11y<br />
* Need practical examples of #accessibility coding techniques? WAI made Before and After Demo for you. http://bit.ly/BADdemo #a11y<br />
* Cool new site, easy to use and share to show accessible design techniques applied. @w3c_wai resource. http://bit.ly/BADdemo #a11y<br />
* Great resource for accidental accessibility team leads. Before and After Demo from @w3c_wai http://bit.ly/aboutBAD #a11y<br />
<br />
== Draft blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Audience: Teachers, trainers ===<br />
'''Use BAD to Train Developers to Create Great Pages for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Teaching web development professionals about web accessibility almost always includes the need to clear up misunderstandings about the impact of accessible design on visual style and presentation. The Web Accessibility Initiative (WAI) at the W3C has just updated a set of demonstration web pages to help trainers do just that.<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web and application developers believe that accessible web sites must be dull and lack interactivity. The [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)] is a free and useful teaching tool that gives trainers and internal accessibility advocates a set of practical examples, implemented within a set of related pages. Trainers can use BAD to demonstrate that pages can be fully accessible without changing the cool visual features that developers love.<br />
<br />
Dr. Wayne Dick is the former Chair of the Computer Science and Engineering Department at the University of California at Long Beach. <br />
<br />
“BAD is great for these reasons,” says Dr Dick. “And here is support for that…..”<br />
<br />
===Audience: Public speakers===<br />
'''BAD Shows Audiences How to Do Good for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Web accessibility means designing pages and applications so that they can be used by everyone, including people with disabilities, some of whom use assistive technologies to browse the web. Accessibility is required by federal law in many instances and courts are broadening their interpretation of how the legal requirements are implemented. Many know that web accessibility is an increasingly important issue, but are not sure what to do.<br />
<br />
It is not uncommon for individuals who recognize and speak up about the need for accessibility within an organization to find that they have become experts by default. For those in this situation and who are invited to speak to groups about web accessibility, an updated tool from the W3C’s [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) can help.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. Sharp, new, and fun to use, BAD is designed to serve a variety of purposes. In addition to raising general awareness of web accessibility issues, BAD is a highly effective way to show how [http://w3.org/WAI/into/WCAG/ Web Content Accessibility Guidelines] (WCAG 2) can be applied without sacrificing visual appeal or interactivity.<br />
<br />
BAD shows common accessibility barriers using practical examples. The demonstration consists of an inaccessible Web site, an accessible version of the same site, as well as a report about the demonstrated barriers. The demonstration does not attempt to cover every checkpoint of the Web Content Accessibility Guidelines (WCAG) nor to provide an exhaustive list of examples but to demonstrate some key aspects of Web accessibility appropriate for short, focused presentations.<br />
<br />
Demonstrating practical examples during presentation is usually very effective. The description pages provide an overview of the accessibility barriers and features that are shown in the Demo. Together with the inaccessible and accessible Demo pages, concrete before and after examples can be explained during presentations. <br />
<br />
Presenters are encouraged to use the demo live or to download the pages with the understanding that some pages will not have full interactivity without connection to a server. WAI is interested to hear if BAD is good for you. Please use the demo and then let WAI know about your experience. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
...insert contact info.<br />
<br />
=== Audience: Web developers ===<br />
<br />
'''Use BAD for Great Examples of Web Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Here is a resource tip for the next time you need to meet an accessibility requirement. You had that accessibility training a few weeks age but you’re not exactly certain what they said about radio buttons and don’t really have time to sort through the guidelines and techniques of the [http://www.w3.org/WAI/intro/wcag/ Web Content Accessibility Guidelines] (WCAG 2). When you need a good example, think BAD. <br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the [http://www.w3.org/WAI Web Accessibility Initiative] (WAI) at the W3C and it is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images. <br />
<br />
With BAD you can look at the inaccessible version of any of the four pages – Home, News, Tickets, and Survey; you can read a report about the accessibility barriers that were found; you can look at the same pages with accessibility fixes in place; you can look at the code; and you can download and use the page template, adapting it for your own needs. <br />
<br />
While the general information can be very helpful, you may want to hone in on the one problem you need to solve - that one tricky item where you just want to know what the accessibility problem is and how can it be fixed? BAD pages come in two versions. The Before page is the inaccessible version. The After page is the same page, same function, same visual design but with accessibility built in. You can look right at the code to see how the problem was solved. <br />
<br />
Use BAD for good accessibility outcomes. See more information about [http://www.w3.org/WAI/demos/bad/ BAD].<br />
{shawn: I'm not sure which links you want in this paragraph and the next. anyway, I updated them from the outdated /2005/ links :-}<br />
<br />
So the next time you need a good example of accessibility in action, think BAD. More about [http://www.w3.org/WAI/demos/bad/#howto how to use the demo] is found on the WAI site.<br />
<br />
=== Audience: Internal Accessibility Advocates and Testers ===<br />
<br />
'''W3C Releases BAD web accessibility demo for advocates and testers'''(initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web development teams delegate accessibility responsibility to a few or even to just to one team member. The [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) at the W3C has just updated a tool to help make that job easier.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is a set of related web pages that provide fully integrated examples of accessibility at work. Accessibility leads who are seeking ways to test, report, and convince fellow team members of practical accessibility techniques will find this a useful demonstration tool for many common accessibility errors. BAD puts accessibility in the context of a set of related web pages. <br />
<br />
BAD provides an inaccessible version of each of the four pages – Home, News, Tickets, and Survey. Each one has a corresponding report of accessibility barriers contained in the page. An accessible version of the same pages with accessibility fixes in place can be viewed to demonstrate that the visual style remains largely unchanged.<br />
<br />
In many instances, the real issues for people with disabilities are not clear to developers or managers. Browsing through the inaccessible Demo pages using different browser configurations or assistive technologies (such as screen readers and magnifiers) helps highlight these issues. {shawn: need to broaden to cover other disabilities & interaction, e.g., keyboard only} The accessible Demo pages can be browsed in the same manner to show the difference.<br />
<br />
A well written evaluation report is key in the process of retrofitting websites for accessibility. It communicates the problems to managers and the developers who need to decide which solutions to implement. The evaluation reports of the Demo serve as a sample format for evaluators.<br />
<br />
BAD is designed to serve a variety of purposes. Not only is BAD useful in raising general awareness of web accessibility issues, it also provides practical examples for developers and demonstrates that an accessible site can be just as visually appealing and interactive as the one with access barriers. If the tool is helpful, please consider sharing your experience with the creators at WAI. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
…insert contact info<br />
<br />
===Audience: Web Managers===<br />
'''Use BAD, a Good Example of Accessibility at work''' (initial editor Cliff Tillick) <br />
<br />
<del>Have you ever considered what it would cost to make your website accessible? If so, what has worried you most:</del><br />
<del>- The time required?</del><br />
<del>- The design features you might lose?</del><br />
<del>- The impact on usability?</del><br />
{Shawn: not comfortable with intro about cost, and especially the possible mis-read that accessibility will cause you to lose design features.}<br />
<br />
Wouldn’t it be nice if you could see an example of the difference an accessible website makes?<br />
Well now you can. But we should warn you, it’s BAD—as in “Before and After Demonstration.”<br />
Published through the W3C’s Web Accessibility Initiative, BAD is a mockup of a website that contains a number of common barriers to accessibility and, linked to it, a website that has the same information but without those barriers.<br />
<br />
The differences are hard to recognize—unless you use a screen reader or screen magnification to get information from these pages. {shawn: or keyboard only or... need to be inclusive!} Then the differences are obvious. {shawn: Otherwise, you might not notice them at all. that's because most of the differences are "under the covers" -that is, in the underlying code and they don't impact the visual design at all. ...}<br />
<br />
=== Notes on posts, blurbs, etc. ===<br />
<br />
* Brainstorming -- possible theme -- When something bad becomes good. Making BAD good. (Jennifer, January 8, 2012)<br />
<br />
* What did site code look like before and how is it now fixed? How BAD can improve awareness about Web accessibility. (Sylvie, January 10, 2012)<br />
<br />
* For UN Newsletter (submitted on Jan. 23): Revised version:<br/>'''Web Accessibility''':<br/>How to make a BAD site GREATLY accessible to people with disabilities, older users, and others: The Before and After Demo (BAD) is a newly released set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the Web Accessibility Initiative (WAI) at the W3C and is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images.<br />
<br />
== WAI IG e-mail ==<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html archived final e-mail]<br />
<br />
== 2012 blogs, newsletters, references, etc. ==<br />
<br />
* [http://blog.knowbility.org/content/accessu-at-csun-2012-assistive-technology-and-web-accessibility-live-demos-show-how-it-really-works/ AccessU at CSUN 2012: Assistive Technology and Web Accessibility — Live Demos Show How it Really Works] "... people with disabilities... will use the Before and After Demo... to illustrate Web accessibility issues and how to resolve them." Knowbility blog - 20 Feb 2012 (Jennifer)<br />
* [http://accessibilityindia.wordpress.com/2012/02/12/talk-less-show-more/ Talk less & Show more] Accessibility India Maxability blog 12 February<br />
* [http://blog.knowbility.org/content/use-bad-for-good-examples-of-accessibility-in-action/ Use BAD for Good Examples of Accessibility in Action] posted on January 31, 2012 on Knowbility's Universally Designed blog by Sharron <br />
* [http://lists.d.umn.edu/pipermail/webdev/2012q1/000629.html Web Design Update newsletter] (Laura Carlson) lead article in newsletter that has 2,500+ readers<br />
* United Nations Enable Newsletter - [http://www.un.org/disabilities/documents/newsletter/january2012.doc January 2012, MS-Word]<br />
* Notable tweets & retweets:<br />
** [https://twitter.com/#!/cinteractionlab/status/167242173098627072 @cityuni_hcid] could be useful for #inm313 students - BaD Demo for accessibility at bit.ly/BADdemo #w3c #wai #a11y (via @AdobeAccess)<br />
** @mollydotcom: @SteveBuell @dboudreau I love the demo. I'm definitely going to be using it in some of my sessions. It's very clear and the annotations fab.<br />
** [https://twitter.com/#!/dboudreau/status/167134289912283136 @dboudreau] and reply from [https://twitter.com/#!/Nethermind/status/167257448959324161 @Nethermind (Elle Waters)]: I used this last week for new dev teams to understand real examples of #accessibility impacts - thanks you!<br />
** [https://twitter.com/#!/w3c_wai/status/164452260707975168 w3c_wai] BAD to Good: Demo shows example website with #accessibility barriers and fixes bit.ly/BADshare Useful for presentations. #a11y ''-- has 50+ Retweets & 31 Favorites''<br />
** [http://www.twitter.com/netmag Net Mag on Twitter] tweeted, on Feb. 9: "Check out the W3C's Before & After Demo for accessibility: http://bit.ly/nrBgvy" followers: 25192. According to [http://twitter.com/#!/netmag/status/167538119527235584 http://twitter.com/#!/netmag/status/167538119527235584], this was retweeted approximately 20 times. (Jennifer, Feb. 12)<br />
<br />
== 2012 EOWG Recent Contacts ==<br />
<br />
* '''Done:'''<br />
** UNDESA - Vicki (January 23, 2012)<br />
** ITU - Vicki (February 2, 2012)<br />
** WMO - Vicki (February 2, 2012)<br />
** ILO - Vicki (February 2, 2012)<br />
** WHO - Vicki (February 2, 2012)<br />
** OHCR - Vicki (February 2, 2012)<br />
** OHCA - Vicki (February 2, 2012)<br />
** UN NY (2)Vicki, positive feedback (February 2, 2012)<br />
** ITC - Vicki (February 2, 2012)<br />
** UNCTAD - Vicki (February 2, 2012)<br />
** UPU - Vicki (February 2, 2012)<br />
** EFSA - Vicki (February 2, 2012)<br />
** UNICEF - Vicki (February 2, 2012)<br />
** IAEA (2) - Vicki (February 2, 2012)<br />
** WTO - Vicki (February 2, 2012)<br />
** ICJ - Vicki (February 2, 2012)<br />
** WIPO (several)- Vicki, positive feedback (February 2, 2012)<br />
** Laura Carlson - Denis [Feb 8th]<br />
** Russ Weakly - Denis [Feb 8th]<br />
** Dennis Lembree - Denis [Feb 8th]<br />
** Léonie Watson - Denis [Feb 8th]<br />
** John Foliot - Denis [Feb 8th]<br />
** Jared W. Smith - Denis [Feb 8th]<br />
** Jason Kiss - Denis [Feb 8th]<br />
** David MacDonald - Denis [Feb 8th]<br />
** Kathy Wahlbin - Denis [Feb 8th]<br />
** Olivier Nourry - Denis [Feb 8th]<br />
** Glenda Sims - Denis [Feb 8th]<br />
** Karen Mardahl - Denis [Feb 8th]<br />
** Roger Hudson - Denis [Feb 8th]<br />
** Jennison Asuncion - Denis [Feb 8th]<br />
** Elle Waters - Denis [Feb 8th]<br />
** Karl Groves - Denis [Feb 8th]<br />
** Steve Buell - Denis [Feb 8th]<br />
** Matt May - Denis [Feb 8th]<br />
** Wendy Chisholm - Denis [Feb 8th]<br />
** Henny Swan - Denis [Feb 8th]<br />
** Molly Holzschlag - Denis [Feb 8th]<br />
** Andrew Kirkpatrick - Denis [Feb 8th]<br />
** Steve Faulkner - Denis [Feb 8th]<br />
** Mike Paciello - Denis [Feb 8th]<br />
** Bruce Lawson - Denis [Feb 8th]<br />
** Gez Lemon - Denis [Feb 8th]<br />
** Mike Gifford - Denis [Feb 8th]<br />
** WANAU list (Australian Universities) - Andrew [Feb 9th]<br />
** Distributed to a total of 31 personal contacts, and many of them are in the usability field. I sent the post Shawn sent to the WAI-IG list, and of course, I focused on choosing people who I don't believe are subscribed to WAI-IG or WebAIM. I sent to 15 people on January 31, and 16 more on February 12. As best I can tell, only one duplicates Denis's effort. (Jennifer)<br />
** Charity webforum list (Not for profit web managers and developers) - Jason [Feb 14th]<br />
** Ecampaigning forum list (Not for profit web managers and developers, specialist in campaigning) - Jason [Feb 14th]<br />
** Derek Featherstone -- Sharron communicated with him, along with other AccessU at CSUN presenters<br />
** "How People with Disabilities Use the Web" panel, as part of AccessU at CSUN, February 27, 2012 [Note added by Jennifer on March 15 -- the demo would work best, when using AT, if it was done via video. To illustrate with a s.r., it's necessary to do a lot of alt-tabbing between Before and After, and it's not easy to juggle all of the technology, while explaining (and making sure both presenter and audience remain oriented in terms of whether looking at Before or After). A video would permit a short, clear, and concise presentation to show two or three key highlights and permit attendees to then undertake further independent study.]<br />
* To Do:<br />
** Access U presenters - Sharron (in Austin, May 15 - 17? -- Jennifer)<br />
** UCal State list - Wayne<br />
** European design for all network (EDeAN)<br />
** RNIB - Vicki<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=443Promoting Make Presentations Accessible2012-03-10T02:23:43Z<p>Jsutton2: /* Conferences */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French in progress<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L - 20 Feb, Jennifer<br />
<br />
=== Tweets ===<br />
<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
* [https://twitter.com/#!/shawn_slh/status/175672283216621568 #CSUN12 (2 March, shawn_slh)] in reply to tweet about inaccessible presentations<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://sxsw.com/interactive SXSW interactive] more than 1500 Speakers and Panelists - 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* AccessU at CSUN presenters by email from Sharron, Feb 2012 Jennifer<br />
<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
* UN Enable Newsletter - 27 February 2012 - Vicki<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* AccessU conferences held by Knowbility next: May 15 to 17 in Austin<br />
* ATIA, Jennifer, Feb 22, 2012 - but would be good to follow up later<br />
* European eAccessibility Forum<br />
* ICCHP<br />
* Accessibility barcamps/unconferences (NOTE: Jennifer emailed Jennison directly about this on Feb. 22, but individual follow-ups would be good, closer to the dates), including:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.accessibilitycampdc.org/ Accessibility Camp DC] (October 13, 2012, contact is John Croston -- Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Via @a11ysea, the 2nd #Accessibility Camp Seattle is June 2 & 3rd (Jennifer, March 9, 2012)<br />
** Accessibility Camp Montreal, August 31, 2012 (Jennifer)<br />
** Accessibility Camp Los Angeles - October 20, 2012 (no link, yet -- Jennifer)<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.w4a.info/2012/ W4A]<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=433Promoting Make Presentations Accessible2012-02-23T01:06:19Z<p>Jsutton2: </p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French in progress<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L, 20 Feb., Jennifer<br />
=== Tweets ===<br />
<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://sxsw.com/interactive SXSW interactive] 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* Distributed by email from Sharron to AccessU at CSUN presenters, Jennifer<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* ATIA, Jennifer, Feb 22, 2012 <br />
* CSUN -- Shawn tweeted to them, as noted elsewhere (Jennifer)<br />
* European eAccessibility Forum<br />
* AccessU conferences held by Knowbility (In 2012, Feb. 27 and 28 in San Diego for CSUN (Sharron sent to 10+ presenters via private mailing, as noted elsewhere) and May 15 to 17 in Austin -- Jennifer)<br />
* ICCHP<br />
* Accessibility barcamps/unconferences (NOTE: Jennifer emailed Jennison directly about this on Feb. 22, but individual follow-ups would be good, closer to the dates), including:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.accessibilitycampdc.org/ Accessibility Camp DC] (October 13, 2012 -- Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Accessibility Camp Montreal, August 31, 2012 (Jennifer)<br />
** Accessibility Camp Los Angeles - October 20, 2012 (no link, yet -- Jennifer)<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.w4a.info/2012/ W4A]<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=432Promoting Make Presentations Accessible2012-02-22T23:00:53Z<p>Jsutton2: </p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, trainers, conference organizers and others about How to Make Presentations Accessible.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
<br />
* Document: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* 2012 announcements:<br />
** [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog Feb 2012] short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso]<br />
**[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html WAI IG e-mail Feb 2012]<br />
**[https://twitter.com/#!/w3c_wai/status/171670711432265729 tweet Feb 2012] <br />
* 2010 announcements: [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight 2010], [http://www.w3.org/QA/2010/06/make_your_presentations_access.html W3C blog 2010], Tweet<br />
* Translations:<br />
** French in progress<br />
<br />
== Audience & Messages ==<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
== Blog & newsletter ideas you can use==<br />
See [http://www.w3.org/QA/2012/02/make_presentations_accessible.html W3C blog 20 Feb 2012]<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
== Tweet ideas you can use==<br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* How to Make Your Presentations #Accessible to All for conference organizers, #speakers, #trainers, etc. http://bit.ly/YourPreso #a11y<br />
<br />
== E-mail ideas you can use ==<br />
See [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0123.html Feb 2012 WAI IG e-mail]<br /><br />
(Note: short URI to blog post: [http://bit.ly/YourPreso http://bit.ly/YourPreso])<br />
<br />
=== To conference organizers: ===<br />
main points:<br />
* please add a link to this document on your website wherever your provide information for speakers<br />
* please send this link to your speakers and encourage them to make their presentations accessible<br />
* consider including accessibility as a requirement in speaker contracts<br />
<br />
==== example 1 (drafted by Shawn) ====<br />
Subject: [Acme] Conference Quality Improvements<br />
<br />
Hi [organizer],<br />
<br />
You can improve the quality of [your conference | conference name] through accessibility. *'''Inclusive conferences and presentations are accessible to people with disabilities and work better for all your attendees, including those without disabilities'''*. There are many additional benefits of inclusive presentations, especially if you are in a large venue, have remote participants, provide podcasts of presentations, or make material available after the conference.<br />
<br />
W3C WAI has a resource to help conference organizers and presenters improve your events:<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;How to Make Presentations Accessible to All<br/><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://www.w3.org/WAI/training/accessible.php<br />
<br />
'''*Because this is so important, I am writing to ask if you would send this link to your speakers and encourage them to make their presentations accessible'''*. <br />
(and let me know if you do, as we are tracking outreach on it :)<br />
<br />
(As always, we welcome suggestions on how we might improve this resource in future versions. You can comment on the blog post at http://www.w3.org/QA/2012/02/make_presentations_accessible.html or send e-mail to the publicly archived list wai-eo-editors@w3.org or WAI staff-only list wai@w3.org )<br />
<br />
Thanks for your help making conferences and presentations more accessible!<br />
<br />
~Shawn<br />
<br />
=== To presenters: ===<br />
...<br />
<br />
== EOWG planning & record keeping ==<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== Mailing lists ===<br />
* WebAIM - 20 Feb, Jennifer<br />
* VICUG-L, 20 Feb., Jennifer<br />
=== Tweets ===<br />
<br />
* For conference organizers, #speakers, #trainers, etc., see: How to Make Your Presentations #Accessible to All http://bit.ly/YourPreso #a11y ([https://twitter.com/#!/w3c_wai/status/171670711432265729 WAI tweeted 20 Feb 2012])<br />
* @sxsw Presenters/panelists: To make your session work for the podcast & all, see W3C WAI resource bit.ly/YourPreso preparing for #SXSW ([https://twitter.com/#!/w3c_wai/status/172382006485852160 WAI tweeted 22 Feb 2012])<br />
* @CSUNCOD Presenters get tips & guidance on How to Make Your Presentations Accessible to All from bit.ly/YourPreso preparing for #CSUN12 [https://twitter.com/#!/w3c_wai/status/171697250114871296 WAI tweeted 20 Feb 2012]<br />
* lots of retweets, favorites, and similar tweets, e.g., "Do *NOT* give your next presentation without reading this! bit.ly/YourPreso "<br />
<br />
=== Presenters for Specific Conferences ===<br />
''e.g., the conference organizers said they were sending (or had sent) the info to their presenters''<br />
* [http://sxsw.com/interactive SXSW interactive] 22 February 2012 via Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] 22 February 2012 via Shawn<br />
* Distributed by email from Sharron to AccessU at CSUN presenters, Jennifer<br />
=== [http://www.linkedin.com/ LinkedIn] groups ===<br />
<br />
* in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
* as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] - December 2011 - Andrew<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
* [http://sxsw.com/interactive SXSW interactive] to Hugh via personal e-mail (reply: This is great -- we *will* try to get this out to speakers... in future years, it would help a ton to get something like in October or November (which is when we first start communicating with speakers) shawn: That URI is stable and you can add it to your template for communications for later this year. ;) update: "'''we incorporated into the last-minute e-mail that ISA (interactive speaker assistants) are sending to speakers'''.") - 22 February 2012 - Shawn<br />
* [http://aneventapart.com/ An Event Apart] to Jeffrey Zeldman via personal e-mail, to Marci Eversole via contact form (reply: Thanks Shawn, I will pass this information on for you. Marci) - 20 February 2012 - Shawn<br />
* [http://dae.uic.edu Digital Accessibility Expo] organizers to DIGITALACEXPO@LISTSERV.UIC.EDU and Kevin Price direct e-mail - 20 February 2012 - Shawn<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* ATIA<br />
* CSUN<br />
* European eAccessibility Forum<br />
* AccessU conferences held by Knowbility (In 2012, Feb. 27 and 28 in San Diego for CSUN and May 15 to 17 in Austin -- Jennifer)<br />
* ICCHP<br />
* Accessibility barcamps/unconferences including:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.accessibilitycampdc.org/ Accessibility Camp DC] (October 13, 2012 -- Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Accessibility Camp Montreal, August 31, 2012 (Jennifer)<br />
** Accessibility Camp Los Angeles - October 20, 2012 (no link, yet -- Jennifer)<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.w4a.info/2012/ W4A]<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read =====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups (see done above)<br />
* distributed to 17 people via private email campaign, Feb. 20, Jennifer<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=393Promoting Make Presentations Accessible2012-02-17T08:21:26Z<p>Jsutton2: /* Conferences */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc; border-top: 1px solid #930;">'''IMPORTANT''': The document How to Make Presentations Accessible is '''not ready for promotion yet'''! It's still a draft.</span><br/><span style="background-color: #ffffcc; border-bottom: 1px solid #930;">When it is ready, we'll send e-mail to WAI IG list and [http://www.w3.org/WAI/about/announcements other announcements].</span><br />
<br />
=== Resources & Pointers ===<br />
<br />
* Doc: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight June 2010]<br />
* [http://www.w3.org/QA/2010/06/make_your_presentations_access.html WAI blog June 2010]<br />
* Tweet June 2010<br />
* Translations: (none yet)<br />
<br />
<span style="background-color: #ffffcc; border-top: 1px solid #930;">'''IMPORTANT''': The document How to Make Presentations Accessible is '''not ready for promotion yet'''! It's still a draft.</span><br/><span style="background-color: #ffffcc; border-bottom: 1px solid #930;">When it is ready, we'll send e-mail to WAI IG list and [http://www.w3.org/WAI/about/announcements other announcements].</span><br />
<br />
=== Audience & Messages ===<br />
<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
=== Draft posts/blurbs ===<br />
<br />
''Do you remember a time when people around you broke out in laughter, but you didn't hear the joke?''<br /><br />
''You could be doing a similar thing to your audience — leaving some people out. For example, if you say "you can read it on the slide", you're probably excluding people who can't see the slide.''<br /><br />
<br />
[http://www.w3.org/WAI/training/accessible How to Make Presentations Accessible to All] is an updated WAI resource that helps you make presentations, talks, meetings, and training accessible to all of your potential audience, including people with disabilities and others. It covers planning, preparing slides, providing accessible material, considerations during your session, and more. It also mentions some of the [http://www.w3.org/WAI/training/accessible#benefits many benefits of inclusive presentations].<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
=== Tweet ideas ===<br />
...<br />
<br />
=== Draft e-mails ===<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2010AprJun/0065.html June 2012 WAI IG e-mail]<br />
<br />
==== To conference organizers: ====<br />
* add a link to this document on your website<br />
* include in material provided to presenters<br />
==== To presenters: ====<br />
...<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
<br />
==== To Do: ====<br />
<br />
a===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* ATIA?<br />
* CSUN<br />
* European eAccessibility Forum<br />
* AccessU conferences held by Knowbility (In 2012, Feb. 27 and 28 in San Diego for CSUN and May 15 to 17 in Austin -- Jennifer)<br />
* As seen on Twitter, Feb. 16, 2012 (Jennifer): Jennison wrote: "please hold May 9 for Global Accessibility Awareness Day. Stay tuned." and then "Regarding @gbla11yday, thank @JoeDevon who inspired the idea via a blog post I just happened upon http://bit.ly/A2I1Jf"<br />
* ICCHP<br />
* SXSW<br />
* Accessibility barcamps/unconferences including:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.accessibilitycampdc.org/ Accessibility Camp DC] (October 13, 2012 -- Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Accessibility Camp Montreal, August 31, 2012 (Jennifer)<br />
** Accessibility Camp Los Angeles - October 20, 2012 (no link, yet -- Jennifer)<br />
* An Event Apart<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.w4a.info/2012/ W4A]<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read=====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups<br />
** ''{done, Dec 2011, Andrew}'' in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility]<br />
** ''{done, Dec 2011}'' as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility]<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=392Promoting Make Presentations Accessible2012-02-17T08:07:35Z<p>Jsutton2: /* Conferences */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc; border-top: 1px solid #930;">'''IMPORTANT''': The document How to Make Presentations Accessible is '''not ready for promotion yet'''! It's still a draft.</span><br/><span style="background-color: #ffffcc; border-bottom: 1px solid #930;">When it is ready, we'll send e-mail to WAI IG list and [http://www.w3.org/WAI/about/announcements other announcements].</span><br />
<br />
=== Resources & Pointers ===<br />
<br />
* Doc: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight June 2010]<br />
* [http://www.w3.org/QA/2010/06/make_your_presentations_access.html WAI blog June 2010]<br />
* Tweet June 2010<br />
* Translations: (none yet)<br />
<br />
<span style="background-color: #ffffcc; border-top: 1px solid #930;">'''IMPORTANT''': The document How to Make Presentations Accessible is '''not ready for promotion yet'''! It's still a draft.</span><br/><span style="background-color: #ffffcc; border-bottom: 1px solid #930;">When it is ready, we'll send e-mail to WAI IG list and [http://www.w3.org/WAI/about/announcements other announcements].</span><br />
<br />
=== Audience & Messages ===<br />
<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
=== Draft posts/blurbs ===<br />
<br />
''Do you remember a time when people around you broke out in laughter, but you didn't hear the joke?''<br /><br />
''You could be doing a similar thing to your audience — leaving some people out. For example, if you say "you can read it on the slide", you're probably excluding people who can't see the slide.''<br /><br />
<br />
[http://www.w3.org/WAI/training/accessible How to Make Presentations Accessible to All] is an updated WAI resource that helps you make presentations, talks, meetings, and training accessible to all of your potential audience, including people with disabilities and others. It covers planning, preparing slides, providing accessible material, considerations during your session, and more. It also mentions some of the [http://www.w3.org/WAI/training/accessible#benefits many benefits of inclusive presentations].<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
=== Tweet ideas ===<br />
...<br />
<br />
=== Draft e-mails ===<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2010AprJun/0065.html June 2012 WAI IG e-mail]<br />
<br />
==== To conference organizers: ====<br />
* add a link to this document on your website<br />
* include in material provided to presenters<br />
==== To presenters: ====<br />
...<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* ATIA?<br />
* CSUN<br />
* European eAccessibility Forum<br />
* AccessU conferences held by Knowbility (In 2012, Feb. 27 and 28 in San Diego for CSUN and May 15 to 17 in Austin -- Jennifer)<br />
* As seen on Twitter, Feb. 16, 2012 (Jennifer): Jennison wrote: "please hold May 9 for Global Accessibility Awareness Day. Stay tuned."<br />
* ICCHP<br />
* SXSW<br />
* Accessibility barcamps/unconferences including:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.accessibilitycampdc.org/ Accessibility Camp DC] (October 13, 2012 -- Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Accessibility Camp Montreal, August 31, 2012 (Jennifer)<br />
** Accessibility Camp Los Angeles - October 20, 2012 (no link, yet -- Jennifer)<br />
* An Event Apart<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.w4a.info/2012/ W4A]<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read=====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups<br />
** ''{done, Dec 2011, Andrew}'' in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility]<br />
** ''{done, Dec 2011}'' as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility]<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_BAD&diff=379Promoting BAD2012-02-13T03:32:04Z<p>Jsutton2: </p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, developers, teachers, trainers, and advocates about BAD.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)], short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare<br />
<br />
* Jan 2012 [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html WAI IG e-mail], [https://twitter.com/#!/w3c_wai/status/164452260707975168 tweet], [http://www.w3.org/WAI/highlights/archive#x20120131a WAI highlight & RSS feed]<br />
<br />
* <del>Supporting document http://www.w3.org/WAI/EO/2005/Demo/ About BAD </del> {this is old, don't point to it.}<br />
* Oct 2011 [http://twitter.com/#!/w3c_wai/status/124504842004742144 Tweet], [http://www.w3.org/WAI/highlights/archive#x20111013a WAI highlight & rss feed], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2011OctDec/0003.html WAI IG email]<br />
* Translations: (none)<br />
<br />
== Audiences ==<br />
<br />
* Teachers, trainers<br />
* Conference presenters<br />
* Web developers<br />
* Accessibility advocates<br />
* Web accessibility evaluators and testers<br />
* ([http://www.w3.org/WAI/EO/Drafts/retrofit/requ-basite.html old audience analysis])<br />
<br />
== Tweet ideas ==<br />
''(Note: short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare )''<br />
* BAD to Good: Demo shows example website with #accessibility barriers and fixes http://bit.ly/BADshare Useful for presentations. #a11y<br />
* BAD to Good: WAI demo website with #accessibility barriers and fixes http://bit.ly/BADdemo Useful for presentations. #a11y<br />
* Need to show web devs how to fix #accessibility issues without sacrificing visual style? http://bit.ly/BADdemo #a11y <br />
* Read about WAI's Before and After Demo (BAD) and use it to show #accessibility at work http://bit.ly/aboutBAD #a11y<br />
* Need practical examples of #accessibility coding techniques? WAI made Before and After Demo for you. http://bit.ly/BADdemo #a11y<br />
* Cool new site, easy to use and share to show accessible design techniques applied. @w3c_wai resource. http://bit.ly/BADdemo #a11y<br />
* Great resource for accidental accessibility team leads. Before and After Demo from @w3c_wai http://bit.ly/aboutBAD #a11y<br />
<br />
== Draft blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Audience: Teachers, trainers ===<br />
'''Use BAD to Train Developers to Create Great Pages for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Teaching web development professionals about web accessibility almost always includes the need to clear up misunderstandings about the impact of accessible design on visual style and presentation. The Web Accessibility Initiative (WAI) at the W3C has just updated a set of demonstration web pages to help trainers do just that.<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web and application developers believe that accessible web sites must be dull and lack interactivity. The [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)] is a free and useful teaching tool that gives trainers and internal accessibility advocates a set of practical examples, implemented within a set of related pages. Trainers can use BAD to demonstrate that pages can be fully accessible without changing the cool visual features that developers love.<br />
<br />
Dr. Wayne Dick is the former Chair of the Computer Science and Engineering Department at the University of California at Long Beach. <br />
<br />
“BAD is great for these reasons,” says Dr Dick. “And here is support for that…..”<br />
<br />
===Audience: Public speakers===<br />
'''BAD Shows Audiences How to Do Good for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Web accessibility means designing pages and applications so that they can be used by everyone, including people with disabilities, some of whom use assistive technologies to browse the web. Accessibility is required by federal law in many instances and courts are broadening their interpretation of how the legal requirements are implemented. Many know that web accessibility is an increasingly important issue, but are not sure what to do.<br />
<br />
It is not uncommon for individuals who recognize and speak up about the need for accessibility within an organization to find that they have become experts by default. For those in this situation and who are invited to speak to groups about web accessibility, an updated tool from the W3C’s [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) can help.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. Sharp, new, and fun to use, BAD is designed to serve a variety of purposes. In addition to raising general awareness of web accessibility issues, BAD is a highly effective way to show how [http://w3.org/WAI/into/WCAG/ Web Content Accessibility Guidelines] (WCAG 2) can be applied without sacrificing visual appeal or interactivity.<br />
<br />
BAD shows common accessibility barriers using practical examples. The demonstration consists of an inaccessible Web site, an accessible version of the same site, as well as a report about the demonstrated barriers. The demonstration does not attempt to cover every checkpoint of the Web Content Accessibility Guidelines (WCAG) nor to provide an exhaustive list of examples but to demonstrate some key aspects of Web accessibility appropriate for short, focused presentations.<br />
<br />
Demonstrating practical examples during presentation is usually very effective. The description pages provide an overview of the accessibility barriers and features that are shown in the Demo. Together with the inaccessible and accessible Demo pages, concrete before and after examples can be explained during presentations. <br />
<br />
Presenters are encouraged to use the demo live or to download the pages with the understanding that some pages will not have full interactivity without connection to a server. WAI is interested to hear if BAD is good for you. Please use the demo and then let WAI know about your experience. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
...insert contact info.<br />
<br />
=== Audience: Web developers ===<br />
<br />
'''Use BAD for Great Examples of Web Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Here is a resource tip for the next time you need to meet an accessibility requirement. You had that accessibility training a few weeks age but you’re not exactly certain what they said about radio buttons and don’t really have time to sort through the guidelines and techniques of the [http://www.w3.org/WAI/intro/wcag/ Web Content Accessibility Guidelines] (WCAG 2). When you need a good example, think BAD. <br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the [http://www.w3.org/WAI Web Accessibility Initiative] (WAI) at the W3C and it is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images. <br />
<br />
With BAD you can look at the inaccessible version of any of the four pages – Home, News, Tickets, and Survey; you can read a report about the accessibility barriers that were found; you can look at the same pages with accessibility fixes in place; you can look at the code; and you can download and use the page template, adapting it for your own needs. <br />
<br />
While the general information can be very helpful, you may want to hone in on the one problem you need to solve - that one tricky item where you just want to know what the accessibility problem is and how can it be fixed? BAD pages come in two versions. The Before page is the inaccessible version. The After page is the same page, same function, same visual design but with accessibility built in. You can look right at the code to see how the problem was solved. <br />
<br />
Use BAD for good accessibility outcomes. See more information about [http://www.w3.org/WAI/demos/bad/ BAD].<br />
{shawn: I'm not sure which links you want in this paragraph and the next. anyway, I updated them from the outdated /2005/ links :-}<br />
<br />
So the next time you need a good example of accessibility in action, think BAD. More about [http://www.w3.org/WAI/demos/bad/#howto how to use the demo] is found on the WAI site.<br />
<br />
=== Audience: Internal Accessibility Advocates and Testers ===<br />
<br />
'''W3C Releases BAD web accessibility demo for advocates and testers'''(initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web development teams delegate accessibility responsibility to a few or even to just to one team member. The [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) at the W3C has just updated a tool to help make that job easier.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is a set of related web pages that provide fully integrated examples of accessibility at work. Accessibility leads who are seeking ways to test, report, and convince fellow team members of practical accessibility techniques will find this a useful demonstration tool for many common accessibility errors. BAD puts accessibility in the context of a set of related web pages. <br />
<br />
BAD provides an inaccessible version of each of the four pages – Home, News, Tickets, and Survey. Each one has a corresponding report of accessibility barriers contained in the page. An accessible version of the same pages with accessibility fixes in place can be viewed to demonstrate that the visual style remains largely unchanged.<br />
<br />
In many instances, the real issues for people with disabilities are not clear to developers or managers. Browsing through the inaccessible Demo pages using different browser configurations or assistive technologies (such as screen readers and magnifiers) helps highlight these issues. {shawn: need to broaden to cover other disabilities & interaction, e.g., keyboard only} The accessible Demo pages can be browsed in the same manner to show the difference.<br />
<br />
A well written evaluation report is key in the process of retrofitting websites for accessibility. It communicates the problems to managers and the developers who need to decide which solutions to implement. The evaluation reports of the Demo serve as a sample format for evaluators.<br />
<br />
BAD is designed to serve a variety of purposes. Not only is BAD useful in raising general awareness of web accessibility issues, it also provides practical examples for developers and demonstrates that an accessible site can be just as visually appealing and interactive as the one with access barriers. If the tool is helpful, please consider sharing your experience with the creators at WAI. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
…insert contact info<br />
<br />
===Audience: Web Managers===<br />
'''Use BAD, a Good Example of Accessibility at work''' (initial editor Cliff Tillick) <br />
<br />
<del>Have you ever considered what it would cost to make your website accessible? If so, what has worried you most:</del><br />
<del>- The time required?</del><br />
<del>- The design features you might lose?</del><br />
<del>- The impact on usability?</del><br />
{Shawn: not comfortable with intro about cost, and especially the possible mis-read that accessibility will cause you to lose design features.}<br />
<br />
Wouldn’t it be nice if you could see an example of the difference an accessible website makes?<br />
Well now you can. But we should warn you, it’s BAD—as in “Before and After Demonstration.”<br />
Published through the W3C’s Web Accessibility Initiative, BAD is a mockup of a website that contains a number of common barriers to accessibility and, linked to it, a website that has the same information but without those barriers.<br />
<br />
The differences are hard to recognize—unless you use a screen reader or screen magnification to get information from these pages. {shawn: or keyboard only or... need to be inclusive!} Then the differences are obvious. {shawn: Otherwise, you might not notice them at all. that's because most of the differences are "under the covers" -that is, in the underlying code and they don't impact the visual design at all. ...}<br />
<br />
=== Notes on posts, blurbs, etc. ===<br />
<br />
* Brainstorming -- possible theme -- When something bad becomes good. Making BAD good. (Jennifer, January 8, 2012)<br />
<br />
* What did site code look like before and how is it now fixed? How BAD can improve awareness about Web accessibility. (Sylvie, January 10, 2012)<br />
<br />
* For UN Newsletter (submitted on Jan. 23): Revised version:<br/>'''Web Accessibility''':<br/>How to make a BAD site GREATLY accessible to people with disabilities, older users, and others: The Before and After Demo (BAD) is a newly released set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the Web Accessibility Initiative (WAI) at the W3C and is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images.<br />
<br />
== WAI IG e-mail ==<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html archived final e-mail]<br />
<br />
== 2012 blogs, newsletters, references, etc. ==<br />
<br />
* [http://blog.knowbility.org/content/use-bad-for-good-examples-of-accessibility-in-action/ Use BAD for Good Examples of Accessibility in Action] posted on January 31, 2012 on Knowbility's Universally Designed blog by Sharron <br />
* [http://lists.d.umn.edu/pipermail/webdev/2012q1/000629.html Web Design Update newsletter] (Laura Carlson) lead article in newsletter that has 2,500+ readers<br />
* United Nations Enable Newsletter - [http://www.un.org/disabilities/documents/newsletter/january2012.doc January 2012, MS-Word]<br />
* Notable tweets & retweets:<br />
** [https://twitter.com/#!/cinteractionlab/status/167242173098627072 @cityuni_hcid] could be useful for #inm313 students - BaD Demo for accessibility at bit.ly/BADdemo #w3c #wai #a11y (via @AdobeAccess)<br />
** [https://twitter.com/#!/dboudreau/status/167134289912283136 @dboudreau] and reply from [https://twitter.com/#!/Nethermind/status/167257448959324161 @Nethermind (Elle Waters)]: I used this last week for new dev teams to understand real examples of #accessibility impacts - thanks you!<br />
** [https://twitter.com/#!/w3c_wai/status/164452260707975168 w3c_wai] BAD to Good: Demo shows example website with #accessibility barriers and fixes bit.ly/BADshare Useful for presentations. #a11y ''-- has 50+ Retweets & 31 Favorites''<br />
** [http://www.twitter.com/netmag Net Mag on Twitter] tweeted, on Feb. 9: "Check out the W3C's Before & After Demo for accessibility: http://bit.ly/nrBgvy" According to [http://twitter.com/#!/netmag/status/167538119527235584 http://twitter.com/#!/netmag/status/167538119527235584], this was retweeted approximately 20 times. (Jennifer, Feb. 12)<br />
<br />
== 2012 EOWG Recent Contacts ==<br />
<br />
* '''Done:'''<br />
** UNDESA - Vicki (January 23, 2012)<br />
** ITU - Vicki (February 2, 2012)<br />
** WMO - Vicki (February 2, 2012)<br />
** ILO - Vicki (February 2, 2012)<br />
** WHO - Vicki (February 2, 2012)<br />
** OHCR - Vicki (February 2, 2012)<br />
** OHCA - Vicki (February 2, 2012)<br />
** UN NY (2)Vicki, positive feedback (February 2, 2012)<br />
** ITC - Vicki (February 2, 2012)<br />
** UNCTAD - Vicki (February 2, 2012)<br />
** UPU - Vicki (February 2, 2012)<br />
** EFSA - Vicki (February 2, 2012)<br />
** UNICEF - Vicki (February 2, 2012)<br />
** IAEA (2) - Vicki (February 2, 2012)<br />
** WTO - Vicki (February 2, 2012)<br />
** ICJ - Vicki (February 2, 2012)<br />
** WIPO (several)- Vicki, positive feedback (February 2, 2012)<br />
** Laura Carlson - Denis [Feb 8th]<br />
** Russ Weakly - Denis [Feb 8th]<br />
** Dennis Lembree - Denis [Feb 8th]<br />
** Léonie Watson - Denis [Feb 8th]<br />
** John Foliot - Denis [Feb 8th]<br />
** Jared W. Smith - Denis [Feb 8th]<br />
** Jason Kiss - Denis [Feb 8th]<br />
** David MacDonald - Denis [Feb 8th]<br />
** Kathy Wahlbin - Denis [Feb 8th]<br />
** Olivier Nourry - Denis [Feb 8th]<br />
** Glenda Sims - Denis [Feb 8th]<br />
** Karen Mardahl - Denis [Feb 8th]<br />
** Roger Hudson - Denis [Feb 8th]<br />
** Jennison Asuncion - Denis [Feb 8th]<br />
** Elle Waters - Denis [Feb 8th]<br />
** Karl Groves - Denis [Feb 8th]<br />
** Steve Buell - Denis [Feb 8th]<br />
** Matt May - Denis [Feb 8th]<br />
** Wendy Chisholm - Denis [Feb 8th]<br />
** Henny Swan - Denis [Feb 8th]<br />
** Molly Holzschlag - Denis [Feb 8th]<br />
** Andrew Kirkpatrick - Denis [Feb 8th]<br />
** Steve Faulkner - Denis [Feb 8th]<br />
** Mike Paciello - Denis [Feb 8th]<br />
** Bruce Lawson - Denis [Feb 8th]<br />
** Gez Lemon - Denis [Feb 8th]<br />
** Mike Gifford - Denis [Feb 8th]<br />
** WANAU list (Australian Universities) - Andrew [Feb 9th]<br />
** Distributed to a total of 31 personal contacts, and many of them are in the usability field. I sent the post Shawn sent to the WAI-IG list, and of course, I focused on choosing people who I don't believe are subscribed to WAI-IG or WebAIM. I sent to 15 people on January 31, and 16 more on February 12. As best I can tell, only one duplicates Denis's effort. (Jennifer)<br />
<br />
* To Do:<br />
** Derek Featherstone - Sharron<br />
** Access U presenters - Sharron (both CSUN and in Austin? -- Jennifer)<br />
** AccessU at CSUN "How We Use the Web" Demo," Feb. 27 (Jennifer)<br />
** UCal State list - Wayne<br />
** Web manager, developer lists - Jason<br />
** European design for all network (EDeAN)<br />
** RNIB - Vicki<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_BAD&diff=378Promoting BAD2012-02-13T03:26:57Z<p>Jsutton2: </p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, developers, teachers, trainers, and advocates about BAD.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)], short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare<br />
<br />
* Jan 2012 [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html WAI IG e-mail], [https://twitter.com/#!/w3c_wai/status/164452260707975168 tweet], [http://www.w3.org/WAI/highlights/archive#x20120131a WAI highlight & RSS feed]<br />
<br />
* <del>Supporting document http://www.w3.org/WAI/EO/2005/Demo/ About BAD </del> {this is old, don't point to it.}<br />
* Oct 2011 [http://twitter.com/#!/w3c_wai/status/124504842004742144 Tweet], [http://www.w3.org/WAI/highlights/archive#x20111013a WAI highlight & rss feed], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2011OctDec/0003.html WAI IG email]<br />
* Translations: (none)<br />
<br />
== Audiences ==<br />
<br />
* Teachers, trainers<br />
* Conference presenters<br />
* Web developers<br />
* Accessibility advocates<br />
* Web accessibility evaluators and testers<br />
* ([http://www.w3.org/WAI/EO/Drafts/retrofit/requ-basite.html old audience analysis])<br />
<br />
== Tweet ideas ==<br />
''(Note: short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare )''<br />
* BAD to Good: Demo shows example website with #accessibility barriers and fixes http://bit.ly/BADshare Useful for presentations. #a11y<br />
* BAD to Good: WAI demo website with #accessibility barriers and fixes http://bit.ly/BADdemo Useful for presentations. #a11y<br />
* Need to show web devs how to fix #accessibility issues without sacrificing visual style? http://bit.ly/BADdemo #a11y <br />
* Read about WAI's Before and After Demo (BAD) and use it to show #accessibility at work http://bit.ly/aboutBAD #a11y<br />
* Need practical examples of #accessibility coding techniques? WAI made Before and After Demo for you. http://bit.ly/BADdemo #a11y<br />
* Cool new site, easy to use and share to show accessible design techniques applied. @w3c_wai resource. http://bit.ly/BADdemo #a11y<br />
* Great resource for accidental accessibility team leads. Before and After Demo from @w3c_wai http://bit.ly/aboutBAD #a11y<br />
<br />
== Draft blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Audience: Teachers, trainers ===<br />
'''Use BAD to Train Developers to Create Great Pages for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Teaching web development professionals about web accessibility almost always includes the need to clear up misunderstandings about the impact of accessible design on visual style and presentation. The Web Accessibility Initiative (WAI) at the W3C has just updated a set of demonstration web pages to help trainers do just that.<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web and application developers believe that accessible web sites must be dull and lack interactivity. The [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)] is a free and useful teaching tool that gives trainers and internal accessibility advocates a set of practical examples, implemented within a set of related pages. Trainers can use BAD to demonstrate that pages can be fully accessible without changing the cool visual features that developers love.<br />
<br />
Dr. Wayne Dick is the former Chair of the Computer Science and Engineering Department at the University of California at Long Beach. <br />
<br />
“BAD is great for these reasons,” says Dr Dick. “And here is support for that…..”<br />
<br />
===Audience: Public speakers===<br />
'''BAD Shows Audiences How to Do Good for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Web accessibility means designing pages and applications so that they can be used by everyone, including people with disabilities, some of whom use assistive technologies to browse the web. Accessibility is required by federal law in many instances and courts are broadening their interpretation of how the legal requirements are implemented. Many know that web accessibility is an increasingly important issue, but are not sure what to do.<br />
<br />
It is not uncommon for individuals who recognize and speak up about the need for accessibility within an organization to find that they have become experts by default. For those in this situation and who are invited to speak to groups about web accessibility, an updated tool from the W3C’s [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) can help.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. Sharp, new, and fun to use, BAD is designed to serve a variety of purposes. In addition to raising general awareness of web accessibility issues, BAD is a highly effective way to show how [http://w3.org/WAI/into/WCAG/ Web Content Accessibility Guidelines] (WCAG 2) can be applied without sacrificing visual appeal or interactivity.<br />
<br />
BAD shows common accessibility barriers using practical examples. The demonstration consists of an inaccessible Web site, an accessible version of the same site, as well as a report about the demonstrated barriers. The demonstration does not attempt to cover every checkpoint of the Web Content Accessibility Guidelines (WCAG) nor to provide an exhaustive list of examples but to demonstrate some key aspects of Web accessibility appropriate for short, focused presentations.<br />
<br />
Demonstrating practical examples during presentation is usually very effective. The description pages provide an overview of the accessibility barriers and features that are shown in the Demo. Together with the inaccessible and accessible Demo pages, concrete before and after examples can be explained during presentations. <br />
<br />
Presenters are encouraged to use the demo live or to download the pages with the understanding that some pages will not have full interactivity without connection to a server. WAI is interested to hear if BAD is good for you. Please use the demo and then let WAI know about your experience. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
...insert contact info.<br />
<br />
=== Audience: Web developers ===<br />
<br />
'''Use BAD for Great Examples of Web Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Here is a resource tip for the next time you need to meet an accessibility requirement. You had that accessibility training a few weeks age but you’re not exactly certain what they said about radio buttons and don’t really have time to sort through the guidelines and techniques of the [http://www.w3.org/WAI/intro/wcag/ Web Content Accessibility Guidelines] (WCAG 2). When you need a good example, think BAD. <br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the [http://www.w3.org/WAI Web Accessibility Initiative] (WAI) at the W3C and it is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images. <br />
<br />
With BAD you can look at the inaccessible version of any of the four pages – Home, News, Tickets, and Survey; you can read a report about the accessibility barriers that were found; you can look at the same pages with accessibility fixes in place; you can look at the code; and you can download and use the page template, adapting it for your own needs. <br />
<br />
While the general information can be very helpful, you may want to hone in on the one problem you need to solve - that one tricky item where you just want to know what the accessibility problem is and how can it be fixed? BAD pages come in two versions. The Before page is the inaccessible version. The After page is the same page, same function, same visual design but with accessibility built in. You can look right at the code to see how the problem was solved. <br />
<br />
Use BAD for good accessibility outcomes. See more information about [http://www.w3.org/WAI/demos/bad/ BAD].<br />
{shawn: I'm not sure which links you want in this paragraph and the next. anyway, I updated them from the outdated /2005/ links :-}<br />
<br />
So the next time you need a good example of accessibility in action, think BAD. More about [http://www.w3.org/WAI/demos/bad/#howto how to use the demo] is found on the WAI site.<br />
<br />
=== Audience: Internal Accessibility Advocates and Testers ===<br />
<br />
'''W3C Releases BAD web accessibility demo for advocates and testers'''(initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web development teams delegate accessibility responsibility to a few or even to just to one team member. The [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) at the W3C has just updated a tool to help make that job easier.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is a set of related web pages that provide fully integrated examples of accessibility at work. Accessibility leads who are seeking ways to test, report, and convince fellow team members of practical accessibility techniques will find this a useful demonstration tool for many common accessibility errors. BAD puts accessibility in the context of a set of related web pages. <br />
<br />
BAD provides an inaccessible version of each of the four pages – Home, News, Tickets, and Survey. Each one has a corresponding report of accessibility barriers contained in the page. An accessible version of the same pages with accessibility fixes in place can be viewed to demonstrate that the visual style remains largely unchanged.<br />
<br />
In many instances, the real issues for people with disabilities are not clear to developers or managers. Browsing through the inaccessible Demo pages using different browser configurations or assistive technologies (such as screen readers and magnifiers) helps highlight these issues. {shawn: need to broaden to cover other disabilities & interaction, e.g., keyboard only} The accessible Demo pages can be browsed in the same manner to show the difference.<br />
<br />
A well written evaluation report is key in the process of retrofitting websites for accessibility. It communicates the problems to managers and the developers who need to decide which solutions to implement. The evaluation reports of the Demo serve as a sample format for evaluators.<br />
<br />
BAD is designed to serve a variety of purposes. Not only is BAD useful in raising general awareness of web accessibility issues, it also provides practical examples for developers and demonstrates that an accessible site can be just as visually appealing and interactive as the one with access barriers. If the tool is helpful, please consider sharing your experience with the creators at WAI. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
…insert contact info<br />
<br />
===Audience: Web Managers===<br />
'''Use BAD, a Good Example of Accessibility at work''' (initial editor Cliff Tillick) <br />
<br />
<del>Have you ever considered what it would cost to make your website accessible? If so, what has worried you most:</del><br />
<del>- The time required?</del><br />
<del>- The design features you might lose?</del><br />
<del>- The impact on usability?</del><br />
{Shawn: not comfortable with intro about cost, and especially the possible mis-read that accessibility will cause you to lose design features.}<br />
<br />
Wouldn’t it be nice if you could see an example of the difference an accessible website makes?<br />
Well now you can. But we should warn you, it’s BAD—as in “Before and After Demonstration.”<br />
Published through the W3C’s Web Accessibility Initiative, BAD is a mockup of a website that contains a number of common barriers to accessibility and, linked to it, a website that has the same information but without those barriers.<br />
<br />
The differences are hard to recognize—unless you use a screen reader or screen magnification to get information from these pages. {shawn: or keyboard only or... need to be inclusive!} Then the differences are obvious. {shawn: Otherwise, you might not notice them at all. that's because most of the differences are "under the covers" -that is, in the underlying code and they don't impact the visual design at all. ...}<br />
<br />
=== Notes on posts, blurbs, etc. ===<br />
<br />
* Brainstorming -- possible theme -- When something bad becomes good. Making BAD good. (Jennifer, January 8, 2012)<br />
<br />
* What did site code look like before and how is it now fixed? How BAD can improve awareness about Web accessibility. (Sylvie, January 10, 2012)<br />
<br />
* For UN Newsletter (submitted on Jan. 23): Revised version:<br/>'''Web Accessibility''':<br/>How to make a BAD site GREATLY accessible to people with disabilities, older users, and others: The Before and After Demo (BAD) is a newly released set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the Web Accessibility Initiative (WAI) at the W3C and is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images.<br />
<br />
== WAI IG e-mail ==<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html archived final e-mail]<br />
<br />
== 2012 blogs, newsletters, references, etc. ==<br />
<br />
<br />
* [http://blog.knowbility.org/content/use-bad-for-good-examples-of-accessibility-in-action/ Use BAD for Good Examples of Accessibility in Action] posted on January 31, 2012 on Knowbility's Universally Designed blog by Sharron <br />
* [http://lists.d.umn.edu/pipermail/webdev/2012q1/000629.html Web Design Update newsletter] (Laura Carlson) lead article in newsletter that has 2,500+ readers<br />
* United Nations Enable Newsletter - [http://www.un.org/disabilities/documents/newsletter/january2012.doc January 2012, MS-Word]<br />
* Notable tweets & retweets:<br />
** [https://twitter.com/#!/cinteractionlab/status/167242173098627072 @cityuni_hcid] could be useful for #inm313 students - BaD Demo for accessibility at bit.ly/BADdemo #w3c #wai #a11y (via @AdobeAccess)<br />
** [https://twitter.com/#!/dboudreau/status/167134289912283136 @dboudreau] and reply from [https://twitter.com/#!/Nethermind/status/167257448959324161 @Nethermind (Elle Waters)]: I used this last week for new dev teams to understand real examples of #accessibility impacts - thanks you!<br />
** [https://twitter.com/#!/w3c_wai/status/164452260707975168 w3c_wai] BAD to Good: Demo shows example website with #accessibility barriers and fixes bit.ly/BADshare Useful for presentations. #a11y ''-- has 50+ Retweets & 31 Favorites''<br />
<br />
** [http://www.twitter.com/netmag Net Mag on Twitter] tweeted, on Feb. 9: "Check out the W3C's Before & After Demo for accessibility: http://bit.ly/nrBgvy" According to [http://twitter.com/#!/netmag/status/167538119527235584 http://twitter.com/#!/netmag/status/167538119527235584], this was retweeted approximately 20 times. (Jennifer, Feb. 12)cc<br />
<br />
== 2012 EOWG Recent Contacts ==<br />
<br />
* '''Done:'''<br />
** UNDESA - Vicki (January 23, 2012)<br />
** ITU - Vicki (February 2, 2012)<br />
** WMO - Vicki (February 2, 2012)<br />
** ILO - Vicki (February 2, 2012)<br />
** WHO - Vicki (February 2, 2012)<br />
** OHCR - Vicki (February 2, 2012)<br />
** OHCA - Vicki (February 2, 2012)<br />
** UN NY (2)Vicki, positive feedback (February 2, 2012)<br />
** ITC - Vicki (February 2, 2012)<br />
** UNCTAD - Vicki (February 2, 2012)<br />
** UPU - Vicki (February 2, 2012)<br />
** EFSA - Vicki (February 2, 2012)<br />
** UNICEF - Vicki (February 2, 2012)<br />
** IAEA (2) - Vicki (February 2, 2012)<br />
** WTO - Vicki (February 2, 2012)<br />
** ICJ - Vicki (February 2, 2012)<br />
** WIPO (several)- Vicki, positive feedback (February 2, 2012)<br />
** Laura Carlson - Denis [Feb 8th]<br />
** Russ Weakly - Denis [Feb 8th]<br />
** Dennis Lembree - Denis [Feb 8th]<br />
** Léonie Watson - Denis [Feb 8th]<br />
** John Foliot - Denis [Feb 8th]<br />
** Jared W. Smith - Denis [Feb 8th]<br />
** Jason Kiss - Denis [Feb 8th]<br />
** David MacDonald - Denis [Feb 8th]<br />
** Kathy Wahlbin - Denis [Feb 8th]<br />
** Olivier Nourry - Denis [Feb 8th]<br />
** Glenda Sims - Denis [Feb 8th]<br />
** Karen Mardahl - Denis [Feb 8th]<br />
** Roger Hudson - Denis [Feb 8th]<br />
** Jennison Asuncion - Denis [Feb 8th]<br />
** Elle Waters - Denis [Feb 8th]<br />
** Karl Groves - Denis [Feb 8th]<br />
** Steve Buell - Denis [Feb 8th]<br />
** Matt May - Denis [Feb 8th]<br />
** Wendy Chisholm - Denis [Feb 8th]<br />
** Henny Swan - Denis [Feb 8th]<br />
** Molly Holzschlag - Denis [Feb 8th]<br />
** Andrew Kirkpatrick - Denis [Feb 8th]<br />
** Steve Faulkner - Denis [Feb 8th]<br />
** Mike Paciello - Denis [Feb 8th]<br />
** Bruce Lawson - Denis [Feb 8th]<br />
** Gez Lemon - Denis [Feb 8th]<br />
** Mike Gifford - Denis [Feb 8th]<br />
** WANAU list (Australian Universities) - Andrew [Feb 9th]<br />
** Distributed to a total of 31 personal contacts, and many of them are in the usability field. I sent the post Shawn sent to the WAI-IG list, and of course, I focused on choosing people who I don't believe are subscribed to WAI-IG or WebAIM. I sent to 15 people on January 31, and 16 more on February 12. As best I can tell, only one duplicates Denis's effort. (Jennifer)<br />
<br />
* To Do:<br />
** Derek Featherstone - Sharron<br />
** Access U presenters - Sharron (both CSUN and in Austin? -- Jennifer)<br />
** AccessU at CSUN "How We Use the Web" Demo," Feb. 27 (Jennifer)<br />
** UCal State list - Wayne<br />
** Web manager, developer lists - Jason<br />
** European design for all network (EDeAN)<br />
** RNIB - Vicki<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_BAD&diff=377Promoting BAD2012-02-13T01:45:04Z<p>Jsutton2: /* 2012 EOWG Recent Contacts */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, developers, teachers, trainers, and advocates about BAD.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)], short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare<br />
<br />
* Jan 2012 [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html WAI IG e-mail], [https://twitter.com/#!/w3c_wai/status/164452260707975168 tweet], [http://www.w3.org/WAI/highlights/archive#x20120131a WAI highlight & RSS feed]<br />
<br />
* <del>Supporting document http://www.w3.org/WAI/EO/2005/Demo/ About BAD </del> {this is old, don't point to it.}<br />
* Oct 2011 [http://twitter.com/#!/w3c_wai/status/124504842004742144 Tweet], [http://www.w3.org/WAI/highlights/archive#x20111013a WAI highlight & rss feed], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2011OctDec/0003.html WAI IG email]<br />
* Translations: (none)<br />
<br />
== Audiences ==<br />
<br />
* Teachers, trainers<br />
* Conference presenters<br />
* Web developers<br />
* Accessibility advocates<br />
* Web accessibility evaluators and testers<br />
* ([http://www.w3.org/WAI/EO/Drafts/retrofit/requ-basite.html old audience analysis])<br />
<br />
== Tweet ideas ==<br />
''(Note: short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare )''<br />
* BAD to Good: Demo shows example website with #accessibility barriers and fixes http://bit.ly/BADshare Useful for presentations. #a11y<br />
* BAD to Good: WAI demo website with #accessibility barriers and fixes http://bit.ly/BADdemo Useful for presentations. #a11y<br />
* Need to show web devs how to fix #accessibility issues without sacrificing visual style? http://bit.ly/BADdemo #a11y <br />
* Read about WAI's Before and After Demo (BAD) and use it to show #accessibility at work http://bit.ly/aboutBAD #a11y<br />
* Need practical examples of #accessibility coding techniques? WAI made Before and After Demo for you. http://bit.ly/BADdemo #a11y<br />
* Cool new site, easy to use and share to show accessible design techniques applied. @w3c_wai resource. http://bit.ly/BADdemo #a11y<br />
* Great resource for accidental accessibility team leads. Before and After Demo from @w3c_wai http://bit.ly/aboutBAD #a11y<br />
<br />
== Draft blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Audience: Teachers, trainers ===<br />
'''Use BAD to Train Developers to Create Great Pages for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Teaching web development professionals about web accessibility almost always includes the need to clear up misunderstandings about the impact of accessible design on visual style and presentation. The Web Accessibility Initiative (WAI) at the W3C has just updated a set of demonstration web pages to help trainers do just that.<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web and application developers believe that accessible web sites must be dull and lack interactivity. The [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)] is a free and useful teaching tool that gives trainers and internal accessibility advocates a set of practical examples, implemented within a set of related pages. Trainers can use BAD to demonstrate that pages can be fully accessible without changing the cool visual features that developers love.<br />
<br />
Dr. Wayne Dick is the former Chair of the Computer Science and Engineering Department at the University of California at Long Beach. <br />
<br />
“BAD is great for these reasons,” says Dr Dick. “And here is support for that…..”<br />
<br />
===Audience: Public speakers===<br />
'''BAD Shows Audiences How to Do Good for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Web accessibility means designing pages and applications so that they can be used by everyone, including people with disabilities, some of whom use assistive technologies to browse the web. Accessibility is required by federal law in many instances and courts are broadening their interpretation of how the legal requirements are implemented. Many know that web accessibility is an increasingly important issue, but are not sure what to do.<br />
<br />
It is not uncommon for individuals who recognize and speak up about the need for accessibility within an organization to find that they have become experts by default. For those in this situation and who are invited to speak to groups about web accessibility, an updated tool from the W3C’s [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) can help.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. Sharp, new, and fun to use, BAD is designed to serve a variety of purposes. In addition to raising general awareness of web accessibility issues, BAD is a highly effective way to show how [http://w3.org/WAI/into/WCAG/ Web Content Accessibility Guidelines] (WCAG 2) can be applied without sacrificing visual appeal or interactivity.<br />
<br />
BAD shows common accessibility barriers using practical examples. The demonstration consists of an inaccessible Web site, an accessible version of the same site, as well as a report about the demonstrated barriers. The demonstration does not attempt to cover every checkpoint of the Web Content Accessibility Guidelines (WCAG) nor to provide an exhaustive list of examples but to demonstrate some key aspects of Web accessibility appropriate for short, focused presentations.<br />
<br />
Demonstrating practical examples during presentation is usually very effective. The description pages provide an overview of the accessibility barriers and features that are shown in the Demo. Together with the inaccessible and accessible Demo pages, concrete before and after examples can be explained during presentations. <br />
<br />
Presenters are encouraged to use the demo live or to download the pages with the understanding that some pages will not have full interactivity without connection to a server. WAI is interested to hear if BAD is good for you. Please use the demo and then let WAI know about your experience. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
...insert contact info.<br />
<br />
=== Audience: Web developers ===<br />
<br />
'''Use BAD for Great Examples of Web Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Here is a resource tip for the next time you need to meet an accessibility requirement. You had that accessibility training a few weeks age but you’re not exactly certain what they said about radio buttons and don’t really have time to sort through the guidelines and techniques of the [http://www.w3.org/WAI/intro/wcag/ Web Content Accessibility Guidelines] (WCAG 2). When you need a good example, think BAD. <br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the [http://www.w3.org/WAI Web Accessibility Initiative] (WAI) at the W3C and it is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images. <br />
<br />
With BAD you can look at the inaccessible version of any of the four pages – Home, News, Tickets, and Survey; you can read a report about the accessibility barriers that were found; you can look at the same pages with accessibility fixes in place; you can look at the code; and you can download and use the page template, adapting it for your own needs. <br />
<br />
While the general information can be very helpful, you may want to hone in on the one problem you need to solve - that one tricky item where you just want to know what the accessibility problem is and how can it be fixed? BAD pages come in two versions. The Before page is the inaccessible version. The After page is the same page, same function, same visual design but with accessibility built in. You can look right at the code to see how the problem was solved. <br />
<br />
Use BAD for good accessibility outcomes. See more information about [http://www.w3.org/WAI/demos/bad/ BAD].<br />
{shawn: I'm not sure which links you want in this paragraph and the next. anyway, I updated them from the outdated /2005/ links :-}<br />
<br />
So the next time you need a good example of accessibility in action, think BAD. More about [http://www.w3.org/WAI/demos/bad/#howto how to use the demo] is found on the WAI site.<br />
<br />
=== Audience: Internal Accessibility Advocates and Testers ===<br />
<br />
'''W3C Releases BAD web accessibility demo for advocates and testers'''(initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web development teams delegate accessibility responsibility to a few or even to just to one team member. The [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) at the W3C has just updated a tool to help make that job easier.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is a set of related web pages that provide fully integrated examples of accessibility at work. Accessibility leads who are seeking ways to test, report, and convince fellow team members of practical accessibility techniques will find this a useful demonstration tool for many common accessibility errors. BAD puts accessibility in the context of a set of related web pages. <br />
<br />
BAD provides an inaccessible version of each of the four pages – Home, News, Tickets, and Survey. Each one has a corresponding report of accessibility barriers contained in the page. An accessible version of the same pages with accessibility fixes in place can be viewed to demonstrate that the visual style remains largely unchanged.<br />
<br />
In many instances, the real issues for people with disabilities are not clear to developers or managers. Browsing through the inaccessible Demo pages using different browser configurations or assistive technologies (such as screen readers and magnifiers) helps highlight these issues. {shawn: need to broaden to cover other disabilities & interaction, e.g., keyboard only} The accessible Demo pages can be browsed in the same manner to show the difference.<br />
<br />
A well written evaluation report is key in the process of retrofitting websites for accessibility. It communicates the problems to managers and the developers who need to decide which solutions to implement. The evaluation reports of the Demo serve as a sample format for evaluators.<br />
<br />
BAD is designed to serve a variety of purposes. Not only is BAD useful in raising general awareness of web accessibility issues, it also provides practical examples for developers and demonstrates that an accessible site can be just as visually appealing and interactive as the one with access barriers. If the tool is helpful, please consider sharing your experience with the creators at WAI. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
…insert contact info<br />
<br />
===Audience: Web Managers===<br />
'''Use BAD, a Good Example of Accessibility at work''' (initial editor Cliff Tillick) <br />
<br />
<del>Have you ever considered what it would cost to make your website accessible? If so, what has worried you most:</del><br />
<del>- The time required?</del><br />
<del>- The design features you might lose?</del><br />
<del>- The impact on usability?</del><br />
{Shawn: not comfortable with intro about cost, and especially the possible mis-read that accessibility will cause you to lose design features.}<br />
<br />
Wouldn’t it be nice if you could see an example of the difference an accessible website makes?<br />
Well now you can. But we should warn you, it’s BAD—as in “Before and After Demonstration.”<br />
Published through the W3C’s Web Accessibility Initiative, BAD is a mockup of a website that contains a number of common barriers to accessibility and, linked to it, a website that has the same information but without those barriers.<br />
<br />
The differences are hard to recognize—unless you use a screen reader or screen magnification to get information from these pages. {shawn: or keyboard only or... need to be inclusive!} Then the differences are obvious. {shawn: Otherwise, you might not notice them at all. that's because most of the differences are "under the covers" -that is, in the underlying code and they don't impact the visual design at all. ...}<br />
<br />
=== Notes on posts, blurbs, etc. ===<br />
<br />
* Brainstorming -- possible theme -- When something bad becomes good. Making BAD good. (Jennifer, January 8, 2012)<br />
<br />
* What did site code look like before and how is it now fixed? How BAD can improve awareness about Web accessibility. (Sylvie, January 10, 2012)<br />
<br />
* For UN Newsletter (submitted on Jan. 23): Revised version:<br/>'''Web Accessibility''':<br/>How to make a BAD site GREATLY accessible to people with disabilities, older users, and others: The Before and After Demo (BAD) is a newly released set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the Web Accessibility Initiative (WAI) at the W3C and is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images.<br />
<br />
== WAI IG e-mail ==<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html archived final e-mail]<br />
<br />
== 2012 blogs, newsletters, references, etc. ==<br />
<br />
<br />
* [http://blog.knowbility.org/content/use-bad-for-good-examples-of-accessibility-in-action/ Use BAD for Good Examples of Accessibility in Action] posted on January 31, 2012 on Knowbility's Universally Designed blog by Sharron <br />
* [http://lists.d.umn.edu/pipermail/webdev/2012q1/000629.html Web Design Update newsletter] (Laura Carlson) lead article in newsletter that has 2,500+ readers<br />
* United Nations Enable Newsletter - [http://www.un.org/disabilities/documents/newsletter/january2012.doc January 2012, MS-Word]<br />
* Notable tweets & retweets:<br />
** [https://twitter.com/#!/cinteractionlab/status/167242173098627072 @cityuni_hcid] could be useful for #inm313 students - BaD Demo for accessibility at bit.ly/BADdemo #w3c #wai #a11y (via @AdobeAccess)<br />
** [https://twitter.com/#!/dboudreau/status/167134289912283136 @dboudreau] and reply from [https://twitter.com/#!/Nethermind/status/167257448959324161 @Nethermind (Elle Waters)]: I used this last week for new dev teams to understand real examples of #accessibility impacts - thanks you!<br />
** [https://twitter.com/#!/w3c_wai/status/164452260707975168 w3c_wai] BAD to Good: Demo shows example website with #accessibility barriers and fixes bit.ly/BADshare Useful for presentations. #a11y ''-- has 50+ Retweets & 31 Favorites''<br />
<br />
== 2012 EOWG Recent Contacts ==<br />
<br />
* '''Done:'''<br />
** UNDESA - Vicki (January 23, 2012)<br />
** ITU - Vicki (February 2, 2012)<br />
** WMO - Vicki (February 2, 2012)<br />
** ILO - Vicki (February 2, 2012)<br />
** WHO - Vicki (February 2, 2012)<br />
** OHCR - Vicki (February 2, 2012)<br />
** OHCA - Vicki (February 2, 2012)<br />
** UN NY (2)Vicki, positive feedback (February 2, 2012)<br />
** ITC - Vicki (February 2, 2012)<br />
** UNCTAD - Vicki (February 2, 2012)<br />
** UPU - Vicki (February 2, 2012)<br />
** EFSA - Vicki (February 2, 2012)<br />
** UNICEF - Vicki (February 2, 2012)<br />
** IAEA (2) - Vicki (February 2, 2012)<br />
** WTO - Vicki (February 2, 2012)<br />
** ICJ - Vicki (February 2, 2012)<br />
** WIPO (several)- Vicki, positive feedback (February 2, 2012)<br />
** Laura Carlson - Denis [Feb 8th]<br />
** Russ Weakly - Denis [Feb 8th]<br />
** Dennis Lembree - Denis [Feb 8th]<br />
** Léonie Watson - Denis [Feb 8th]<br />
** John Foliot - Denis [Feb 8th]<br />
** Jared W. Smith - Denis [Feb 8th]<br />
** Jason Kiss - Denis [Feb 8th]<br />
** David MacDonald - Denis [Feb 8th]<br />
** Kathy Wahlbin - Denis [Feb 8th]<br />
** Olivier Nourry - Denis [Feb 8th]<br />
** Glenda Sims - Denis [Feb 8th]<br />
** Karen Mardahl - Denis [Feb 8th]<br />
** Roger Hudson - Denis [Feb 8th]<br />
** Jennison Asuncion - Denis [Feb 8th]<br />
** Elle Waters - Denis [Feb 8th]<br />
** Karl Groves - Denis [Feb 8th]<br />
** Steve Buell - Denis [Feb 8th]<br />
** Matt May - Denis [Feb 8th]<br />
** Wendy Chisholm - Denis [Feb 8th]<br />
** Henny Swan - Denis [Feb 8th]<br />
** Molly Holzschlag - Denis [Feb 8th]<br />
** Andrew Kirkpatrick - Denis [Feb 8th]<br />
** Steve Faulkner - Denis [Feb 8th]<br />
** Mike Paciello - Denis [Feb 8th]<br />
** Bruce Lawson - Denis [Feb 8th]<br />
** Gez Lemon - Denis [Feb 8th]<br />
** Mike Gifford - Denis [Feb 8th]<br />
** WANAU list (Australian Universities) - Andrew [Feb 9th]<br />
** Distributed to a total of 31 personal contacts, and many of them are in the usability field. I sent the post Shawn sent to the WAI-IG list, and of course, I focused on choosing people who I don't believe are subscribed to WAI-IG or WebAIM. I sent to 15 people on January 31, and 16 more on February 12. As best I can tell, only one duplicates Denis's effort. (Jennifer)<br />
<br />
* To Do:<br />
** Derek Featherstone - Sharron<br />
** Access U presenters - Sharron (both CSUN and in Austin? -- Jennifer)<br />
** AccessU at CSUN "How We Use the Web" Demo," Feb. 27 (Jennifer)<br />
** UCal State list - Wayne<br />
** Web manager, developer lists - Jason<br />
** European design for all network (EDeAN)<br />
** RNIB - Vicki<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_BAD&diff=376Promoting BAD2012-02-13T01:39:36Z<p>Jsutton2: /* 2012 EOWG Recent Contacts */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, developers, teachers, trainers, and advocates about BAD.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)], short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare<br />
<br />
* Jan 2012 [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html WAI IG e-mail], [https://twitter.com/#!/w3c_wai/status/164452260707975168 tweet], [http://www.w3.org/WAI/highlights/archive#x20120131a WAI highlight & RSS feed]<br />
<br />
* <del>Supporting document http://www.w3.org/WAI/EO/2005/Demo/ About BAD </del> {this is old, don't point to it.}<br />
* Oct 2011 [http://twitter.com/#!/w3c_wai/status/124504842004742144 Tweet], [http://www.w3.org/WAI/highlights/archive#x20111013a WAI highlight & rss feed], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2011OctDec/0003.html WAI IG email]<br />
* Translations: (none)<br />
<br />
== Audiences ==<br />
<br />
* Teachers, trainers<br />
* Conference presenters<br />
* Web developers<br />
* Accessibility advocates<br />
* Web accessibility evaluators and testers<br />
* ([http://www.w3.org/WAI/EO/Drafts/retrofit/requ-basite.html old audience analysis])<br />
<br />
== Tweet ideas ==<br />
''(Note: short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare )''<br />
* BAD to Good: Demo shows example website with #accessibility barriers and fixes http://bit.ly/BADshare Useful for presentations. #a11y<br />
* BAD to Good: WAI demo website with #accessibility barriers and fixes http://bit.ly/BADdemo Useful for presentations. #a11y<br />
* Need to show web devs how to fix #accessibility issues without sacrificing visual style? http://bit.ly/BADdemo #a11y <br />
* Read about WAI's Before and After Demo (BAD) and use it to show #accessibility at work http://bit.ly/aboutBAD #a11y<br />
* Need practical examples of #accessibility coding techniques? WAI made Before and After Demo for you. http://bit.ly/BADdemo #a11y<br />
* Cool new site, easy to use and share to show accessible design techniques applied. @w3c_wai resource. http://bit.ly/BADdemo #a11y<br />
* Great resource for accidental accessibility team leads. Before and After Demo from @w3c_wai http://bit.ly/aboutBAD #a11y<br />
<br />
== Draft blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Audience: Teachers, trainers ===<br />
'''Use BAD to Train Developers to Create Great Pages for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Teaching web development professionals about web accessibility almost always includes the need to clear up misunderstandings about the impact of accessible design on visual style and presentation. The Web Accessibility Initiative (WAI) at the W3C has just updated a set of demonstration web pages to help trainers do just that.<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web and application developers believe that accessible web sites must be dull and lack interactivity. The [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)] is a free and useful teaching tool that gives trainers and internal accessibility advocates a set of practical examples, implemented within a set of related pages. Trainers can use BAD to demonstrate that pages can be fully accessible without changing the cool visual features that developers love.<br />
<br />
Dr. Wayne Dick is the former Chair of the Computer Science and Engineering Department at the University of California at Long Beach. <br />
<br />
“BAD is great for these reasons,” says Dr Dick. “And here is support for that…..”<br />
<br />
===Audience: Public speakers===<br />
'''BAD Shows Audiences How to Do Good for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Web accessibility means designing pages and applications so that they can be used by everyone, including people with disabilities, some of whom use assistive technologies to browse the web. Accessibility is required by federal law in many instances and courts are broadening their interpretation of how the legal requirements are implemented. Many know that web accessibility is an increasingly important issue, but are not sure what to do.<br />
<br />
It is not uncommon for individuals who recognize and speak up about the need for accessibility within an organization to find that they have become experts by default. For those in this situation and who are invited to speak to groups about web accessibility, an updated tool from the W3C’s [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) can help.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. Sharp, new, and fun to use, BAD is designed to serve a variety of purposes. In addition to raising general awareness of web accessibility issues, BAD is a highly effective way to show how [http://w3.org/WAI/into/WCAG/ Web Content Accessibility Guidelines] (WCAG 2) can be applied without sacrificing visual appeal or interactivity.<br />
<br />
BAD shows common accessibility barriers using practical examples. The demonstration consists of an inaccessible Web site, an accessible version of the same site, as well as a report about the demonstrated barriers. The demonstration does not attempt to cover every checkpoint of the Web Content Accessibility Guidelines (WCAG) nor to provide an exhaustive list of examples but to demonstrate some key aspects of Web accessibility appropriate for short, focused presentations.<br />
<br />
Demonstrating practical examples during presentation is usually very effective. The description pages provide an overview of the accessibility barriers and features that are shown in the Demo. Together with the inaccessible and accessible Demo pages, concrete before and after examples can be explained during presentations. <br />
<br />
Presenters are encouraged to use the demo live or to download the pages with the understanding that some pages will not have full interactivity without connection to a server. WAI is interested to hear if BAD is good for you. Please use the demo and then let WAI know about your experience. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
...insert contact info.<br />
<br />
=== Audience: Web developers ===<br />
<br />
'''Use BAD for Great Examples of Web Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Here is a resource tip for the next time you need to meet an accessibility requirement. You had that accessibility training a few weeks age but you’re not exactly certain what they said about radio buttons and don’t really have time to sort through the guidelines and techniques of the [http://www.w3.org/WAI/intro/wcag/ Web Content Accessibility Guidelines] (WCAG 2). When you need a good example, think BAD. <br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the [http://www.w3.org/WAI Web Accessibility Initiative] (WAI) at the W3C and it is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images. <br />
<br />
With BAD you can look at the inaccessible version of any of the four pages – Home, News, Tickets, and Survey; you can read a report about the accessibility barriers that were found; you can look at the same pages with accessibility fixes in place; you can look at the code; and you can download and use the page template, adapting it for your own needs. <br />
<br />
While the general information can be very helpful, you may want to hone in on the one problem you need to solve - that one tricky item where you just want to know what the accessibility problem is and how can it be fixed? BAD pages come in two versions. The Before page is the inaccessible version. The After page is the same page, same function, same visual design but with accessibility built in. You can look right at the code to see how the problem was solved. <br />
<br />
Use BAD for good accessibility outcomes. See more information about [http://www.w3.org/WAI/demos/bad/ BAD].<br />
{shawn: I'm not sure which links you want in this paragraph and the next. anyway, I updated them from the outdated /2005/ links :-}<br />
<br />
So the next time you need a good example of accessibility in action, think BAD. More about [http://www.w3.org/WAI/demos/bad/#howto how to use the demo] is found on the WAI site.<br />
<br />
=== Audience: Internal Accessibility Advocates and Testers ===<br />
<br />
'''W3C Releases BAD web accessibility demo for advocates and testers'''(initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web development teams delegate accessibility responsibility to a few or even to just to one team member. The [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) at the W3C has just updated a tool to help make that job easier.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is a set of related web pages that provide fully integrated examples of accessibility at work. Accessibility leads who are seeking ways to test, report, and convince fellow team members of practical accessibility techniques will find this a useful demonstration tool for many common accessibility errors. BAD puts accessibility in the context of a set of related web pages. <br />
<br />
BAD provides an inaccessible version of each of the four pages – Home, News, Tickets, and Survey. Each one has a corresponding report of accessibility barriers contained in the page. An accessible version of the same pages with accessibility fixes in place can be viewed to demonstrate that the visual style remains largely unchanged.<br />
<br />
In many instances, the real issues for people with disabilities are not clear to developers or managers. Browsing through the inaccessible Demo pages using different browser configurations or assistive technologies (such as screen readers and magnifiers) helps highlight these issues. {shawn: need to broaden to cover other disabilities & interaction, e.g., keyboard only} The accessible Demo pages can be browsed in the same manner to show the difference.<br />
<br />
A well written evaluation report is key in the process of retrofitting websites for accessibility. It communicates the problems to managers and the developers who need to decide which solutions to implement. The evaluation reports of the Demo serve as a sample format for evaluators.<br />
<br />
BAD is designed to serve a variety of purposes. Not only is BAD useful in raising general awareness of web accessibility issues, it also provides practical examples for developers and demonstrates that an accessible site can be just as visually appealing and interactive as the one with access barriers. If the tool is helpful, please consider sharing your experience with the creators at WAI. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
…insert contact info<br />
<br />
===Audience: Web Managers===<br />
'''Use BAD, a Good Example of Accessibility at work''' (initial editor Cliff Tillick) <br />
<br />
<del>Have you ever considered what it would cost to make your website accessible? If so, what has worried you most:</del><br />
<del>- The time required?</del><br />
<del>- The design features you might lose?</del><br />
<del>- The impact on usability?</del><br />
{Shawn: not comfortable with intro about cost, and especially the possible mis-read that accessibility will cause you to lose design features.}<br />
<br />
Wouldn’t it be nice if you could see an example of the difference an accessible website makes?<br />
Well now you can. But we should warn you, it’s BAD—as in “Before and After Demonstration.”<br />
Published through the W3C’s Web Accessibility Initiative, BAD is a mockup of a website that contains a number of common barriers to accessibility and, linked to it, a website that has the same information but without those barriers.<br />
<br />
The differences are hard to recognize—unless you use a screen reader or screen magnification to get information from these pages. {shawn: or keyboard only or... need to be inclusive!} Then the differences are obvious. {shawn: Otherwise, you might not notice them at all. that's because most of the differences are "under the covers" -that is, in the underlying code and they don't impact the visual design at all. ...}<br />
<br />
=== Notes on posts, blurbs, etc. ===<br />
<br />
* Brainstorming -- possible theme -- When something bad becomes good. Making BAD good. (Jennifer, January 8, 2012)<br />
<br />
* What did site code look like before and how is it now fixed? How BAD can improve awareness about Web accessibility. (Sylvie, January 10, 2012)<br />
<br />
* For UN Newsletter (submitted on Jan. 23): Revised version:<br/>'''Web Accessibility''':<br/>How to make a BAD site GREATLY accessible to people with disabilities, older users, and others: The Before and After Demo (BAD) is a newly released set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the Web Accessibility Initiative (WAI) at the W3C and is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images.<br />
<br />
== WAI IG e-mail ==<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html archived final e-mail]<br />
<br />
== 2012 blogs, newsletters, references, etc. ==<br />
<br />
<br />
* [http://blog.knowbility.org/content/use-bad-for-good-examples-of-accessibility-in-action/ Use BAD for Good Examples of Accessibility in Action] posted on January 31, 2012 on Knowbility's Universally Designed blog by Sharron <br />
* [http://lists.d.umn.edu/pipermail/webdev/2012q1/000629.html Web Design Update newsletter] (Laura Carlson) lead article in newsletter that has 2,500+ readers<br />
* United Nations Enable Newsletter - [http://www.un.org/disabilities/documents/newsletter/january2012.doc January 2012, MS-Word]<br />
* Notable tweets & retweets:<br />
** [https://twitter.com/#!/cinteractionlab/status/167242173098627072 @cityuni_hcid] could be useful for #inm313 students - BaD Demo for accessibility at bit.ly/BADdemo #w3c #wai #a11y (via @AdobeAccess)<br />
** [https://twitter.com/#!/dboudreau/status/167134289912283136 @dboudreau] and reply from [https://twitter.com/#!/Nethermind/status/167257448959324161 @Nethermind (Elle Waters)]: I used this last week for new dev teams to understand real examples of #accessibility impacts - thanks you!<br />
** [https://twitter.com/#!/w3c_wai/status/164452260707975168 w3c_wai] BAD to Good: Demo shows example website with #accessibility barriers and fixes bit.ly/BADshare Useful for presentations. #a11y ''-- has 50+ Retweets & 31 Favorites''<br />
<br />
== 2012 EOWG Recent Contacts ==<br />
<br />
* '''Done:'''<br />
<br />
** UNDESA - Vicki (January 23, 2012)<br />
** ITU - Vicki (February 2, 2012)<br />
** WMO - Vicki (February 2, 2012)<br />
** ILO - Vicki (February 2, 2012)<br />
** WHO - Vicki (February 2, 2012)<br />
** OHCR - Vicki (February 2, 2012)<br />
** OHCA - Vicki (February 2, 2012)<br />
** UN NY (2)Vicki, positive feedback (February 2, 2012)<br />
** ITC - Vicki (February 2, 2012)<br />
** UNCTAD - Vicki (February 2, 2012)<br />
** UPU - Vicki (February 2, 2012)<br />
** EFSA - Vicki (February 2, 2012)<br />
** UNICEF - Vicki (February 2, 2012)<br />
** IAEA (2) - Vicki (February 2, 2012)<br />
** WTO - Vicki (February 2, 2012)<br />
** ICJ - Vicki (February 2, 2012)<br />
** WIPO (several)- Vicki, positive feedback (February 2, 2012)<br />
** Laura Carlson - Denis [Feb 8th]<br />
** Russ Weakly - Denis [Feb 8th]<br />
** Dennis Lembree - Denis [Feb 8th]<br />
** Léonie Watson - Denis [Feb 8th]<br />
** John Foliot - Denis [Feb 8th]<br />
** Jared W. Smith - Denis [Feb 8th]<br />
** Jason Kiss - Denis [Feb 8th]<br />
** David MacDonald - Denis [Feb 8th]<br />
** Kathy Wahlbin - Denis [Feb 8th]<br />
** Olivier Nourry - Denis [Feb 8th]<br />
** Glenda Sims - Denis [Feb 8th]<br />
** Karen Mardahl - Denis [Feb 8th]<br />
** Roger Hudson - Denis [Feb 8th]<br />
** Jennison Asuncion - Denis [Feb 8th]<br />
** Elle Waters - Denis [Feb 8th]<br />
** Karl Groves - Denis [Feb 8th]<br />
** Steve Buell - Denis [Feb 8th]<br />
** Matt May - Denis [Feb 8th]<br />
** Wendy Chisholm - Denis [Feb 8th]<br />
** Henny Swan - Denis [Feb 8th]<br />
** Molly Holzschlag - Denis [Feb 8th]<br />
** Andrew Kirkpatrick - Denis [Feb 8th]<br />
** Steve Faulkner - Denis [Feb 8th]<br />
** Mike Paciello - Denis [Feb 8th]<br />
** Bruce Lawson - Denis [Feb 8th]<br />
** Gez Lemon - Denis [Feb 8th]<br />
** Mike Gifford - Denis [Feb 8th]<br />
** WANAU list (Australian Universities) - Andrew [Feb 9th]<br />
* To Do:<br />
** Derek Featherstone - Sharron<br />
** Access U presenters - Sharron (both CSUN and in Austin? -- Jennifer)<br />
** AccessU at CSUN "How We Use the Web" Demo," Feb. 27 (Jennifer)<br />
** UCal State list - Wayne<br />
** Web manager, developer lists - Jason<br />
** European design for all network (EDeAN)<br />
** RNIB - Vicki<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_BAD&diff=375Promoting BAD2012-02-13T01:36:50Z<p>Jsutton2: /* 2012 blogs, newsletters, references, etc. */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, developers, teachers, trainers, and advocates about BAD.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)], short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare<br />
<br />
* Jan 2012 [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html WAI IG e-mail], [https://twitter.com/#!/w3c_wai/status/164452260707975168 tweet], [http://www.w3.org/WAI/highlights/archive#x20120131a WAI highlight & RSS feed]<br />
<br />
* <del>Supporting document http://www.w3.org/WAI/EO/2005/Demo/ About BAD </del> {this is old, don't point to it.}<br />
* Oct 2011 [http://twitter.com/#!/w3c_wai/status/124504842004742144 Tweet], [http://www.w3.org/WAI/highlights/archive#x20111013a WAI highlight & rss feed], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2011OctDec/0003.html WAI IG email]<br />
* Translations: (none)<br />
<br />
== Audiences ==<br />
<br />
* Teachers, trainers<br />
* Conference presenters<br />
* Web developers<br />
* Accessibility advocates<br />
* Web accessibility evaluators and testers<br />
* ([http://www.w3.org/WAI/EO/Drafts/retrofit/requ-basite.html old audience analysis])<br />
<br />
== Tweet ideas ==<br />
''(Note: short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare )''<br />
* BAD to Good: Demo shows example website with #accessibility barriers and fixes http://bit.ly/BADshare Useful for presentations. #a11y<br />
* BAD to Good: WAI demo website with #accessibility barriers and fixes http://bit.ly/BADdemo Useful for presentations. #a11y<br />
* Need to show web devs how to fix #accessibility issues without sacrificing visual style? http://bit.ly/BADdemo #a11y <br />
* Read about WAI's Before and After Demo (BAD) and use it to show #accessibility at work http://bit.ly/aboutBAD #a11y<br />
* Need practical examples of #accessibility coding techniques? WAI made Before and After Demo for you. http://bit.ly/BADdemo #a11y<br />
* Cool new site, easy to use and share to show accessible design techniques applied. @w3c_wai resource. http://bit.ly/BADdemo #a11y<br />
* Great resource for accidental accessibility team leads. Before and After Demo from @w3c_wai http://bit.ly/aboutBAD #a11y<br />
<br />
== Draft blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Audience: Teachers, trainers ===<br />
'''Use BAD to Train Developers to Create Great Pages for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Teaching web development professionals about web accessibility almost always includes the need to clear up misunderstandings about the impact of accessible design on visual style and presentation. The Web Accessibility Initiative (WAI) at the W3C has just updated a set of demonstration web pages to help trainers do just that.<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web and application developers believe that accessible web sites must be dull and lack interactivity. The [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)] is a free and useful teaching tool that gives trainers and internal accessibility advocates a set of practical examples, implemented within a set of related pages. Trainers can use BAD to demonstrate that pages can be fully accessible without changing the cool visual features that developers love.<br />
<br />
Dr. Wayne Dick is the former Chair of the Computer Science and Engineering Department at the University of California at Long Beach. <br />
<br />
“BAD is great for these reasons,” says Dr Dick. “And here is support for that…..”<br />
<br />
===Audience: Public speakers===<br />
'''BAD Shows Audiences How to Do Good for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Web accessibility means designing pages and applications so that they can be used by everyone, including people with disabilities, some of whom use assistive technologies to browse the web. Accessibility is required by federal law in many instances and courts are broadening their interpretation of how the legal requirements are implemented. Many know that web accessibility is an increasingly important issue, but are not sure what to do.<br />
<br />
It is not uncommon for individuals who recognize and speak up about the need for accessibility within an organization to find that they have become experts by default. For those in this situation and who are invited to speak to groups about web accessibility, an updated tool from the W3C’s [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) can help.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. Sharp, new, and fun to use, BAD is designed to serve a variety of purposes. In addition to raising general awareness of web accessibility issues, BAD is a highly effective way to show how [http://w3.org/WAI/into/WCAG/ Web Content Accessibility Guidelines] (WCAG 2) can be applied without sacrificing visual appeal or interactivity.<br />
<br />
BAD shows common accessibility barriers using practical examples. The demonstration consists of an inaccessible Web site, an accessible version of the same site, as well as a report about the demonstrated barriers. The demonstration does not attempt to cover every checkpoint of the Web Content Accessibility Guidelines (WCAG) nor to provide an exhaustive list of examples but to demonstrate some key aspects of Web accessibility appropriate for short, focused presentations.<br />
<br />
Demonstrating practical examples during presentation is usually very effective. The description pages provide an overview of the accessibility barriers and features that are shown in the Demo. Together with the inaccessible and accessible Demo pages, concrete before and after examples can be explained during presentations. <br />
<br />
Presenters are encouraged to use the demo live or to download the pages with the understanding that some pages will not have full interactivity without connection to a server. WAI is interested to hear if BAD is good for you. Please use the demo and then let WAI know about your experience. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
...insert contact info.<br />
<br />
=== Audience: Web developers ===<br />
<br />
'''Use BAD for Great Examples of Web Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Here is a resource tip for the next time you need to meet an accessibility requirement. You had that accessibility training a few weeks age but you’re not exactly certain what they said about radio buttons and don’t really have time to sort through the guidelines and techniques of the [http://www.w3.org/WAI/intro/wcag/ Web Content Accessibility Guidelines] (WCAG 2). When you need a good example, think BAD. <br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the [http://www.w3.org/WAI Web Accessibility Initiative] (WAI) at the W3C and it is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images. <br />
<br />
With BAD you can look at the inaccessible version of any of the four pages – Home, News, Tickets, and Survey; you can read a report about the accessibility barriers that were found; you can look at the same pages with accessibility fixes in place; you can look at the code; and you can download and use the page template, adapting it for your own needs. <br />
<br />
While the general information can be very helpful, you may want to hone in on the one problem you need to solve - that one tricky item where you just want to know what the accessibility problem is and how can it be fixed? BAD pages come in two versions. The Before page is the inaccessible version. The After page is the same page, same function, same visual design but with accessibility built in. You can look right at the code to see how the problem was solved. <br />
<br />
Use BAD for good accessibility outcomes. See more information about [http://www.w3.org/WAI/demos/bad/ BAD].<br />
{shawn: I'm not sure which links you want in this paragraph and the next. anyway, I updated them from the outdated /2005/ links :-}<br />
<br />
So the next time you need a good example of accessibility in action, think BAD. More about [http://www.w3.org/WAI/demos/bad/#howto how to use the demo] is found on the WAI site.<br />
<br />
=== Audience: Internal Accessibility Advocates and Testers ===<br />
<br />
'''W3C Releases BAD web accessibility demo for advocates and testers'''(initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web development teams delegate accessibility responsibility to a few or even to just to one team member. The [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) at the W3C has just updated a tool to help make that job easier.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is a set of related web pages that provide fully integrated examples of accessibility at work. Accessibility leads who are seeking ways to test, report, and convince fellow team members of practical accessibility techniques will find this a useful demonstration tool for many common accessibility errors. BAD puts accessibility in the context of a set of related web pages. <br />
<br />
BAD provides an inaccessible version of each of the four pages – Home, News, Tickets, and Survey. Each one has a corresponding report of accessibility barriers contained in the page. An accessible version of the same pages with accessibility fixes in place can be viewed to demonstrate that the visual style remains largely unchanged.<br />
<br />
In many instances, the real issues for people with disabilities are not clear to developers or managers. Browsing through the inaccessible Demo pages using different browser configurations or assistive technologies (such as screen readers and magnifiers) helps highlight these issues. {shawn: need to broaden to cover other disabilities & interaction, e.g., keyboard only} The accessible Demo pages can be browsed in the same manner to show the difference.<br />
<br />
A well written evaluation report is key in the process of retrofitting websites for accessibility. It communicates the problems to managers and the developers who need to decide which solutions to implement. The evaluation reports of the Demo serve as a sample format for evaluators.<br />
<br />
BAD is designed to serve a variety of purposes. Not only is BAD useful in raising general awareness of web accessibility issues, it also provides practical examples for developers and demonstrates that an accessible site can be just as visually appealing and interactive as the one with access barriers. If the tool is helpful, please consider sharing your experience with the creators at WAI. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
…insert contact info<br />
<br />
===Audience: Web Managers===<br />
'''Use BAD, a Good Example of Accessibility at work''' (initial editor Cliff Tillick) <br />
<br />
<del>Have you ever considered what it would cost to make your website accessible? If so, what has worried you most:</del><br />
<del>- The time required?</del><br />
<del>- The design features you might lose?</del><br />
<del>- The impact on usability?</del><br />
{Shawn: not comfortable with intro about cost, and especially the possible mis-read that accessibility will cause you to lose design features.}<br />
<br />
Wouldn’t it be nice if you could see an example of the difference an accessible website makes?<br />
Well now you can. But we should warn you, it’s BAD—as in “Before and After Demonstration.”<br />
Published through the W3C’s Web Accessibility Initiative, BAD is a mockup of a website that contains a number of common barriers to accessibility and, linked to it, a website that has the same information but without those barriers.<br />
<br />
The differences are hard to recognize—unless you use a screen reader or screen magnification to get information from these pages. {shawn: or keyboard only or... need to be inclusive!} Then the differences are obvious. {shawn: Otherwise, you might not notice them at all. that's because most of the differences are "under the covers" -that is, in the underlying code and they don't impact the visual design at all. ...}<br />
<br />
=== Notes on posts, blurbs, etc. ===<br />
<br />
* Brainstorming -- possible theme -- When something bad becomes good. Making BAD good. (Jennifer, January 8, 2012)<br />
<br />
* What did site code look like before and how is it now fixed? How BAD can improve awareness about Web accessibility. (Sylvie, January 10, 2012)<br />
<br />
* For UN Newsletter (submitted on Jan. 23): Revised version:<br/>'''Web Accessibility''':<br/>How to make a BAD site GREATLY accessible to people with disabilities, older users, and others: The Before and After Demo (BAD) is a newly released set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the Web Accessibility Initiative (WAI) at the W3C and is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images.<br />
<br />
== WAI IG e-mail ==<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html archived final e-mail]<br />
<br />
== 2012 blogs, newsletters, references, etc. ==<br />
<br />
<br />
* [http://blog.knowbility.org/content/use-bad-for-good-examples-of-accessibility-in-action/ Use BAD for Good Examples of Accessibility in Action] posted on January 31, 2012 on Knowbility's Universally Designed blog by Sharron <br />
* [http://lists.d.umn.edu/pipermail/webdev/2012q1/000629.html Web Design Update newsletter] (Laura Carlson) lead article in newsletter that has 2,500+ readers<br />
* United Nations Enable Newsletter - [http://www.un.org/disabilities/documents/newsletter/january2012.doc January 2012, MS-Word]<br />
* Notable tweets & retweets:<br />
** [https://twitter.com/#!/cinteractionlab/status/167242173098627072 @cityuni_hcid] could be useful for #inm313 students - BaD Demo for accessibility at bit.ly/BADdemo #w3c #wai #a11y (via @AdobeAccess)<br />
** [https://twitter.com/#!/dboudreau/status/167134289912283136 @dboudreau] and reply from [https://twitter.com/#!/Nethermind/status/167257448959324161 @Nethermind (Elle Waters)]: I used this last week for new dev teams to understand real examples of #accessibility impacts - thanks you!<br />
** [https://twitter.com/#!/w3c_wai/status/164452260707975168 w3c_wai] BAD to Good: Demo shows example website with #accessibility barriers and fixes bit.ly/BADshare Useful for presentations. #a11y ''-- has 50+ Retweets & 31 Favorites''<br />
<br />
== 2012 EOWG Recent Contacts ==<br />
<br />
* '''Done:'''<br />
<br />
** UNDESA - Vicki (January 23, 2012)<br />
** [http://blog.knowbility.org/content/use-bad-for-good-examples-of-accessibility-in-action/ Use BAD for Good Examples of Accessibility in Action] posted on January 31, 2012 on Knowbility's Universally Designed blog by Sharron <br />
** ITU - Vicki (February 2, 2012)<br />
** WMO - Vicki (February 2, 2012)<br />
** ILO - Vicki (February 2, 2012)<br />
** WHO - Vicki (February 2, 2012)<br />
** OHCR - Vicki (February 2, 2012)<br />
** OHCA - Vicki (February 2, 2012)<br />
** UN NY (2)Vicki, positive feedback (February 2, 2012)<br />
** ITC - Vicki (February 2, 2012)<br />
** UNCTAD - Vicki (February 2, 2012)<br />
** UPU - Vicki (February 2, 2012)<br />
** EFSA - Vicki (February 2, 2012)<br />
** UNICEF - Vicki (February 2, 2012)<br />
** IAEA (2) - Vicki (February 2, 2012)<br />
** WTO - Vicki (February 2, 2012)<br />
** ICJ - Vicki (February 2, 2012)<br />
** WIPO (several)- Vicki, positive feedback (February 2, 2012)<br />
** Laura Carlson - Denis [Feb 8th]<br />
** Russ Weakly - Denis [Feb 8th]<br />
** Dennis Lembree - Denis [Feb 8th]<br />
** Léonie Watson - Denis [Feb 8th]<br />
** John Foliot - Denis [Feb 8th]<br />
** Jared W. Smith - Denis [Feb 8th]<br />
** Jason Kiss - Denis [Feb 8th]<br />
** David MacDonald - Denis [Feb 8th]<br />
** Kathy Wahlbin - Denis [Feb 8th]<br />
** Olivier Nourry - Denis [Feb 8th]<br />
** Glenda Sims - Denis [Feb 8th]<br />
** Karen Mardahl - Denis [Feb 8th]<br />
** Roger Hudson - Denis [Feb 8th]<br />
** Jennison Asuncion - Denis [Feb 8th]<br />
** Elle Waters - Denis [Feb 8th]<br />
** Karl Groves - Denis [Feb 8th]<br />
** Steve Buell - Denis [Feb 8th]<br />
** Matt May - Denis [Feb 8th]<br />
** Wendy Chisholm - Denis [Feb 8th]<br />
** Henny Swan - Denis [Feb 8th]<br />
** Molly Holzschlag - Denis [Feb 8th]<br />
** Andrew Kirkpatrick - Denis [Feb 8th]<br />
** Steve Faulkner - Denis [Feb 8th]<br />
** Mike Paciello - Denis [Feb 8th]<br />
** Bruce Lawson - Denis [Feb 8th]<br />
** Gez Lemon - Denis [Feb 8th]<br />
** Mike Gifford - Denis [Feb 8th]<br />
** WANAU list (Australian Universities) - Andrew [Feb 9th]<br />
* To Do:<br />
** Derek Featherstone - Sharron<br />
** Access U presenters - Sharron (both CSUN and in Austin? -- Jennifer)<br />
** AccessU at CSUN "How We Use the Web" Demo," Feb. 27 (Jennifer)<br />
** UCal State list - Wayne<br />
** Web manager, developer lists - Jason<br />
** European design for all network (EDeAN)<br />
** RNIB - Vicki<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_BAD&diff=374Promoting BAD2012-02-13T01:32:54Z<p>Jsutton2: </p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, developers, teachers, trainers, and advocates about BAD.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)], short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare<br />
<br />
* Jan 2012 [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html WAI IG e-mail], [https://twitter.com/#!/w3c_wai/status/164452260707975168 tweet], [http://www.w3.org/WAI/highlights/archive#x20120131a WAI highlight & RSS feed]<br />
<br />
* <del>Supporting document http://www.w3.org/WAI/EO/2005/Demo/ About BAD </del> {this is old, don't point to it.}<br />
* Oct 2011 [http://twitter.com/#!/w3c_wai/status/124504842004742144 Tweet], [http://www.w3.org/WAI/highlights/archive#x20111013a WAI highlight & rss feed], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2011OctDec/0003.html WAI IG email]<br />
* Translations: (none)<br />
<br />
== Audiences ==<br />
<br />
* Teachers, trainers<br />
* Conference presenters<br />
* Web developers<br />
* Accessibility advocates<br />
* Web accessibility evaluators and testers<br />
* ([http://www.w3.org/WAI/EO/Drafts/retrofit/requ-basite.html old audience analysis])<br />
<br />
== Tweet ideas ==<br />
''(Note: short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare )''<br />
* BAD to Good: Demo shows example website with #accessibility barriers and fixes http://bit.ly/BADshare Useful for presentations. #a11y<br />
* BAD to Good: WAI demo website with #accessibility barriers and fixes http://bit.ly/BADdemo Useful for presentations. #a11y<br />
* Need to show web devs how to fix #accessibility issues without sacrificing visual style? http://bit.ly/BADdemo #a11y <br />
* Read about WAI's Before and After Demo (BAD) and use it to show #accessibility at work http://bit.ly/aboutBAD #a11y<br />
* Need practical examples of #accessibility coding techniques? WAI made Before and After Demo for you. http://bit.ly/BADdemo #a11y<br />
* Cool new site, easy to use and share to show accessible design techniques applied. @w3c_wai resource. http://bit.ly/BADdemo #a11y<br />
* Great resource for accidental accessibility team leads. Before and After Demo from @w3c_wai http://bit.ly/aboutBAD #a11y<br />
<br />
== Draft blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Audience: Teachers, trainers ===<br />
'''Use BAD to Train Developers to Create Great Pages for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Teaching web development professionals about web accessibility almost always includes the need to clear up misunderstandings about the impact of accessible design on visual style and presentation. The Web Accessibility Initiative (WAI) at the W3C has just updated a set of demonstration web pages to help trainers do just that.<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web and application developers believe that accessible web sites must be dull and lack interactivity. The [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)] is a free and useful teaching tool that gives trainers and internal accessibility advocates a set of practical examples, implemented within a set of related pages. Trainers can use BAD to demonstrate that pages can be fully accessible without changing the cool visual features that developers love.<br />
<br />
Dr. Wayne Dick is the former Chair of the Computer Science and Engineering Department at the University of California at Long Beach. <br />
<br />
“BAD is great for these reasons,” says Dr Dick. “And here is support for that…..”<br />
<br />
===Audience: Public speakers===<br />
'''BAD Shows Audiences How to Do Good for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Web accessibility means designing pages and applications so that they can be used by everyone, including people with disabilities, some of whom use assistive technologies to browse the web. Accessibility is required by federal law in many instances and courts are broadening their interpretation of how the legal requirements are implemented. Many know that web accessibility is an increasingly important issue, but are not sure what to do.<br />
<br />
It is not uncommon for individuals who recognize and speak up about the need for accessibility within an organization to find that they have become experts by default. For those in this situation and who are invited to speak to groups about web accessibility, an updated tool from the W3C’s [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) can help.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. Sharp, new, and fun to use, BAD is designed to serve a variety of purposes. In addition to raising general awareness of web accessibility issues, BAD is a highly effective way to show how [http://w3.org/WAI/into/WCAG/ Web Content Accessibility Guidelines] (WCAG 2) can be applied without sacrificing visual appeal or interactivity.<br />
<br />
BAD shows common accessibility barriers using practical examples. The demonstration consists of an inaccessible Web site, an accessible version of the same site, as well as a report about the demonstrated barriers. The demonstration does not attempt to cover every checkpoint of the Web Content Accessibility Guidelines (WCAG) nor to provide an exhaustive list of examples but to demonstrate some key aspects of Web accessibility appropriate for short, focused presentations.<br />
<br />
Demonstrating practical examples during presentation is usually very effective. The description pages provide an overview of the accessibility barriers and features that are shown in the Demo. Together with the inaccessible and accessible Demo pages, concrete before and after examples can be explained during presentations. <br />
<br />
Presenters are encouraged to use the demo live or to download the pages with the understanding that some pages will not have full interactivity without connection to a server. WAI is interested to hear if BAD is good for you. Please use the demo and then let WAI know about your experience. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
...insert contact info.<br />
<br />
=== Audience: Web developers ===<br />
<br />
'''Use BAD for Great Examples of Web Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Here is a resource tip for the next time you need to meet an accessibility requirement. You had that accessibility training a few weeks age but you’re not exactly certain what they said about radio buttons and don’t really have time to sort through the guidelines and techniques of the [http://www.w3.org/WAI/intro/wcag/ Web Content Accessibility Guidelines] (WCAG 2). When you need a good example, think BAD. <br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the [http://www.w3.org/WAI Web Accessibility Initiative] (WAI) at the W3C and it is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images. <br />
<br />
With BAD you can look at the inaccessible version of any of the four pages – Home, News, Tickets, and Survey; you can read a report about the accessibility barriers that were found; you can look at the same pages with accessibility fixes in place; you can look at the code; and you can download and use the page template, adapting it for your own needs. <br />
<br />
While the general information can be very helpful, you may want to hone in on the one problem you need to solve - that one tricky item where you just want to know what the accessibility problem is and how can it be fixed? BAD pages come in two versions. The Before page is the inaccessible version. The After page is the same page, same function, same visual design but with accessibility built in. You can look right at the code to see how the problem was solved. <br />
<br />
Use BAD for good accessibility outcomes. See more information about [http://www.w3.org/WAI/demos/bad/ BAD].<br />
{shawn: I'm not sure which links you want in this paragraph and the next. anyway, I updated them from the outdated /2005/ links :-}<br />
<br />
So the next time you need a good example of accessibility in action, think BAD. More about [http://www.w3.org/WAI/demos/bad/#howto how to use the demo] is found on the WAI site.<br />
<br />
=== Audience: Internal Accessibility Advocates and Testers ===<br />
<br />
'''W3C Releases BAD web accessibility demo for advocates and testers'''(initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web development teams delegate accessibility responsibility to a few or even to just to one team member. The [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) at the W3C has just updated a tool to help make that job easier.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is a set of related web pages that provide fully integrated examples of accessibility at work. Accessibility leads who are seeking ways to test, report, and convince fellow team members of practical accessibility techniques will find this a useful demonstration tool for many common accessibility errors. BAD puts accessibility in the context of a set of related web pages. <br />
<br />
BAD provides an inaccessible version of each of the four pages – Home, News, Tickets, and Survey. Each one has a corresponding report of accessibility barriers contained in the page. An accessible version of the same pages with accessibility fixes in place can be viewed to demonstrate that the visual style remains largely unchanged.<br />
<br />
In many instances, the real issues for people with disabilities are not clear to developers or managers. Browsing through the inaccessible Demo pages using different browser configurations or assistive technologies (such as screen readers and magnifiers) helps highlight these issues. {shawn: need to broaden to cover other disabilities & interaction, e.g., keyboard only} The accessible Demo pages can be browsed in the same manner to show the difference.<br />
<br />
A well written evaluation report is key in the process of retrofitting websites for accessibility. It communicates the problems to managers and the developers who need to decide which solutions to implement. The evaluation reports of the Demo serve as a sample format for evaluators.<br />
<br />
BAD is designed to serve a variety of purposes. Not only is BAD useful in raising general awareness of web accessibility issues, it also provides practical examples for developers and demonstrates that an accessible site can be just as visually appealing and interactive as the one with access barriers. If the tool is helpful, please consider sharing your experience with the creators at WAI. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
…insert contact info<br />
<br />
===Audience: Web Managers===<br />
'''Use BAD, a Good Example of Accessibility at work''' (initial editor Cliff Tillick) <br />
<br />
<del>Have you ever considered what it would cost to make your website accessible? If so, what has worried you most:</del><br />
<del>- The time required?</del><br />
<del>- The design features you might lose?</del><br />
<del>- The impact on usability?</del><br />
{Shawn: not comfortable with intro about cost, and especially the possible mis-read that accessibility will cause you to lose design features.}<br />
<br />
Wouldn’t it be nice if you could see an example of the difference an accessible website makes?<br />
Well now you can. But we should warn you, it’s BAD—as in “Before and After Demonstration.”<br />
Published through the W3C’s Web Accessibility Initiative, BAD is a mockup of a website that contains a number of common barriers to accessibility and, linked to it, a website that has the same information but without those barriers.<br />
<br />
The differences are hard to recognize—unless you use a screen reader or screen magnification to get information from these pages. {shawn: or keyboard only or... need to be inclusive!} Then the differences are obvious. {shawn: Otherwise, you might not notice them at all. that's because most of the differences are "under the covers" -that is, in the underlying code and they don't impact the visual design at all. ...}<br />
<br />
=== Notes on posts, blurbs, etc. ===<br />
<br />
* Brainstorming -- possible theme -- When something bad becomes good. Making BAD good. (Jennifer, January 8, 2012)<br />
<br />
* What did site code look like before and how is it now fixed? How BAD can improve awareness about Web accessibility. (Sylvie, January 10, 2012)<br />
<br />
* For UN Newsletter (submitted on Jan. 23): Revised version:<br/>'''Web Accessibility''':<br/>How to make a BAD site GREATLY accessible to people with disabilities, older users, and others: The Before and After Demo (BAD) is a newly released set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the Web Accessibility Initiative (WAI) at the W3C and is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images.<br />
<br />
== WAI IG e-mail ==<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html archived final e-mail]<br />
<br />
== 2012 blogs, newsletters, references, etc. ==<br />
<br />
* [http://lists.d.umn.edu/pipermail/webdev/2012q1/000629.html Web Design Update newsletter] (Laura Carlson) lead article in newsletter that has 2,500+ readers<br />
* United Nations Enable Newsletter - [http://www.un.org/disabilities/documents/newsletter/january2012.doc January 2012, MS-Word]<br />
* Notable tweets & retweets:<br />
** [https://twitter.com/#!/cinteractionlab/status/167242173098627072 @cityuni_hcid] could be useful for #inm313 students - BaD Demo for accessibility at bit.ly/BADdemo #w3c #wai #a11y (via @AdobeAccess)<br />
** [https://twitter.com/#!/dboudreau/status/167134289912283136 @dboudreau] and reply from [https://twitter.com/#!/Nethermind/status/167257448959324161 @Nethermind (Elle Waters)]: I used this last week for new dev teams to understand real examples of #accessibility impacts - thanks you!<br />
** [https://twitter.com/#!/w3c_wai/status/164452260707975168 w3c_wai] BAD to Good: Demo shows example website with #accessibility barriers and fixes bit.ly/BADshare Useful for presentations. #a11y ''-- has 50+ Retweets & 31 Favorites''<br />
<br />
== 2012 EOWG Recent Contacts ==<br />
<br />
* '''Done:'''<br />
<br />
** UNDESA - Vicki (January 23, 2012)<br />
** [http://blog.knowbility.org/content/use-bad-for-good-examples-of-accessibility-in-action/ Use BAD for Good Examples of Accessibility in Action] posted on January 31, 2012 on Knowbility's Universally Designed blog by Sharron <br />
** ITU - Vicki (February 2, 2012)<br />
** WMO - Vicki (February 2, 2012)<br />
** ILO - Vicki (February 2, 2012)<br />
** WHO - Vicki (February 2, 2012)<br />
** OHCR - Vicki (February 2, 2012)<br />
** OHCA - Vicki (February 2, 2012)<br />
** UN NY (2)Vicki, positive feedback (February 2, 2012)<br />
** ITC - Vicki (February 2, 2012)<br />
** UNCTAD - Vicki (February 2, 2012)<br />
** UPU - Vicki (February 2, 2012)<br />
** EFSA - Vicki (February 2, 2012)<br />
** UNICEF - Vicki (February 2, 2012)<br />
** IAEA (2) - Vicki (February 2, 2012)<br />
** WTO - Vicki (February 2, 2012)<br />
** ICJ - Vicki (February 2, 2012)<br />
** WIPO (several)- Vicki, positive feedback (February 2, 2012)<br />
** Laura Carlson - Denis [Feb 8th]<br />
** Russ Weakly - Denis [Feb 8th]<br />
** Dennis Lembree - Denis [Feb 8th]<br />
** Léonie Watson - Denis [Feb 8th]<br />
** John Foliot - Denis [Feb 8th]<br />
** Jared W. Smith - Denis [Feb 8th]<br />
** Jason Kiss - Denis [Feb 8th]<br />
** David MacDonald - Denis [Feb 8th]<br />
** Kathy Wahlbin - Denis [Feb 8th]<br />
** Olivier Nourry - Denis [Feb 8th]<br />
** Glenda Sims - Denis [Feb 8th]<br />
** Karen Mardahl - Denis [Feb 8th]<br />
** Roger Hudson - Denis [Feb 8th]<br />
** Jennison Asuncion - Denis [Feb 8th]<br />
** Elle Waters - Denis [Feb 8th]<br />
** Karl Groves - Denis [Feb 8th]<br />
** Steve Buell - Denis [Feb 8th]<br />
** Matt May - Denis [Feb 8th]<br />
** Wendy Chisholm - Denis [Feb 8th]<br />
** Henny Swan - Denis [Feb 8th]<br />
** Molly Holzschlag - Denis [Feb 8th]<br />
** Andrew Kirkpatrick - Denis [Feb 8th]<br />
** Steve Faulkner - Denis [Feb 8th]<br />
** Mike Paciello - Denis [Feb 8th]<br />
** Bruce Lawson - Denis [Feb 8th]<br />
** Gez Lemon - Denis [Feb 8th]<br />
** Mike Gifford - Denis [Feb 8th]<br />
** WANAU list (Australian Universities) - Andrew [Feb 9th]<br />
* To Do:<br />
** Derek Featherstone - Sharron<br />
** Access U presenters - Sharron (both CSUN and in Austin? -- Jennifer)<br />
** AccessU at CSUN "How We Use the Web" Demo," Feb. 27 (Jennifer)<br />
** UCal State list - Wayne<br />
** Web manager, developer lists - Jason<br />
** European design for all network (EDeAN)<br />
** RNIB - Vicki<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=372Promoting Make Presentations Accessible2012-02-10T05:49:17Z<p>Jsutton2: /* Conferences */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc; border-top: 1px solid #930;">'''IMPORTANT''': The document How to Make Presentations Accessible is '''not ready for promotion yet'''! It's still a draft.</span><br/><span style="background-color: #ffffcc; border-bottom: 1px solid #930;">When it is ready, we'll send e-mail to WAI IG list and [http://www.w3.org/WAI/about/announcements other announcements].</span><br />
<br />
=== Resources & Pointers ===<br />
<br />
* Doc: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight June 2010]<br />
* [http://www.w3.org/QA/2010/06/make_your_presentations_access.html WAI blog June 2010]<br />
* Tweet June 2010<br />
* Translations: (none yet)<br />
<br />
<span style="background-color: #ffffcc; border-top: 1px solid #930;">'''IMPORTANT''': The document How to Make Presentations Accessible is '''not ready for promotion yet'''! It's still a draft.</span><br/><span style="background-color: #ffffcc; border-bottom: 1px solid #930;">When it is ready, we'll send e-mail to WAI IG list and [http://www.w3.org/WAI/about/announcements other announcements].</span><br />
<br />
=== Audience & Messages ===<br />
<br />
# Conference organizers - make your whole conference accessible, require that your speakers make their presentations accessible<br />
# Presenters - reach all of your audience!<br />
<br />
=== Draft posts/blurbs ===<br />
<br />
''Do you remember a time when people around you broke out in laughter, but you didn't hear the joke?''<br /><br />
''You could be doing a similar thing to your audience — leaving some people out. For example, if you say "you can read it on the slide", you're probably excluding people who can't see the slide.''<br /><br />
<br />
[http://www.w3.org/WAI/training/accessible How to Make Presentations Accessible to All] is an updated WAI resource that helps you make presentations, talks, meetings, and training accessible to all of your potential audience, including people with disabilities and others. It covers planning, preparing slides, providing accessible material, considerations during your session, and more. It also mentions some of the [http://www.w3.org/WAI/training/accessible#benefits many benefits of inclusive presentations].<br />
<br />
...<br />
<br />
Presentations that are accessible to people with disabilities are inclusive to many more audiences as well, including people who are not fluent in the language and people with different learning styles. Accessible presentations also have additional benefits, such as in these situations:<br />
* Consider a live presentation with visuals that is recorded and made available online as an audio podcast. If during the presentation you described the visuals (for people who are blind or otherwise cannot see them well), then those listening to the podcast will also get the visual information.<br />
* CART provides real-time text of the speaker and other audio. CART is used by people who are deaf or hard of hearing, people who can understand text better than spoken language — including people whose native language is different, and others. CART output can also be used to develop a transcript.<br />
* Transcripts can be put online to increase search engine optimization (SEO) and realize the other benefits of transcripts .<br />
<br />
=== Tweet ideas ===<br />
...<br />
<br />
=== Draft e-mails ===<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2010AprJun/0065.html June 2012 WAI IG e-mail]<br />
<br />
==== To conference organizers: ====<br />
* add a link to this document on your website<br />
* include in material provided to presenters<br />
==== To presenters: ====<br />
...<br />
<br />
=== 2012 blogs, newsletters, references, etc. ===<br />
...<br />
<br />
=== 2012 EOWG Recent Contacts ===<br />
<br />
==== Done: ====<br />
<br />
==== To Do: ====<br />
<br />
===== Conferences =====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* ATIA?<br />
* CSUN<br />
* European eAccessibility Forum<br />
* AccessU conferences held by Knowbility (In 2012, Feb. 27 and 28 in San Diego for CSUN and May 15 to 17 in Austin -- Jennifer)<br />
* ICCHP<br />
* SXSW<br />
* Accessibility barcamps/unconferences including:<br />
** [http://www.a11ycamp.org/ a11y Camp] (as of Feb. 9, still lists 2011 dates, but is a source of camp dates and links throughout the year -- Jennifer)<br />
** [http://www.accessibilitycamp.org/ Accessibility Camp] (another collection, but with more history -- Jennifer)<br />
** [http://www.accessibilitycampdc.org/ Accessibility Camp DC] (October 13, 2012 -- Jennifer)<br />
** [http://www.accessconf.ca/ Aiming for Accessibility Creating Barrier-Free Information and Communication University of Guelph] to be held May 29 and 30, 2012 -- Jennifer)<br />
** Accessibility Camp Los Angeles - October 20, 2012 (no link, yet -- Jennifer)<br />
* An Event Apart<br />
* [http://www.webdirections.org/ Web Directions] conf series<br />
* [http://www.w4a.info/2012/ W4A]<br />
* [http://www.webstock.org.nz/ Webstock]<br />
* [http://eotw.com.au/ Edge of the Web]<br />
* ...<br />
(Andrew wonders why just conferences that have a primary target of WAI work? - ah, because of EO's charter? {shawn replies: yup.})<br />
<br />
Vicki says: even so, :) many others to reach, so I would like to propose contacting: UN Organizations, I can reach the conference persons in a number of the organizations (e.g. UNOG, UN NY, ITU, ILO, WHO, UNCTAD, UNHCR, UNDESA etc.) {shawn happy for you to contact all these!!!}<br />
<br />
===== Presenters & bloggers that presenters read=====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
===== Misc =====<br />
* [http://www.linkedin.com/ LinkedIn] groups<br />
** ''{done, Dec 2011, Andrew}'' in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups, e.g. [http://www.linkedin.com/groupItem?view=&gid=3420162&type=member&item=84952130&qid=028e67fc-f9fc-4186-9a33-7647e24996eb&trk=group_most_popular-0-b-cmr&goback=%2Egmp_3420162 eaccessplus]; [http://www.linkedin.com/groupItem?view=&gid=889757&type=member&item=84952151&qid=962532df-6abc-44d6-94c8-14fec448c6ac&trk=group_most_popular-0-b-cmr&goback=%2Egmp_889757%2Egde_889757_member_84952151%2Egmp_889757 eINCLUSION]; [http://www.linkedin.com/groups/10-steps-making-your-meeting-2419815%2ES%2E84019877?qid=5230b9b3-202c-4ef1-8d6e-8c12fa3e152f&trk=group_most_popular-0-b-cmr&goback=%2Egmp_2419815 IBM Accessibility]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=84952131&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility]<br />
** ''{done, Dec 2011}'' as a discussion starter on several groups including: [http://www.linkedin.com/groups/Breaking-Barriers-Technology-163162?trk=myg_ugrp_ovr Breaking the Barriers of Technology]; [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=871b15fd-cf26-4d7d-80c8-02edf1699265&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility]<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_BAD&diff=371Promoting BAD2012-02-10T05:15:52Z<p>Jsutton2: </p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
<span style="background-color: #ffffcc;">We welcome your help telling presenters, developers, teachers, trainers, and advocates about BAD.<br/>'''You are welcome to use the sample wording below for your own blog posts, newsletter articles, etc.'''<br/>If you write a blog, newsletter article, or such, ''please let us know'' by sending e-mail to wai-eo-editors@w3.org and we'll add it to our list.</span><br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)], short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare<br />
<br />
* Jan 2012 [http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html WAI IG e-mail], [https://twitter.com/#!/w3c_wai/status/164452260707975168 tweet], [http://www.w3.org/WAI/highlights/archive#x20120131a WAI highlight & RSS feed]<br />
<br />
* <del>Supporting document http://www.w3.org/WAI/EO/2005/Demo/ About BAD </del> {this is old, don't point to it.}<br />
* Oct 2011 [http://twitter.com/#!/w3c_wai/status/124504842004742144 Tweet], [http://www.w3.org/WAI/highlights/archive#x20111013a WAI highlight & rss feed], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2011OctDec/0003.html WAI IG email]<br />
* Translations: (none)<br />
<br />
== Audiences ==<br />
<br />
* Teachers, trainers<br />
* Conference presenters<br />
* Web developers<br />
* Accessibility advocates<br />
* Web accessibility evaluators and testers<br />
* ([http://www.w3.org/WAI/EO/Drafts/retrofit/requ-basite.html old audience analysis])<br />
<br />
== Tweet ideas ==<br />
''(Note: short uri to doc: http://bit.ly/BADdemo, short URi to message for potential promoters: http://bit.ly/BADshare )''<br />
* BAD to Good: Demo shows example website with #accessibility barriers and fixes http://bit.ly/BADshare Useful for presentations. #a11y<br />
* BAD to Good: WAI demo website with #accessibility barriers and fixes http://bit.ly/BADdemo Useful for presentations. #a11y<br />
* Need to show web devs how to fix #accessibility issues without sacrificing visual style? http://bit.ly/BADdemo #a11y <br />
* Read about WAI's Before and After Demo (BAD) and use it to show #accessibility at work http://bit.ly/aboutBAD #a11y<br />
* Need practical examples of #accessibility coding techniques? WAI made Before and After Demo for you. http://bit.ly/BADdemo #a11y<br />
* Cool new site, easy to use and share to show accessible design techniques applied. @w3c_wai resource. http://bit.ly/BADdemo #a11y<br />
* Great resource for accidental accessibility team leads. Before and After Demo from @w3c_wai http://bit.ly/aboutBAD #a11y<br />
<br />
== Draft blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Audience: Teachers, trainers ===<br />
'''Use BAD to Train Developers to Create Great Pages for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Teaching web development professionals about web accessibility almost always includes the need to clear up misunderstandings about the impact of accessible design on visual style and presentation. The Web Accessibility Initiative (WAI) at the W3C has just updated a set of demonstration web pages to help trainers do just that.<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web and application developers believe that accessible web sites must be dull and lack interactivity. The [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)] is a free and useful teaching tool that gives trainers and internal accessibility advocates a set of practical examples, implemented within a set of related pages. Trainers can use BAD to demonstrate that pages can be fully accessible without changing the cool visual features that developers love.<br />
<br />
Dr. Wayne Dick is the former Chair of the Computer Science and Engineering Department at the University of California at Long Beach. <br />
<br />
“BAD is great for these reasons,” says Dr Dick. “And here is support for that…..”<br />
<br />
===Audience: Public speakers===<br />
'''BAD Shows Audiences How to Do Good for Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Web accessibility means designing pages and applications so that they can be used by everyone, including people with disabilities, some of whom use assistive technologies to browse the web. Accessibility is required by federal law in many instances and courts are broadening their interpretation of how the legal requirements are implemented. Many know that web accessibility is an increasingly important issue, but are not sure what to do.<br />
<br />
It is not uncommon for individuals who recognize and speak up about the need for accessibility within an organization to find that they have become experts by default. For those in this situation and who are invited to speak to groups about web accessibility, an updated tool from the W3C’s [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) can help.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. Sharp, new, and fun to use, BAD is designed to serve a variety of purposes. In addition to raising general awareness of web accessibility issues, BAD is a highly effective way to show how [http://w3.org/WAI/into/WCAG/ Web Content Accessibility Guidelines] (WCAG 2) can be applied without sacrificing visual appeal or interactivity.<br />
<br />
BAD shows common accessibility barriers using practical examples. The demonstration consists of an inaccessible Web site, an accessible version of the same site, as well as a report about the demonstrated barriers. The demonstration does not attempt to cover every checkpoint of the Web Content Accessibility Guidelines (WCAG) nor to provide an exhaustive list of examples but to demonstrate some key aspects of Web accessibility appropriate for short, focused presentations.<br />
<br />
Demonstrating practical examples during presentation is usually very effective. The description pages provide an overview of the accessibility barriers and features that are shown in the Demo. Together with the inaccessible and accessible Demo pages, concrete before and after examples can be explained during presentations. <br />
<br />
Presenters are encouraged to use the demo live or to download the pages with the understanding that some pages will not have full interactivity without connection to a server. WAI is interested to hear if BAD is good for you. Please use the demo and then let WAI know about your experience. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
...insert contact info.<br />
<br />
=== Audience: Web developers ===<br />
<br />
'''Use BAD for Great Examples of Web Accessibility''' (initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Here is a resource tip for the next time you need to meet an accessibility requirement. You had that accessibility training a few weeks age but you’re not exactly certain what they said about radio buttons and don’t really have time to sort through the guidelines and techniques of the [http://www.w3.org/WAI/intro/wcag/ Web Content Accessibility Guidelines] (WCAG 2). When you need a good example, think BAD. <br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is an updated set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the [http://www.w3.org/WAI Web Accessibility Initiative] (WAI) at the W3C and it is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images. <br />
<br />
With BAD you can look at the inaccessible version of any of the four pages – Home, News, Tickets, and Survey; you can read a report about the accessibility barriers that were found; you can look at the same pages with accessibility fixes in place; you can look at the code; and you can download and use the page template, adapting it for your own needs. <br />
<br />
While the general information can be very helpful, you may want to hone in on the one problem you need to solve - that one tricky item where you just want to know what the accessibility problem is and how can it be fixed? BAD pages come in two versions. The Before page is the inaccessible version. The After page is the same page, same function, same visual design but with accessibility built in. You can look right at the code to see how the problem was solved. <br />
<br />
Use BAD for good accessibility outcomes. See more information about [http://www.w3.org/WAI/demos/bad/ BAD].<br />
{shawn: I'm not sure which links you want in this paragraph and the next. anyway, I updated them from the outdated /2005/ links :-}<br />
<br />
So the next time you need a good example of accessibility in action, think BAD. More about [http://www.w3.org/WAI/demos/bad/#howto how to use the demo] is found on the WAI site.<br />
<br />
=== Audience: Internal Accessibility Advocates and Testers ===<br />
<br />
'''W3C Releases BAD web accessibility demo for advocates and testers'''(initial co-editors Sharron Rush and Wayne Dick)<br />
<br />
Designing for web accessibility means creating web pages and applications that can be used by all - including people with disabilities. Many web development teams delegate accessibility responsibility to a few or even to just to one team member. The [http://w3.org/WAI/ Web Accessibility Initiative] (WAI) at the W3C has just updated a tool to help make that job easier.<br />
<br />
The [http://www.w3.org/WAI/demos/bad/ Before and After Demo] (BAD) is a set of related web pages that provide fully integrated examples of accessibility at work. Accessibility leads who are seeking ways to test, report, and convince fellow team members of practical accessibility techniques will find this a useful demonstration tool for many common accessibility errors. BAD puts accessibility in the context of a set of related web pages. <br />
<br />
BAD provides an inaccessible version of each of the four pages – Home, News, Tickets, and Survey. Each one has a corresponding report of accessibility barriers contained in the page. An accessible version of the same pages with accessibility fixes in place can be viewed to demonstrate that the visual style remains largely unchanged.<br />
<br />
In many instances, the real issues for people with disabilities are not clear to developers or managers. Browsing through the inaccessible Demo pages using different browser configurations or assistive technologies (such as screen readers and magnifiers) helps highlight these issues. {shawn: need to broaden to cover other disabilities & interaction, e.g., keyboard only} The accessible Demo pages can be browsed in the same manner to show the difference.<br />
<br />
A well written evaluation report is key in the process of retrofitting websites for accessibility. It communicates the problems to managers and the developers who need to decide which solutions to implement. The evaluation reports of the Demo serve as a sample format for evaluators.<br />
<br />
BAD is designed to serve a variety of purposes. Not only is BAD useful in raising general awareness of web accessibility issues, it also provides practical examples for developers and demonstrates that an accessible site can be just as visually appealing and interactive as the one with access barriers. If the tool is helpful, please consider sharing your experience with the creators at WAI. Send your comments to wai-eo-editors@w3.org (a publicly archived list) or wai@w3.org (a WAI staff-only list).<br />
<br />
…insert contact info<br />
<br />
===Audience: Web Managers===<br />
'''Use BAD, a Good Example of Accessibility at work''' (initial editor Cliff Tillick) <br />
<br />
<del>Have you ever considered what it would cost to make your website accessible? If so, what has worried you most:</del><br />
<del>- The time required?</del><br />
<del>- The design features you might lose?</del><br />
<del>- The impact on usability?</del><br />
{Shawn: not comfortable with intro about cost, and especially the possible mis-read that accessibility will cause you to lose design features.}<br />
<br />
Wouldn’t it be nice if you could see an example of the difference an accessible website makes?<br />
Well now you can. But we should warn you, it’s BAD—as in “Before and After Demonstration.”<br />
Published through the W3C’s Web Accessibility Initiative, BAD is a mockup of a website that contains a number of common barriers to accessibility and, linked to it, a website that has the same information but without those barriers.<br />
<br />
The differences are hard to recognize—unless you use a screen reader or screen magnification to get information from these pages. {shawn: or keyboard only or... need to be inclusive!} Then the differences are obvious. {shawn: Otherwise, you might not notice them at all. that's because most of the differences are "under the covers" -that is, in the underlying code and they don't impact the visual design at all. ...}<br />
<br />
=== Notes on posts, blurbs, etc. ===<br />
<br />
* Brainstorming -- possible theme -- When something bad becomes good. Making BAD good. (Jennifer, January 8, 2012)<br />
<br />
* What did site code look like before and how is it now fixed? How BAD can improve awareness about Web accessibility. (Sylvie, January 10, 2012)<br />
<br />
* For UN Newsletter (submitted on Jan. 23): Revised version:<br/>'''Web Accessibility''':<br/>How to make a BAD site GREATLY accessible to people with disabilities, older users, and others: The Before and After Demo (BAD) is a newly released set of related web pages that provide fully integrated examples of accessibility at work. The mini website is a project of the Web Accessibility Initiative (WAI) at the W3C and is released for public use. A useful teaching tool, BAD is also great for those times when you want a quick memory boost about how to create an accessible data table for example, or how to when to use (and NOT to use) background images.<br />
<br />
== WAI IG e-mail ==<br />
[http://lists.w3.org/Archives/Public/w3c-wai-ig/2012JanMar/0024.html archived final e-mail]<br />
<br />
== 2012 blogs, newsletters, references, etc. ==<br />
<br />
* [http://lists.d.umn.edu/pipermail/webdev/2012q1/000629.html Web Design Update newsletter] (Laura Carlson) lead article in newsletter that has 2,500+ readers<br />
* United Nations Enable Newsletter - [http://www.un.org/disabilities/documents/newsletter/january2012.doc January 2012, MS-Word]<br />
* Notable tweets & retweets:<br />
** [https://twitter.com/#!/cinteractionlab/status/167242173098627072 @cityuni_hcid] could be useful for #inm313 students - BaD Demo for accessibility at bit.ly/BADdemo #w3c #wai #a11y (via @AdobeAccess)<br />
** [https://twitter.com/#!/dboudreau/status/167134289912283136 @dboudreau] and reply from [https://twitter.com/#!/Nethermind/status/167257448959324161 @Nethermind (Elle Waters)]: I used this last week for new dev teams to understand real examples of #accessibility impacts - thanks you!<br />
** [https://twitter.com/#!/w3c_wai/status/164452260707975168 w3c_wai] BAD to Good: Demo shows example website with #accessibility barriers and fixes bit.ly/BADshare Useful for presentations. #a11y ''-- has 50+ Retweets & 31 Favorites''<br />
<br />
== 2012 EOWG Recent Contacts ==<br />
<br />
* '''Done:'''<br />
** UNDESA - Vicki (January 23, 2012)<br />
** ITU - Vicki (February 2, 2012)<br />
** WMO - Vicki (February 2, 2012)<br />
** ILO - Vicki (February 2, 2012)<br />
** WHO - Vicki (February 2, 2012)<br />
** OHCR - Vicki (February 2, 2012)<br />
** OHCA - Vicki (February 2, 2012)<br />
** UN NY (2)Vicki, positive feedback (February 2, 2012)<br />
** ITC - Vicki (February 2, 2012)<br />
** UNCTAD - Vicki (February 2, 2012)<br />
** UPU - Vicki (February 2, 2012)<br />
** EFSA - Vicki (February 2, 2012)<br />
** UNICEF - Vicki (February 2, 2012)<br />
** IAEA (2) - Vicki (February 2, 2012)<br />
** WTO - Vicki (February 2, 2012)<br />
** ICJ - Vicki (February 2, 2012)<br />
** WIPO (several)- Vicki, positive feedback (February 2, 2012)<br />
** Laura Carlson - Denis [Feb 8th]<br />
** Russ Weakly - Denis [Feb 8th]<br />
** Dennis Lembree - Denis [Feb 8th]<br />
** Léonie Watson - Denis [Feb 8th]<br />
** John Foliot - Denis [Feb 8th]<br />
** Jared W. Smith - Denis [Feb 8th]<br />
** Jason Kiss - Denis [Feb 8th]<br />
** David MacDonald - Denis [Feb 8th]<br />
** Kathy Wahlbin - Denis [Feb 8th]<br />
** Olivier Nourry - Denis [Feb 8th]<br />
** Glenda Sims - Denis [Feb 8th]<br />
** Karen Mardahl - Denis [Feb 8th]<br />
** Roger Hudson - Denis [Feb 8th]<br />
** Jennison Asuncion - Denis [Feb 8th]<br />
** Elle Waters - Denis [Feb 8th]<br />
** Karl Groves - Denis [Feb 8th]<br />
** Steve Buell - Denis [Feb 8th]<br />
** Matt May - Denis [Feb 8th]<br />
** Wendy Chisholm - Denis [Feb 8th]<br />
** Henny Swan - Denis [Feb 8th]<br />
** Molly Holzschlag - Denis [Feb 8th]<br />
** Andrew Kirkpatrick - Denis [Feb 8th]<br />
** Steve Faulkner - Denis [Feb 8th]<br />
** Mike Paciello - Denis [Feb 8th]<br />
** Bruce Lawson - Denis [Feb 8th]<br />
** Gez Lemon - Denis [Feb 8th]<br />
** Mike Gifford - Denis [Feb 8th]<br />
** WANAU list (Australian Universities) - Andrew [Feb 9th]<br />
* To Do:<br />
** Derek Featherstone - Sharron<br />
** Access U presenters - Sharron (both CSUN and in Austin? -- Jennifer)<br />
** AccessU at CSUN "How We Use the Web" Demo," Feb. 27 (Jennifer)<br />
** UCal State list - Wayne<br />
** Web manager, developer lists - Jason<br />
** European design for all network (EDeAN)<br />
** RNIB - Vicki<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=149Promoting Make Presentations Accessible2012-01-09T06:31:11Z<p>Jsutton2: /* Presenters & bloggers that presenters read */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
=== Resources & Pointers ===<br />
<br />
* Doc: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight June 2010]<br />
* [http://www.w3.org/QA/2010/06/make_your_presentations_access.html WAI blog June 2010]<br />
* Tweet June 2010<br />
* Translations: (none yet)<br />
<br />
=== Audience & Messages ===<br />
<br />
# Conference organizers - @@ message...<br />
# Presenters - @@ message...<br />
(more in [http://www.w3.org/WAI/EO/changelogs/cl-training#accessibleAnalsysi analysis doc])<br />
<br />
=== Draft posts/blurbs ===<br />
...<br />
<br />
=== Tweet ideas ===<br />
...<br />
<br />
=== Draft e-mails ===<br />
==== To conference organizers: ====<br />
* add a link to this document on your website<br />
* include in material provided to presenters<br />
==== To presenters: ====<br />
...<br />
<br />
=== Contacts ===<br />
<br />
==== Conferences ====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* ATIA?<br />
* CSUN<br />
* AccessU conferences held by Knowbility<br />
* ICCHP<br />
* SXSW<br />
* Accessibility barcamps/unconferences<br />
* An Event Apart<br />
* ...<br />
<br />
==== Presenters & bloggers that presenters read====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
==== Misc ====<br />
* LinkedIn groups (in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups {@@ action: Andrew list which ones @@}, Andrew added pointers to the WAI page (Dec 2011)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=148Promoting Make Presentations Accessible2012-01-09T06:29:20Z<p>Jsutton2: /* Presenters & blogers that presenters read */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
=== Resources & Pointers ===<br />
<br />
* Doc: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight June 2010]<br />
* [http://www.w3.org/QA/2010/06/make_your_presentations_access.html WAI blog June 2010]<br />
* Tweet June 2010<br />
* Translations: (none yet)<br />
<br />
=== Audience & Messages ===<br />
<br />
# Conference organizers - @@ message...<br />
# Presenters - @@ message...<br />
(more in [http://www.w3.org/WAI/EO/changelogs/cl-training#accessibleAnalsysi analysis doc])<br />
<br />
=== Draft posts/blurbs ===<br />
...<br />
<br />
=== Tweet ideas ===<br />
...<br />
<br />
=== Draft e-mails ===<br />
==== To conference organizers: ====<br />
* add a link to this document on your website<br />
* include in material provided to presenters<br />
==== To presenters: ====<br />
...<br />
<br />
=== Contacts ===<br />
<br />
==== Conferences ====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* ATIA?<br />
* CSUN<br />
* AccessU conferences held by Knowbility<br />
* ICCHP<br />
* SXSW<br />
* Accessibility barcamps/unconferences<br />
* An Event Apart<br />
* ...<br />
<br />
==== Presenters & bloggers that presenters read====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* [<br />
http://www.wait-till-i.com Chris Heilmann's site] -- since he attends a lot of conferences, he might be willing to promote<br />
<br />
==== Misc ====<br />
* LinkedIn groups (in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups {@@ action: Andrew list which ones @@}, Andrew added pointers to the WAI page (Dec 2011)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=147Promoting Make Presentations Accessible2012-01-09T06:25:03Z<p>Jsutton2: /* Conferences */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
=== Resources & Pointers ===<br />
<br />
* Doc: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight June 2010]<br />
* [http://www.w3.org/QA/2010/06/make_your_presentations_access.html WAI blog June 2010]<br />
* Tweet June 2010<br />
* Translations: (none yet)<br />
<br />
=== Audience & Messages ===<br />
<br />
# Conference organizers - @@ message...<br />
# Presenters - @@ message...<br />
(more in [http://www.w3.org/WAI/EO/changelogs/cl-training#accessibleAnalsysi analysis doc])<br />
<br />
=== Draft posts/blurbs ===<br />
...<br />
<br />
=== Tweet ideas ===<br />
...<br />
<br />
=== Draft e-mails ===<br />
==== To conference organizers: ====<br />
* add a link to this document on your website<br />
* include in material provided to presenters<br />
==== To presenters: ====<br />
...<br />
<br />
=== Contacts ===<br />
<br />
==== Conferences ====<br />
Conference that specifically want to target (mostly those that overlap with the primary audience of WAI work):<br />
* ATIA?<br />
* CSUN<br />
* AccessU conferences held by Knowbility<br />
* ICCHP<br />
* SXSW<br />
* Accessibility barcamps/unconferences<br />
* An Event Apart<br />
* ...<br />
<br />
==== Presenters & blogers that presenters read====<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
<br />
==== Misc ====<br />
* LinkedIn groups (in reply to pointers to [http://www-03.ibm.com/able/news/accessible_meetings.html IBM's 10 steps for making your meeting accessible] on several groups {@@ action: Andrew list which ones @@}, Andrew added pointers to the WAI page (Dec 2011)<br />
* ...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Contacts_for_promotion&diff=146Contacts for promotion2012-01-09T05:40:46Z<p>Jsutton2: /* General Web designer & developer */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
__TOC__<br />
<br />
'''Suggested format for listings:'''<br />
* What it is - contact person (who knows how to contact them). Notes on what types of material is most relevant for it/them.<br />
<br />
== General Web designer & developer ==<br />
<br />
NOTE: One contact for each document being promoted may wish to set up a few Google Alerts with relevant phrases in order to monitor and document where references to that document are being made.<br />
Lists & Misc:<br />
* [http://www.d.umn.edu/itss/training/online/webdesign/ Web Design References, UMD] - Laura Carlson. [http://www.d.umn.edu/itss/training/online/webdesign/urlform.html form to Suggest a Link]<br />
* [http://www.alistapart.com/articles/ A List Apart] (tech notes?)<br />
* [http://www.smashingmagazine.com Smashing Magazine]<br />
* [http://www.netmagazine.com Net Magazine]<br />
* [http://www.sitepoint.com/ SitePoint]<br />
* [http://radar.oreilly.com OReilly Radar]<br />
* WritersUA monthly user assistance update resource_directory@writersua.com contact: Joe W.<br />
<br />
== Web Accessibility focused ==<br />
<br />
Lists & Misc:<br />
* LinkedIn Groups - Jennison A.<br />
* [http://webaim.org/discussion/ The WebAIM Email Discussion List]<br />
<br />
Blogs:<br />
* [http://blog.knowbility.org/ Knowbility Blog, Universally Designed] - posters: Sharron, Wayne<br />
* Do It Myself Blog - Glenda Watson-Hyatt<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (has contact info: Jennifer, Shawn)<br />
* [http://dboudreau.posterous.com/ accessiWatch v0.1 (2011)] (Denis B.)<br />
* [http://www.paciellogroup.com/blog/ The Paciello Group Blog] (Tech Notes?)<br />
* [http://www.stc-access.org/ STC Accessibility Sig]<br />
* [http://www.coataccess.org Coalition of Organizations for Accessible Technology<br />
(COAT)]<br />
<br />
<br />
Newsletters:<br />
* [http://www.knowbility.org/v/newsletter/ Knowbility] - Sharron R.<br />
* [http://webaim.org/newsletter/ The WebAIM Newsletter] (Jared Smith)<br />
<br />
== Disability focused ==<br />
<br />
Organizations that have blogs, newsletters, lists, etc.:<br />
* [http://www.HumanCenteredDesign.org Institute for Human Centered Design (IHCD)] - Jennifer O. (has contact info: Shawn)<br />
* [http://www.afb.org American Foundation for the Blind] - Paul S. (has contact info: Jennifer, Shawn)<br />
* [http://www.nfb.org/nfb/access_technology_blog.asp NFB Technology Access Blog] - Mark R & Clara V (has contact info: Jennifer, Shawn)<br />
* [http://www.acb.org The American Council of the Blind] - Melanie B. (has contact info: Jennifer)<br />
* [http://www.visionaware.org Visionaware] - ?name (has contact info: Jennifer)<br />
* [http://www.lighthouse-sf.org/ San Francisco Lighthouse] - ?name (has contact info: Jennifer)<br />
* [http://www.eastersealstech.com/content.aspx?pId=682 Podcast - Assistive Technology Update] produced by [http://www.eastersealstech.com/Default.aspx Easter Seals indata Indiana Assistive Technology Act]: The publication is "AT Update" and consists of Fast-paced news, tips, and interviews for AT professionals and enthusiasts. While services are provided throughout Indiana, information seems wide-ranging. Here's the [http://www.eastersealstech.com/content.aspx?pId=87 Contact page].<br />
<br />
<br />
<br />
Blogs:<br />
* [http://www.lflegal.com LF Legal] [especially for policies and standards harmonization)<br />
<br />
Newsletters:<br />
* HeadStar [http://www.headstar.com/eablive/ E-Access Live] and [http://www.headstar.com/site/scripts/documents_info.php?categoryID=1&documentID=11 E-Access Bulletin] - Dan J. (has contact info: Jennifer, Shawn)<br />
<br />
E-mail lists:<br />
* webwatch@accessplace.net (subscribed: Jennifer)<br />
* VICUG-L@LISTSERV.ICORS.ORG 285 members (subscribed: Jennifer)<br />
<br />
Other:<br />
* ...<br />
<br />
== Miscellaneous Items That Need Closer Review/Consideration ==<br />
<br />
*See if any of these [http://www.d.umn.edu/itss/training/online/webdesign/sites.html blogs] seem worth hand-picking<br />
*See if any of these [http://www.d.umn.edu/itss/training/online/webdesign/associations.html associations] seem worth targeting<br />
<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Contact_Orgs_Inaccessible_Sites&diff=145Promoting Contact Orgs Inaccessible Sites2012-01-09T05:36:41Z<p>Jsutton2: /* Published Dec 2011 and Jan., 2012 */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/users/inaccessible.html Contacting Organizations about Inaccessible Websites] - short uri: http://bit.ly/inaccessible2<br />
<br />
* [http://twitter.com/#!/w3c_wai/status/142632565071810560 Tweet 2 Dec 2011]<br />
<br />
* Blog post: [http://www.w3.org/QA/2010/01/encourage_accessibility_make_a_difference.html Take a few minutes to encourage web accessibility. You can make a difference.] Jan 2010 - short uri: http://bit.ly/inaccessible1<br />
<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2010JanMar/0003.html WAI IG e-mail Jan 2010], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2010AprJun/0010.html WAI IG e-mail April 2010], [http://www.w3.org/WAI/highlights/archive#x20100106a WAI highlight Jan 2010]<br />
* Translations:<br />
** Spanish:<br />
*** [http://www.discapnet.es/Castellano/areastematicas/Accesibilidad/Direcciones%20interes/Paginas/Como_contactar_con_organizaciones_con_sitios_web_inaccesibles.aspx Cómo contactar con organizaciones con sitios web inaccesibles (the main doc)]<br />
*** [http://sentindoysensibilidad.blogspot.com/2011/12/em-estas-fiestas-contribuye-hacer-la.html Sentido y sensibilidad (translations of promotional posts/blurbs below)]<br />
** French coming in January 2012<br />
<br />
== Audience & Messages ==<br />
<br />
# Audience: Users - people who want to report accessibility barriers.<br>Message: use this resource to help you - make it easier and hopefully more effective<br />
# Audience: Owners - websites owners & developers.<br>Message: point users to this resource to help them give you more useful feedback about accessibility issues (e.g., [http://www.pinsentmasons.com/en/accessibility/ example under Contacting Us])<br />
* More details of [http://www.w3.org/WAI/EO/changelogs/cl-responding.html#audience audience in contacting initial analysis]<br />
<br />
== Blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Published Dec 2011 and Jan., 2012===<br />
* e-mail lists:<br />
** webwatch@accessplace.net - Jennifer, 2 Dec 2011<br />
** VICUG-L@LISTSERV.ICORS.ORG 285 members - Jennifer, 2 Dec 2011<br />
** ACCESOWEB (accesoweb@yahoogroups.com) 1.821 members - Emmanuelle, 15 Dec 2011<br />
** Discapacidadyderechoshumanos (discapacidadyderechoshumanos@gruposyahoo.com)588 members - Emmanuelle, 15 Dec 2011<br />
** Acessibilidade (acessibilidade@yahoogrupos.com.br) 584 members - Emmanuelle, 15 Dec 2011<br />
** ...<br />
<br />
* blog posts:<br />
** [http://blog.knowbility.org/2011/12/06/retailers-help-your-customers-with-disabilities-help-you/ Knowbility Blog] - Sharron 6 Dec<br />
** [http://www.nfb.org/NewsBot.asp?MODE=VIEW&ID=888&SnID=247008194 Speaking up about inaccessible Web sites] - NFB Blog post, 8 Dec <br />
** [http://webaxe.blogspot.com/2011/12/podcast-93-teaching-mistakes.html Podcast 93: Teaching Mistakes] - 7 Dec 2011<br />
** [http://sentindoysensibilidad.blogspot.com/2011/12/em-estas-fiestas-contribuye-hacer-la.html Sentido y sensibilidad (Spanish)] - Emmanuelle 15 Dec<br />
** [http://www.abc.net.au/rampup/articles/2011/12/19/3393485.htm ABC RampUp - An inaccessible website: don't just suck it up] - added a link in a comment - Andrew 19 Dec <br />
** [http://www.linkedin.com/ LinkedIn] groups are picking it up - e.g. [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=d83c6640-4bd0-4fe4-94b9-8c08aeba24b3&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] and [http://www.linkedin.com/groups/Contacting-Organizations-about-Inaccessible-Websites-163162%2ES%2E85543063?view=&gid=163162&type=member&item=85543063&trk=eml-anet_dig-b_nd-pst_ttle-cn Breaking the Barriers of Technology] - Andrew 23 Dec<br />
** [http://www.glendathegood.com/blog/?p=678 All I want for Christmas is a More Accessible Web – Be an Accessibility Elf] - added doc in Comment - Jennifer 21 Dec<br />
** [http://www.stc-access.org/2011/12/28/a-resolution-for-an-accessible-new-year/ A Resolution for an Accessible New Year?] STC AccessAbility SIG Karen Mardahl 28 Dec "This marvelous resource helps you identify who you need to contact, assists you in how to describe the problem, and strongly encourages you to follow-up as needed. Let’s give a round of applause or a waving of hands to the awesome volunteers in the Education and Outreach Working Group in the W3C’s Web Accessibility Initiative for making such a useful resource available to us."<br />
** [http://www.mardahl.dk/2011/12/30/lets-talk-and-teach-not-fight-about-accessibility/ http://www.mardahl.dk/2011/12/30/lets-talk-and-teach-not-fight-about-accessibility/ Let's Talk and Teach, Not Fight, About Accessibility] December 30, 2011 (includes link to templates)<br />
** [http://www.mediaaccess.org.au/latest_news/general/how-to-contact-organisations-about-website-accessibility How to contact organisations about website accessibility Media Access Australia] January 3, 2012 (link in blog post)<br />
** ...<br />
<br />
* newsletters:<br />
** [http://paper.li/Hear_And_There/1306429577/2011/12/02 Hear and There #Accessibility News] 2 Dec 2011<br />
** Knowbility December 2011 Newsletter - Sharron 12 Dec 2011<br />
** [http://paper.li/egyrs/1311766865/2011/12/15 Accesibilidad Hoy (Spanish)] - Emmanuelle 15 Dec<br />
** ...<br />
<br />
''(Older WAI ones are listed in [[#Resources & Pointers]] above and others are listed in [[#Previous blogs, etc.]] below.)''<br />
<br />
=== Draft posts/blurbs ===<br />
<br />
'''''[http://sentindoysensibilidad.blogspot.com/2011/12/em-estas-fiestas-contribuye-hacer-la.html Spanish translations of these posts/blurbs]'''''<br />
<br />
==== '''Audience: Users - Short''' (initial editor: Jennifer Sutton) ====<br />
<br />
[disabilities audience] During the holidays, shopping online can be frustrating for people with disabilities. Does any of this sound familiar? You have the perfect gift in mind,...<br />
<br />
[broader audience] During the holidays, shopping online can be frustrating for people with disabilities. Imagine how you’d feel if you have the perfect gift in mind,...<br />
<br />
...but then, you can't read the site easily, you can't find the item amid all of the links on the page, you aren't sure whether the item is really in your shopping cart, or you can't check out independently. It's not fun when you can't keep a gift a secret because you can't buy it without help. Complaining on Twitter or Facebook won't help much in the longrun. So, how can you raise your concerns constructively, spread good cheer while helping to make the Web more accessible, and start getting positive results? Try visiting these two pages for some tips and sample email messages. See blog<br />
http://bit.ly/inaccessible1 and document http://bit.ly/inaccessible2<br />
<br />
==== '''Audience: Users - Longer''' (initial editor: Jennifer Sutton) ====<br />
<br />
''{To newsletter editors: You are welcome to use this verbatim attributed to Jennifer Sutton. If you would like to make edits, contact Jennifer at jsuttondc@gmail.com}''<br />
<br />
When I go online during the holidays, I just want to find what I'm looking for and check out without needing any help. But sometimes, by the time I'm done, my holiday cheer is beginning to fade. Trying to use an inaccessible site to buy a gift or make a donation on behalf of a loved one can take time I simply don't have during the busy holiday season.<br />
<br />
But if I spend a little extra time to report my experiences to the organizations that run the sites I visit, I believe my efforts will make the Web a better place next year. <br />
<br />
As I make my shopping list and gather links to the sites I plan to visit, I'm adding a couple of other links to my collection, so they'll be handy. I'm also setting up an email template or two in advance to help me quickly report my shopping experiences -- both the good ones and the ones that are harder than I might wish. Why not join me and start off your New Year positively by helping to make the Web a more accessible place?<br />
<br />
Find tips about giving accessibility feedback to Web sites by visiting these two Web pages, brought to you by the World Wide Web Consortium's Web Accessibility Initiative: blog http://bit.ly/inaccessible1 and document http://bit.ly/inaccessible2.<br />
<br />
==== '''Audience: Web Managers and Developers''' (initial editor: Sharron Rush) ====<br />
<br />
If you sell goods and services online, you have an eager market of more than 750 million people throughout the world. In the United States alone, this group maintains an aggregate income that now exceeds $1 trillion and boasts $220 billion in discretionary spending power, according to Fortune Magazine. <br />
<br />
As ideal as it sounds, many online retailers fail to reach this valuable market because their web sites are not accessible to the group described - people with disabilities. This large and growing group of customers is likely to lose interest when form inputs aren't labeled, graphic elements are not described, or the next step in a purchase process shows up in a modal dialogue that can't be found by assistive technology. These and other design barriers can make online shopping miserable for potential buyers with disabilities.<br />
<br />
If your customers are frustrated, you want to know about it. The [http://www.w3.org/WAI Web Accessibility Initiative] at the W3C has a resource to help them communicate with you in a constructive and useful way. Consider posting a link on your shopping pages for customers who encounter shopping barriers.<br />
<br />
The guide is called [http://www.w3.org/WAI/users/inaccessible Contacting Organizations about Inaccessible Websites] and can help your potential customers describe specific areas of pain. Open the channels of communication to potential customers with disabilities. You may make their holidays much merrier and give yourself the gift of a new customer who is likely to return. May all your holidays be bright!<br />
<br />
==== '''Audience: UN Organizations''' (initial editor: Vicki Menezes Miller) ====<br />
<br />
Web Accessibility - Watch This Corner:<br />
Help make the Web more accessible during the holidays.<br />
The UN Convention on the Rights of Persons with Disabilities, Article 9(g) requires that web sites are accessible to all.<br />
W3C Web Accessibility Initiative provides a wealth of resources and guidance,<br />
This month: If you want to contact an organization to suggest improvements in web accessibility, go to: http://bit.ly/inaccessible2<br />
<br />
==== '''Audience: Public Institutions''' (initial editor: Wayne) ====<br />
<br />
Your service unit worked hard on the Website. You set aside budget and hired good people. Now, you offer most services online. The Web also informs people about services, classes and events offered at the institution. Directions, calendars and other key information are distributed through your on-line presence. You save your clients hours of commute time. You are proud, and should be.<br />
<br />
You may not realize it, but many people with disabilities will visit the site. This is a large and growing group, and it is likely that these visitors may miss important opportunities at your institution because of easily fixed mistakes that obstruct their access. Form inputs appear without labels; graphic elements are used without text description, or the next step in a registration process shows up in a modal dialogue that cannot be found by assistive technology. These and other design barriers can make online usage miserable or impossible for clients with disabilities. Your Website could block access to public services that are intended for everyone — even people with disabilities.<br />
<br />
If your clientele is frustrated, you want to know about it. The [http://www.w3.org/wai Web Accessibility Initiative] at the W3C has a resource to help them communicate with you in a constructive and useful way. Consider posting a link on your institutional pages for users who encounter barriers.<br />
<br />
The guide is called [http://www.w3.org/WAI/users/inaccessible Contacting Organizations about Inaccessible Websites] and can help your potential customers describe specific areas of pain. Open the channels of communication to potential customers with disabilities. You may make their holidays much merrier and give yourself the gift of a new customer who is likely to return. May your all your holidays be bright!<br />
<br />
==== '''Audience: Job Seekers with Disabilities''' (initial editor: Sharron Rush) ====<br />
<br />
Year-end shopping is an incentive for many retailers to add staff and therefore often a good time to find work. As more retailers expect applicants to submit inquiries online, the accessibility of the application process becomes critically important to job seekers with disability. Optimism can quickly turn to discouragement when form inputs aren't labeled, graphic elements are not described, or the next step in the application process shows up in a modal dialogue that can't be found by assistive technology. These and other design barriers can make the online job search miserable for potential buyers with disabilities. An inaccessible web application process can harm the business as well. <br />
<br />
Employees with disabilities are generally a great asset to a company, according to studies by <br />
the Office of Disability Employment Policy at the US Department of Labor. Businesses need to know if their employment application process is excluding valuable human resources. As employees, people with disabilities add to the range of viewpoints businesses need to succeed, offering fresh ideas on how to solve problems, accomplish tasks and implement strategies. Hiring people with disabilities can positively impact a business's bottom line. Recruiting and retaining workers with disabilities is one strategy to counter the effects of the aging and shrinking workforce. This untapped labor pool can offer a source of skilled employees and can contribute to increasing retention and reducing turnover. In addition, tax incentives and technical assistance can assist with accommodations, which are often relatively easy and inexpensive to implement. <br />
<br />
If you encounter barriers to applying for jobs online, you can provide a valuable service by letting the employer know about it. Find tips about giving accessibility feedback to Web sites by visiting these two Web pages, brought to you by the World Wide Web Consortium's Web Accessibility Initiative: blog http://bit.ly/inaccessible1 and document http://bit.ly/inaccessible2.<br />
<br />
=== Tweet ideas ===<br />
<br />
# If an inaccessible site frustrates you during the holidays, here's how you can take action: http://bit.ly/inaccessible2<br />
# Tired of yelling at your computer about inaccessible websites? A blog post describes what you can do: http://bit.ly/inaccessible1<br />
# Have you used sample emails to contact an organization about its inaccessible site? Start here to check them out: http://bit.ly/inaccessible2<br />
# Help make the Web more accessible during the holidays. Contact an organization to suggest improvements: http://bit.ly/inaccessible2<br />
# Finding a website inaccessible? Tell them! Tips & sample emails - blog http://bit.ly/inaccessible1 & doc http://bit.ly/inaccessible2 #a11y {[http://twitter.com/#!/w3c_wai/status/142632565071810560 WAI tweeted 2 Dec 2011]}<br />
<br />
== Previous blogs, references, etc. ==<br />
<br />
* BS8878<br />
* '''Use this to contact us''' (e.g., "For advice on what information to include when you contact us, we recommend that you read "Contacting Organizations about Inaccessible Websites"):<br />
** [http://www.trinityhouse.co.uk/th/about/accessibility-statement.html trinityhouse.co.uk]<br />
** [http://www.my-farm.org.uk/accessibility-policy my-farm.org.uk]<br />
** [http://aseanidpp.org/node/32 aseanidpp.org]<br />
** [http://www.access8878.co.uk/accessibility-statement.aspx access8878.co.uk]<br />
** [http://www.prostate-cancer.org.uk/accessibility prostate-cancer.org.uk]<br />
** [http://www.pinsentmasons.com/en/accessibility/ pinsentmasons.com]<br />
** [http://www.chestertonhumberts.com/accesibility-statement/ chestertonhumberts.com]<br />
** [http://www.thecrownestate.co.uk/accessibility/?site-quicknav-select=/about-us/faqs/ thecrownestate.co.uk]<br />
** [http://www.somewhereto.com/havingtroubleviewingthispage somewhereto.com]<br />
**...<br />
* blogs, lists, etc.: [http://www.karlgroves.com/2011/08/07/users-must-become-their-own-advocates/ Users Must Become Their Own Advocates, Aug 2011], [http://dboudreau.posterous.com/contacting-organizations-about-inaccessible-w accessiWatch, May 2011], [http://webaim.org/discussion/mail_thread?thread=4677 WebAIM email list, April 2011], [http://answerpot.com/showthread.php?461180-Resource - Contacting Organizations about Inaccessible Websites answerpot, Nov 2010], [http://journal.brokenclay.org/wp_archives/2010/05/03/contacting-organizations-about-inaccessible-websites/ brokenclay.org/journal May 2010], [http://www.sitepoint.com/how-to-tell-organizations-their-website-is-inaccessible/ sitepoint, Feb 2010], [http://www.egov.vic.gov.au/website-practice/accessibility/accessibility-online-and-web/contacting-organizations-about-inaccessible-websites.html eGovernment Resource Centre, Feb 2010], [http://list.universaldesign.ie/pipermail/ceud-ict/2010/002118.html [CEUD-ICT], Jan 2010], [http://evolt.org/node/62403 e-volt, Jan 2010] &amp; [http://blog.adrianroselli.com/2010/01/w3c-contacting-organizations-about.html Adrian Roselli, Jan 2010], [http://www.456bereastreet.com/archive/201001/telling_organisations_that_their_websites_are_inaccessible/ 456 Berea Street, Jan 2010], [http://www.cmswire.com/cms/web-content/w3c-provides-guidance-for-brow-beating-inaccessible-websites-006389.php CMS wire, Jan 2010] "W3C Provides Guidance for Brow Beating Inaccessible Websites" ...<br />
<br />
== EOWG Contacts Dec 2011 ==<br />
<br />
...suggesting an organization do "a blog post that best reflects the organization's position in this matter." (Jennifer)<br />
<br />
'''''See also''' the [[#Published Dec 2011]] list above''<br />
* HeadStar [http://www.headstar.com/eablive/ E-Access Live] and [http://www.headstar.com/site/scripts/documents_info.php?categoryID=1&documentID=11 E-Access Bulletin] - Dan J. (Jennifer, 2 Dec 2011)<br />
* [http://www.afb.org American Foundation for the Blind]- suggested either [http://www.afb.org/blog a blog post] or an article in [http://www.afb.org/accessworld AccessWorld] - Paul S. (Jennifer, 2 Dec 2011)<br />
* [http://www.nfb.org/nfb/access_technology_blog.asp NFB Technology Access Blog] - Mark R & Clara V (Jennifer, 2 Dec 2011)<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (Jennifer, 2 Dec 2011)<br />
* Blog: Do It Myself Blog - Glenda Watson-Hyatt (Char, 6 Dec 2011)<br />
* LinkedIn Groups - Jennison A. (Jennifer, 7 Dec 2011)<br />
* [http://www.visionaware.org Visionaware] - requested a blog post (Jennifer, 2 Dec 2011, via Twitter)<br />
* [http://www.lighthouse-sf.org/ San Francisco Lighthouse] - requested a blog post (Jennifer, 2 Dec 2011, via Twitter)<br />
* [http://www.acb.org The American Council of the Blind] (Jennifer, 7 Dec 2011, via Twitter)<br />
* Jonathan Hassell (Ian, 7 Dec 2011, via email)<br />
* [http://www.atechnews.com/ ATechNews] - John M. Williams (Shawn, 10 Dec 2011)<br />
* [http://www.HumanCenteredDesign.org Institute for Human Centered Design (IHCD)] - Jennifer O. (Shawn, 13 Dec 2011)<br />
* [http://www.mediaaccess.org.au/ Media Access Australia (MAA)] - Sarah P. (Andrew, 16 Dec 2011)<br />
* Knowbility list of 1926 organizations providing disability services, especially employment services. Sent the blurb targeting Job-seekers with disabilities to some of the list and the online shopping blurb to others. (Sharron, 16 Dec 2011) <br />
<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Contact_Orgs_Inaccessible_Sites&diff=144Promoting Contact Orgs Inaccessible Sites2012-01-09T05:17:51Z<p>Jsutton2: /* Published Dec 2011 */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/users/inaccessible.html Contacting Organizations about Inaccessible Websites] - short uri: http://bit.ly/inaccessible2<br />
<br />
* [http://twitter.com/#!/w3c_wai/status/142632565071810560 Tweet 2 Dec 2011]<br />
<br />
* Blog post: [http://www.w3.org/QA/2010/01/encourage_accessibility_make_a_difference.html Take a few minutes to encourage web accessibility. You can make a difference.] Jan 2010 - short uri: http://bit.ly/inaccessible1<br />
<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2010JanMar/0003.html WAI IG e-mail Jan 2010], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2010AprJun/0010.html WAI IG e-mail April 2010], [http://www.w3.org/WAI/highlights/archive#x20100106a WAI highlight Jan 2010]<br />
* Translations:<br />
** Spanish:<br />
*** [http://www.discapnet.es/Castellano/areastematicas/Accesibilidad/Direcciones%20interes/Paginas/Como_contactar_con_organizaciones_con_sitios_web_inaccesibles.aspx Cómo contactar con organizaciones con sitios web inaccesibles (the main doc)]<br />
*** [http://sentindoysensibilidad.blogspot.com/2011/12/em-estas-fiestas-contribuye-hacer-la.html Sentido y sensibilidad (translations of promotional posts/blurbs below)]<br />
** French coming in January 2012<br />
<br />
== Audience & Messages ==<br />
<br />
# Audience: Users - people who want to report accessibility barriers.<br>Message: use this resource to help you - make it easier and hopefully more effective<br />
# Audience: Owners - websites owners & developers.<br>Message: point users to this resource to help them give you more useful feedback about accessibility issues (e.g., [http://www.pinsentmasons.com/en/accessibility/ example under Contacting Us])<br />
* More details of [http://www.w3.org/WAI/EO/changelogs/cl-responding.html#audience audience in contacting initial analysis]<br />
<br />
== Blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Published Dec 2011 and Jan., 2012===<br />
* e-mail lists:<br />
** webwatch@accessplace.net - Jennifer, 2 Dec 2011<br />
** VICUG-L@LISTSERV.ICORS.ORG 285 members - Jennifer, 2 Dec 2011<br />
** ACCESOWEB (accesoweb@yahoogroups.com) 1.821 members - Emmanuelle, 15 Dec 2011<br />
** Discapacidadyderechoshumanos (discapacidadyderechoshumanos@gruposyahoo.com)588 members - Emmanuelle, 15 Dec 2011<br />
** Acessibilidade (acessibilidade@yahoogrupos.com.br) 584 members - Emmanuelle, 15 Dec 2011<br />
** ...<br />
<br />
* blog posts:<br />
** [http://blog.knowbility.org/2011/12/06/retailers-help-your-customers-with-disabilities-help-you/ Knowbility Blog] - Sharron 6 Dec<br />
** [http://www.nfb.org/NewsBot.asp?MODE=VIEW&ID=888&SnID=247008194 Speaking up about inaccessible Web sites] - NFB Blog post, 8 Dec <br />
** [http://webaxe.blogspot.com/2011/12/podcast-93-teaching-mistakes.html Podcast 93: Teaching Mistakes] - 7 Dec 2011<br />
** [http://sentindoysensibilidad.blogspot.com/2011/12/em-estas-fiestas-contribuye-hacer-la.html Sentido y sensibilidad (Spanish)] - Emmanuelle 15 Dec<br />
** [http://www.abc.net.au/rampup/articles/2011/12/19/3393485.htm ABC RampUp - An inaccessible website: don't just suck it up] - added a link in a comment - Andrew 19 Dec <br />
** [http://www.linkedin.com/ LinkedIn] groups are picking it up - e.g. [http://www.linkedin.com/groupItem?view=&gid=41800&type=member&item=85543067&qid=d83c6640-4bd0-4fe4-94b9-8c08aeba24b3&trk=group_most_popular-0-b-cmr&goback=%2Egmp_41800 Web Accessibility] and [http://www.linkedin.com/groups/Contacting-Organizations-about-Inaccessible-Websites-163162%2ES%2E85543063?view=&gid=163162&type=member&item=85543063&trk=eml-anet_dig-b_nd-pst_ttle-cn Breaking the Barriers of Technology] - Andrew 23 Dec<br />
** [http://www.glendathegood.com/blog/?p=678 All I want for Christmas is a More Accessible Web – Be an Accessibility Elf] - added doc in Comment - Jennifer 21 Dec<br />
** [http://www.stc-access.org/2011/12/28/a-resolution-for-an-accessible-new-year/ A Resolution for an Accessible New Year?] STC AccessAbility SIG Karen Mardahl 28 Dec "This marvelous resource helps you identify who you need to contact, assists you in how to describe the problem, and strongly encourages you to follow-up as needed. Let’s give a round of applause or a waving of hands to the awesome volunteers in the Education and Outreach Working Group in the W3C’s Web Accessibility Initiative for making such a useful resource available to us."<br />
** [http://www.mardahl.dk/2011/12/30/lets-talk-and-teach-not-fight-about-accessibility/ http://www.mardahl.dk/2011/12/30/lets-talk-and-teach-not-fight-about-accessibility/?utm_campaign=twitter&utm_medium=twitter&utm_source=twitter] December 30, 2011 (includes link to templates)<br />
** [http://www.mediaaccess.org.au/latest_news/general/how-to-contact-organisations-about-website-accessibility How to contact organisations about website accessibility Media Access Australia] January 3, 2012 (link in blog post)<br />
** ...<br />
<br />
* newsletters:<br />
** [http://paper.li/Hear_And_There/1306429577/2011/12/02 Hear and There #Accessibility News] 2 Dec 2011<br />
** Knowbility December 2011 Newsletter - Sharron 12 Dec 2011<br />
** [http://paper.li/egyrs/1311766865/2011/12/15 Accesibilidad Hoy (Spanish)] - Emmanuelle 15 Dec<br />
** ...<br />
<br />
''(Older WAI ones are listed in [[#Resources & Pointers]] above and others are listed in [[#Previous blogs, etc.]] below.)''<br />
<br />
=== Draft posts/blurbs ===<br />
<br />
'''''[http://sentindoysensibilidad.blogspot.com/2011/12/em-estas-fiestas-contribuye-hacer-la.html Spanish translations of these posts/blurbs]'''''<br />
<br />
==== '''Audience: Users - Short''' (initial editor: Jennifer Sutton) ====<br />
<br />
[disabilities audience] During the holidays, shopping online can be frustrating for people with disabilities. Does any of this sound familiar? You have the perfect gift in mind,...<br />
<br />
[broader audience] During the holidays, shopping online can be frustrating for people with disabilities. Imagine how you’d feel if you have the perfect gift in mind,...<br />
<br />
...but then, you can't read the site easily, you can't find the item amid all of the links on the page, you aren't sure whether the item is really in your shopping cart, or you can't check out independently. It's not fun when you can't keep a gift a secret because you can't buy it without help. Complaining on Twitter or Facebook won't help much in the longrun. So, how can you raise your concerns constructively, spread good cheer while helping to make the Web more accessible, and start getting positive results? Try visiting these two pages for some tips and sample email messages. See blog<br />
http://bit.ly/inaccessible1 and document http://bit.ly/inaccessible2<br />
<br />
==== '''Audience: Users - Longer''' (initial editor: Jennifer Sutton) ====<br />
<br />
''{To newsletter editors: You are welcome to use this verbatim attributed to Jennifer Sutton. If you would like to make edits, contact Jennifer at jsuttondc@gmail.com}''<br />
<br />
When I go online during the holidays, I just want to find what I'm looking for and check out without needing any help. But sometimes, by the time I'm done, my holiday cheer is beginning to fade. Trying to use an inaccessible site to buy a gift or make a donation on behalf of a loved one can take time I simply don't have during the busy holiday season.<br />
<br />
But if I spend a little extra time to report my experiences to the organizations that run the sites I visit, I believe my efforts will make the Web a better place next year. <br />
<br />
As I make my shopping list and gather links to the sites I plan to visit, I'm adding a couple of other links to my collection, so they'll be handy. I'm also setting up an email template or two in advance to help me quickly report my shopping experiences -- both the good ones and the ones that are harder than I might wish. Why not join me and start off your New Year positively by helping to make the Web a more accessible place?<br />
<br />
Find tips about giving accessibility feedback to Web sites by visiting these two Web pages, brought to you by the World Wide Web Consortium's Web Accessibility Initiative: blog http://bit.ly/inaccessible1 and document http://bit.ly/inaccessible2.<br />
<br />
==== '''Audience: Web Managers and Developers''' (initial editor: Sharron Rush) ====<br />
<br />
If you sell goods and services online, you have an eager market of more than 750 million people throughout the world. In the United States alone, this group maintains an aggregate income that now exceeds $1 trillion and boasts $220 billion in discretionary spending power, according to Fortune Magazine. <br />
<br />
As ideal as it sounds, many online retailers fail to reach this valuable market because their web sites are not accessible to the group described - people with disabilities. This large and growing group of customers is likely to lose interest when form inputs aren't labeled, graphic elements are not described, or the next step in a purchase process shows up in a modal dialogue that can't be found by assistive technology. These and other design barriers can make online shopping miserable for potential buyers with disabilities.<br />
<br />
If your customers are frustrated, you want to know about it. The [http://www.w3.org/WAI Web Accessibility Initiative] at the W3C has a resource to help them communicate with you in a constructive and useful way. Consider posting a link on your shopping pages for customers who encounter shopping barriers.<br />
<br />
The guide is called [http://www.w3.org/WAI/users/inaccessible Contacting Organizations about Inaccessible Websites] and can help your potential customers describe specific areas of pain. Open the channels of communication to potential customers with disabilities. You may make their holidays much merrier and give yourself the gift of a new customer who is likely to return. May all your holidays be bright!<br />
<br />
==== '''Audience: UN Organizations''' (initial editor: Vicki Menezes Miller) ====<br />
<br />
Web Accessibility - Watch This Corner:<br />
Help make the Web more accessible during the holidays.<br />
The UN Convention on the Rights of Persons with Disabilities, Article 9(g) requires that web sites are accessible to all.<br />
W3C Web Accessibility Initiative provides a wealth of resources and guidance,<br />
This month: If you want to contact an organization to suggest improvements in web accessibility, go to: http://bit.ly/inaccessible2<br />
<br />
==== '''Audience: Public Institutions''' (initial editor: Wayne) ====<br />
<br />
Your service unit worked hard on the Website. You set aside budget and hired good people. Now, you offer most services online. The Web also informs people about services, classes and events offered at the institution. Directions, calendars and other key information are distributed through your on-line presence. You save your clients hours of commute time. You are proud, and should be.<br />
<br />
You may not realize it, but many people with disabilities will visit the site. This is a large and growing group, and it is likely that these visitors may miss important opportunities at your institution because of easily fixed mistakes that obstruct their access. Form inputs appear without labels; graphic elements are used without text description, or the next step in a registration process shows up in a modal dialogue that cannot be found by assistive technology. These and other design barriers can make online usage miserable or impossible for clients with disabilities. Your Website could block access to public services that are intended for everyone — even people with disabilities.<br />
<br />
If your clientele is frustrated, you want to know about it. The [http://www.w3.org/wai Web Accessibility Initiative] at the W3C has a resource to help them communicate with you in a constructive and useful way. Consider posting a link on your institutional pages for users who encounter barriers.<br />
<br />
The guide is called [http://www.w3.org/WAI/users/inaccessible Contacting Organizations about Inaccessible Websites] and can help your potential customers describe specific areas of pain. Open the channels of communication to potential customers with disabilities. You may make their holidays much merrier and give yourself the gift of a new customer who is likely to return. May your all your holidays be bright!<br />
<br />
==== '''Audience: Job Seekers with Disabilities''' (initial editor: Sharron Rush) ====<br />
<br />
Year-end shopping is an incentive for many retailers to add staff and therefore often a good time to find work. As more retailers expect applicants to submit inquiries online, the accessibility of the application process becomes critically important to job seekers with disability. Optimism can quickly turn to discouragement when form inputs aren't labeled, graphic elements are not described, or the next step in the application process shows up in a modal dialogue that can't be found by assistive technology. These and other design barriers can make the online job search miserable for potential buyers with disabilities. An inaccessible web application process can harm the business as well. <br />
<br />
Employees with disabilities are generally a great asset to a company, according to studies by <br />
the Office of Disability Employment Policy at the US Department of Labor. Businesses need to know if their employment application process is excluding valuable human resources. As employees, people with disabilities add to the range of viewpoints businesses need to succeed, offering fresh ideas on how to solve problems, accomplish tasks and implement strategies. Hiring people with disabilities can positively impact a business's bottom line. Recruiting and retaining workers with disabilities is one strategy to counter the effects of the aging and shrinking workforce. This untapped labor pool can offer a source of skilled employees and can contribute to increasing retention and reducing turnover. In addition, tax incentives and technical assistance can assist with accommodations, which are often relatively easy and inexpensive to implement. <br />
<br />
If you encounter barriers to applying for jobs online, you can provide a valuable service by letting the employer know about it. Find tips about giving accessibility feedback to Web sites by visiting these two Web pages, brought to you by the World Wide Web Consortium's Web Accessibility Initiative: blog http://bit.ly/inaccessible1 and document http://bit.ly/inaccessible2.<br />
<br />
=== Tweet ideas ===<br />
<br />
# If an inaccessible site frustrates you during the holidays, here's how you can take action: http://bit.ly/inaccessible2<br />
# Tired of yelling at your computer about inaccessible websites? A blog post describes what you can do: http://bit.ly/inaccessible1<br />
# Have you used sample emails to contact an organization about its inaccessible site? Start here to check them out: http://bit.ly/inaccessible2<br />
# Help make the Web more accessible during the holidays. Contact an organization to suggest improvements: http://bit.ly/inaccessible2<br />
# Finding a website inaccessible? Tell them! Tips & sample emails - blog http://bit.ly/inaccessible1 & doc http://bit.ly/inaccessible2 #a11y {[http://twitter.com/#!/w3c_wai/status/142632565071810560 WAI tweeted 2 Dec 2011]}<br />
<br />
== Previous blogs, references, etc. ==<br />
<br />
* BS8878<br />
* '''Use this to contact us''' (e.g., "For advice on what information to include when you contact us, we recommend that you read "Contacting Organizations about Inaccessible Websites"):<br />
** [http://www.trinityhouse.co.uk/th/about/accessibility-statement.html trinityhouse.co.uk]<br />
** [http://www.my-farm.org.uk/accessibility-policy my-farm.org.uk]<br />
** [http://aseanidpp.org/node/32 aseanidpp.org]<br />
** [http://www.access8878.co.uk/accessibility-statement.aspx access8878.co.uk]<br />
** [http://www.prostate-cancer.org.uk/accessibility prostate-cancer.org.uk]<br />
** [http://www.pinsentmasons.com/en/accessibility/ pinsentmasons.com]<br />
** [http://www.chestertonhumberts.com/accesibility-statement/ chestertonhumberts.com]<br />
** [http://www.thecrownestate.co.uk/accessibility/?site-quicknav-select=/about-us/faqs/ thecrownestate.co.uk]<br />
** [http://www.somewhereto.com/havingtroubleviewingthispage somewhereto.com]<br />
**...<br />
* blogs, lists, etc.: [http://www.karlgroves.com/2011/08/07/users-must-become-their-own-advocates/ Users Must Become Their Own Advocates, Aug 2011], [http://dboudreau.posterous.com/contacting-organizations-about-inaccessible-w accessiWatch, May 2011], [http://webaim.org/discussion/mail_thread?thread=4677 WebAIM email list, April 2011], [http://answerpot.com/showthread.php?461180-Resource - Contacting Organizations about Inaccessible Websites answerpot, Nov 2010], [http://journal.brokenclay.org/wp_archives/2010/05/03/contacting-organizations-about-inaccessible-websites/ brokenclay.org/journal May 2010], [http://www.sitepoint.com/how-to-tell-organizations-their-website-is-inaccessible/ sitepoint, Feb 2010], [http://www.egov.vic.gov.au/website-practice/accessibility/accessibility-online-and-web/contacting-organizations-about-inaccessible-websites.html eGovernment Resource Centre, Feb 2010], [http://list.universaldesign.ie/pipermail/ceud-ict/2010/002118.html [CEUD-ICT], Jan 2010], [http://evolt.org/node/62403 e-volt, Jan 2010] &amp; [http://blog.adrianroselli.com/2010/01/w3c-contacting-organizations-about.html Adrian Roselli, Jan 2010], [http://www.456bereastreet.com/archive/201001/telling_organisations_that_their_websites_are_inaccessible/ 456 Berea Street, Jan 2010], [http://www.cmswire.com/cms/web-content/w3c-provides-guidance-for-brow-beating-inaccessible-websites-006389.php CMS wire, Jan 2010] "W3C Provides Guidance for Brow Beating Inaccessible Websites" ...<br />
<br />
== EOWG Contacts Dec 2011 ==<br />
<br />
...suggesting an organization do "a blog post that best reflects the organization's position in this matter." (Jennifer)<br />
<br />
'''''See also''' the [[#Published Dec 2011]] list above''<br />
* HeadStar [http://www.headstar.com/eablive/ E-Access Live] and [http://www.headstar.com/site/scripts/documents_info.php?categoryID=1&documentID=11 E-Access Bulletin] - Dan J. (Jennifer, 2 Dec 2011)<br />
* [http://www.afb.org American Foundation for the Blind]- suggested either [http://www.afb.org/blog a blog post] or an article in [http://www.afb.org/accessworld AccessWorld] - Paul S. (Jennifer, 2 Dec 2011)<br />
* [http://www.nfb.org/nfb/access_technology_blog.asp NFB Technology Access Blog] - Mark R & Clara V (Jennifer, 2 Dec 2011)<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (Jennifer, 2 Dec 2011)<br />
* Blog: Do It Myself Blog - Glenda Watson-Hyatt (Char, 6 Dec 2011)<br />
* LinkedIn Groups - Jennison A. (Jennifer, 7 Dec 2011)<br />
* [http://www.visionaware.org Visionaware] - requested a blog post (Jennifer, 2 Dec 2011, via Twitter)<br />
* [http://www.lighthouse-sf.org/ San Francisco Lighthouse] - requested a blog post (Jennifer, 2 Dec 2011, via Twitter)<br />
* [http://www.acb.org The American Council of the Blind] (Jennifer, 7 Dec 2011, via Twitter)<br />
* Jonathan Hassell (Ian, 7 Dec 2011, via email)<br />
* [http://www.atechnews.com/ ATechNews] - John M. Williams (Shawn, 10 Dec 2011)<br />
* [http://www.HumanCenteredDesign.org Institute for Human Centered Design (IHCD)] - Jennifer O. (Shawn, 13 Dec 2011)<br />
* [http://www.mediaaccess.org.au/ Media Access Australia (MAA)] - Sarah P. (Andrew, 16 Dec 2011)<br />
* Knowbility list of 1926 organizations providing disability services, especially employment services. Sent the blurb targeting Job-seekers with disabilities to some of the list and the online shopping blurb to others. (Sharron, 16 Dec 2011) <br />
<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_BAD&diff=143Promoting BAD2012-01-09T04:23:21Z<p>Jsutton2: /* Draft posts/blurbs */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/demos/bad/ Before and After Demo (BAD)] - short uri: http://bit.ly/@@<br />
<br />
* [http://twitter.com/#!/w3c_wai/status/124504842004742144 Tweet], [http://www.w3.org/WAI/#x20111013a WAI highlight & rss feed], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2011OctDec/0003.html WAI IG email] from Oct 2011<br />
* Translations: (none)<br />
<br />
== Audience & Messages ==<br />
<br />
* ...<br />
* ([http://www.w3.org/WAI/EO/Drafts/retrofit/requ-basite.html old audience analysis])<br />
<br />
== Blog posts, newsletter blurbs, etc. ==<br />
[later list here]<br />
<br />
=== Draft posts/blurbs ===<br />
<br />
* Brainstorming -- possible theme -- When something bad becomes good. Making BAD good. (Jennifer, January 8, 2012)<br />
...<br />
<br />
=== Tweet ideas ===<br />
* ...<br />
<br />
== Oct-Dec 2011 blogs, references, etc. ==<br />
<br />
* ...<br />
<br />
== EOWG Recent Contacts ==<br />
[for later]<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Contacts_for_promotion&diff=142Contacts for promotion2012-01-09T04:15:03Z<p>Jsutton2: /* Miscellaneous Items That Need Closer Review/Consideration */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
__TOC__<br />
<br />
'''Suggested format for listings:'''<br />
* What it is - contact person (who knows how to contact them). Notes on what types of material is most relevant for it/them.<br />
<br />
== General Web designer & developer ==<br />
<br />
Lists & Misc:<br />
* [http://www.d.umn.edu/itss/training/online/webdesign/ Web Design References, UMD] - Laura Carlson. [http://www.d.umn.edu/itss/training/online/webdesign/urlform.html form to Suggest a Link]<br />
* [http://www.alistapart.com/articles/ A List Apart] (tech notes?)<br />
* [http://www.smashingmagazine.com Smashing Magazine]<br />
* [http://www.netmagazine.com Net Magazine]<br />
* [http://www.sitepoint.com/ SitePoint]<br />
* [http://radar.oreilly.com OReilly Radar]<br />
* WritersUA monthly user assistance update resource_directory@writersua.com contact: Joe W.<br />
<br />
== Web Accessibility focused ==<br />
<br />
Lists & Misc:<br />
* LinkedIn Groups - Jennison A.<br />
* [http://webaim.org/discussion/ The WebAIM Email Discussion List]<br />
<br />
Blogs:<br />
* [http://blog.knowbility.org/ Knowbility Blog, Universally Designed] - posters: Sharron, Wayne<br />
* Do It Myself Blog - Glenda Watson-Hyatt<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (has contact info: Jennifer, Shawn)<br />
* [http://dboudreau.posterous.com/ accessiWatch v0.1 (2011)] (Denis B.)<br />
* [http://www.paciellogroup.com/blog/ The Paciello Group Blog] (Tech Notes?)<br />
* [http://www.stc-access.org/ STC Accessibility Sig]<br />
* [http://www.coataccess.org Coalition of Organizations for Accessible Technology<br />
(COAT)]<br />
<br />
<br />
Newsletters:<br />
* [http://www.knowbility.org/v/newsletter/ Knowbility] - Sharron R.<br />
* [http://webaim.org/newsletter/ The WebAIM Newsletter] (Jared Smith)<br />
<br />
== Disability focused ==<br />
<br />
Organizations that have blogs, newsletters, lists, etc.:<br />
* [http://www.HumanCenteredDesign.org Institute for Human Centered Design (IHCD)] - Jennifer O. (has contact info: Shawn)<br />
* [http://www.afb.org American Foundation for the Blind] - Paul S. (has contact info: Jennifer, Shawn)<br />
* [http://www.nfb.org/nfb/access_technology_blog.asp NFB Technology Access Blog] - Mark R & Clara V (has contact info: Jennifer, Shawn)<br />
* [http://www.acb.org The American Council of the Blind] - Melanie B. (has contact info: Jennifer)<br />
* [http://www.visionaware.org Visionaware] - ?name (has contact info: Jennifer)<br />
* [http://www.lighthouse-sf.org/ San Francisco Lighthouse] - ?name (has contact info: Jennifer)<br />
* [http://www.eastersealstech.com/content.aspx?pId=682 Podcast - Assistive Technology Update] produced by [http://www.eastersealstech.com/Default.aspx Easter Seals indata Indiana Assistive Technology Act]: The publication is "AT Update" and consists of Fast-paced news, tips, and interviews for AT professionals and enthusiasts. While services are provided throughout Indiana, information seems wide-ranging. Here's the [http://www.eastersealstech.com/content.aspx?pId=87 Contact page].<br />
<br />
<br />
<br />
Blogs:<br />
* [http://www.lflegal.com LF Legal] [especially for policies and standards harmonization)<br />
<br />
Newsletters:<br />
* HeadStar [http://www.headstar.com/eablive/ E-Access Live] and [http://www.headstar.com/site/scripts/documents_info.php?categoryID=1&documentID=11 E-Access Bulletin] - Dan J. (has contact info: Jennifer, Shawn)<br />
<br />
E-mail lists:<br />
* webwatch@accessplace.net (subscribed: Jennifer)<br />
* VICUG-L@LISTSERV.ICORS.ORG 285 members (subscribed: Jennifer)<br />
<br />
Other:<br />
* ...<br />
<br />
== Miscellaneous Items That Need Closer Review/Consideration ==<br />
<br />
*See if any of these [http://www.d.umn.edu/itss/training/online/webdesign/sites.html blogs] seem worth hand-picking<br />
*See if any of these [http://www.d.umn.edu/itss/training/online/webdesign/associations.html associations] seem worth targeting<br />
<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Contacts_for_promotion&diff=141Contacts for promotion2012-01-09T04:10:47Z<p>Jsutton2: </p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
__TOC__<br />
<br />
'''Suggested format for listings:'''<br />
* What it is - contact person (who knows how to contact them). Notes on what types of material is most relevant for it/them.<br />
<br />
== General Web designer & developer ==<br />
<br />
Lists & Misc:<br />
* [http://www.d.umn.edu/itss/training/online/webdesign/ Web Design References, UMD] - Laura Carlson. [http://www.d.umn.edu/itss/training/online/webdesign/urlform.html form to Suggest a Link]<br />
* [http://www.alistapart.com/articles/ A List Apart] (tech notes?)<br />
* [http://www.smashingmagazine.com Smashing Magazine]<br />
* [http://www.netmagazine.com Net Magazine]<br />
* [http://www.sitepoint.com/ SitePoint]<br />
* [http://radar.oreilly.com OReilly Radar]<br />
* WritersUA monthly user assistance update resource_directory@writersua.com contact: Joe W.<br />
<br />
== Web Accessibility focused ==<br />
<br />
Lists & Misc:<br />
* LinkedIn Groups - Jennison A.<br />
* [http://webaim.org/discussion/ The WebAIM Email Discussion List]<br />
<br />
Blogs:<br />
* [http://blog.knowbility.org/ Knowbility Blog, Universally Designed] - posters: Sharron, Wayne<br />
* Do It Myself Blog - Glenda Watson-Hyatt<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (has contact info: Jennifer, Shawn)<br />
* [http://dboudreau.posterous.com/ accessiWatch v0.1 (2011)] (Denis B.)<br />
* [http://www.paciellogroup.com/blog/ The Paciello Group Blog] (Tech Notes?)<br />
* [http://www.stc-access.org/ STC Accessibility Sig]<br />
* [http://www.coataccess.org Coalition of Organizations for Accessible Technology<br />
(COAT)]<br />
<br />
<br />
Newsletters:<br />
* [http://www.knowbility.org/v/newsletter/ Knowbility] - Sharron R.<br />
* [http://webaim.org/newsletter/ The WebAIM Newsletter] (Jared Smith)<br />
<br />
== Disability focused ==<br />
<br />
Organizations that have blogs, newsletters, lists, etc.:<br />
* [http://www.HumanCenteredDesign.org Institute for Human Centered Design (IHCD)] - Jennifer O. (has contact info: Shawn)<br />
* [http://www.afb.org American Foundation for the Blind] - Paul S. (has contact info: Jennifer, Shawn)<br />
* [http://www.nfb.org/nfb/access_technology_blog.asp NFB Technology Access Blog] - Mark R & Clara V (has contact info: Jennifer, Shawn)<br />
* [http://www.acb.org The American Council of the Blind] - Melanie B. (has contact info: Jennifer)<br />
* [http://www.visionaware.org Visionaware] - ?name (has contact info: Jennifer)<br />
* [http://www.lighthouse-sf.org/ San Francisco Lighthouse] - ?name (has contact info: Jennifer)<br />
* [http://www.eastersealstech.com/content.aspx?pId=682 Podcast - Assistive Technology Update] produced by [http://www.eastersealstech.com/Default.aspx Easter Seals indata Indiana Assistive Technology Act]: The publication is "AT Update" and consists of Fast-paced news, tips, and interviews for AT professionals and enthusiasts. While services are provided throughout Indiana, information seems wide-ranging. Here's the [http://www.eastersealstech.com/content.aspx?pId=87 Contact page].<br />
<br />
<br />
<br />
Blogs:<br />
* [http://www.lflegal.com LF Legal] [especially for policies and standards harmonization)<br />
<br />
Newsletters:<br />
* HeadStar [http://www.headstar.com/eablive/ E-Access Live] and [http://www.headstar.com/site/scripts/documents_info.php?categoryID=1&documentID=11 E-Access Bulletin] - Dan J. (has contact info: Jennifer, Shawn)<br />
<br />
E-mail lists:<br />
* webwatch@accessplace.net (subscribed: Jennifer)<br />
* VICUG-L@LISTSERV.ICORS.ORG 285 members (subscribed: Jennifer)<br />
<br />
Other:<br />
* ...<br />
<br />
== Miscellaneous Items That Need Closer Review/Consideration ==<br />
<br />
*See if any of these blogs seem worth hand-picking:<br />
http://www.d.umn.edu/itss/training/online/webdesign/sites.html<br />
*See if any of these associations seem worth targeting:<br />
http://www.d.umn.edu/itss/training/online/webdesign/associations.html<br />
<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Make_Presentations_Accessible&diff=90Promoting Make Presentations Accessible2011-12-09T16:29:44Z<p>Jsutton2: /* Methods: */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
'''''Important note:''''' ''This Wiki page is edited by participants of 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.''<br />
<br />
=== Resources ===<br />
<br />
* Doc: [http://www.w3.org/WAI/training/accessible.php How to Make Presentations Accessible to All]<br />
* [http://www.w3.org/WAI/highlights/archive#x20100616a WAI Highlight June 2010]<br />
* [http://www.w3.org/QA/2010/06/make_your_presentations_access.html WAI blog June 2010]<br />
* Tweet June 2010<br />
* Translations: (none yet)<br />
<br />
=== Audience & Messages ===<br />
<br />
# ...<br />
# ...<br />
* See more in [http://www.w3.org/WAI/EO/changelogs/cl-training#accessibleAnalsysi doc]<br />
<br />
=== Methods: ===<br />
<br />
* [http://chrisbrogan.com Chris Brogan] (Consider whether Jennifer should ask Glenda W-H to promote How to Make Presentations Accessible on his site).<br />
* Promote in relation to SXSW?<br />
* Efforts in relation to CSUN?<br />
* ICCHP?<br />
* See if accessibility barcamps/unconferences will link to it on their sites?<br />
* ...<br />
<br />
==== Draft posts/blurbs ====<br />
...<br />
<br />
==== Tweet ideas ====<br />
<br />
...<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Contacts_for_promotion&diff=89Contacts for promotion2011-12-09T16:23:01Z<p>Jsutton2: /* Web Accessibility focused */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
'''''Important note:''''' ''This Wiki page is edited by participants of 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.''<br />
__TOC__<br />
<br />
'''Suggested format for listings:'''<br />
* What it is - contact person (who knows how to contact them). Notes on what types of material is most relevant for it/them.<br />
<br />
== General Web designer & developer ==<br />
<br />
Lists & Misc:<br />
* [http://www.d.umn.edu/itss/training/online/webdesign/ Web Design References, UMD] - Laura Carlson. [http://www.d.umn.edu/itss/training/online/webdesign/urlform.html form to Suggest a Link]<br />
* [http://www.alistapart.com/articles/ A List Apart] (tech notes?)<br />
* [http://www.smashingmagazine.com Smashing Magazine]<br />
* [http://www.netmagazine.com Net Magazine]<br />
* [http://www.sitepoint.com/ SitePoint]<br />
* [http://radar.oreilly.com OReilly Radar]<br />
<br />
== Web Accessibility focused ==<br />
<br />
Lists & Misc:<br />
* LinkedIn Groups - Jennison A.<br />
* [http://webaim.org/discussion/ The WebAIM Email Discussion List]<br />
<br />
Blogs:<br />
* [http://blog.knowbility.org/ Knowbility Blog, Universally Designed] - posters: Sharron, Wayne<br />
* Do It Myself Blog - Glenda Watson-Hyatt<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (has contact info: Jennifer, Shawn)<br />
* [http://dboudreau.posterous.com/ accessiWatch v0.1 (2011)] (Denis B.)<br />
* [http://www.paciellogroup.com/blog/ The Paciello Group Blog] (Tech Notes?)<br />
* [http://www.stc-access.org/ STC Accessibility Sig]<br />
* [http://www.coataccess.org Coalition of Organizations for Accessible Technology<br />
(COAT)]<br />
<br />
<br />
Newsletters:<br />
* [http://www.knowbility.org/v/newsletter/ Knowbility] - Sharron R.<br />
* [http://webaim.org/newsletter/ The WebAIM Newsletter] (Jared Smith)<br />
<br />
== Disability focused ==<br />
<br />
Organizations that have blogs, newsletters, lists, etc.:<br />
* [http://www.afb.org American Foundation for the Blind] - Paul S. (has contact info: Jennifer, Shawn)<br />
* [http://www.nfb.org/nfb/access_technology_blog.asp NFB Technology Access Blog] - Mark R & Clara V (has contact info: Jennifer, Shawn)<br />
* [http://www.acb.org The American Council of the Blind] - Melanie B. (has contact info: Jennifer)<br />
* [http://www.visionaware.org Visionaware] - ?name (has contact info: Jennifer)<br />
* [http://www.lighthouse-sf.org/ San Francisco Lighthouse] - ?name (has contact info: Jennifer)<br />
<br />
Blogs:<br />
* [http://www.lflegal.com LF Legal] [especially for policies and standards harmonization)<br />
<br />
Newsletters:<br />
* HeadStar [http://www.headstar.com/eablive/ E-Access Live] and [http://www.headstar.com/site/scripts/documents_info.php?categoryID=1&documentID=11 E-Access Bulletin] - Dan J. (has contact info: Jennifer, Shawn)<br />
<br />
E-mail lists:<br />
* webwatch@accessplace.net (subscribed: Jennifer)<br />
* VICUG-L@LISTSERV.ICORS.ORG 285 members (subscribed: Jennifer)<br />
<br />
Other:<br />
* ...<br />
<br />
== Miscellaneous Items That Need Closer Review/Consideration ==<br />
<br />
*See if any of these blogs seem worth hand-picking:<br />
http://www.d.umn.edu/itss/training/online/webdesign/sites.html<br />
*See if any of these associations seem worth targeting:<br />
http://www.d.umn.edu/itss/training/online/webdesign/associations.html<br />
<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Contacts_for_promotion&diff=88Contacts for promotion2011-12-09T16:19:57Z<p>Jsutton2: /* General Web designer & developer */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
'''''Important note:''''' ''This Wiki page is edited by participants of 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.''<br />
__TOC__<br />
<br />
'''Suggested format for listings:'''<br />
* What it is - contact person (who knows how to contact them). Notes on what types of material is most relevant for it/them.<br />
<br />
== General Web designer & developer ==<br />
<br />
Lists & Misc:<br />
* [http://www.d.umn.edu/itss/training/online/webdesign/ Web Design References, UMD] - Laura Carlson. [http://www.d.umn.edu/itss/training/online/webdesign/urlform.html form to Suggest a Link]<br />
* [http://www.alistapart.com/articles/ A List Apart] (tech notes?)<br />
* [http://www.smashingmagazine.com Smashing Magazine]<br />
* [http://www.netmagazine.com Net Magazine]<br />
* [http://www.sitepoint.com/ SitePoint]<br />
* [http://radar.oreilly.com OReilly Radar]<br />
<br />
== Web Accessibility focused ==<br />
<br />
Lists & Misc:<br />
* LinkedIn Groups - Jennison A.<br />
* [http://webaim.org/discussion/ The WebAIM Email Discussion List]<br />
<br />
Blogs:<br />
* [http://blog.knowbility.org/ Knowbility Blog, Universally Designed] - posters: Sharron, Wayne<br />
* Do It Myself Blog - Glenda Watson-Hyatt<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (has contact info: Jennifer, Shawn)<br />
* [http://dboudreau.posterous.com/ accessiWatch v0.1 (2011)] (Denis B.)<br />
* [http://www.paciellogroup.com/blog/ The Paciello Group Blog] (Tech Notes?)<br />
* [http://www.stc-access.org/ STC Accessibility Sig]<br />
<br />
<br />
<br />
Newsletters:<br />
* [http://www.knowbility.org/v/newsletter/ Knowbility] - Sharron R.<br />
* [http://webaim.org/newsletter/ The WebAIM Newsletter] (Jared Smith)<br />
<br />
== Disability focused ==<br />
<br />
Organizations that have blogs, newsletters, lists, etc.:<br />
* [http://www.afb.org American Foundation for the Blind] - Paul S. (has contact info: Jennifer, Shawn)<br />
* [http://www.nfb.org/nfb/access_technology_blog.asp NFB Technology Access Blog] - Mark R & Clara V (has contact info: Jennifer, Shawn)<br />
* [http://www.acb.org The American Council of the Blind] - Melanie B. (has contact info: Jennifer)<br />
* [http://www.visionaware.org Visionaware] - ?name (has contact info: Jennifer)<br />
* [http://www.lighthouse-sf.org/ San Francisco Lighthouse] - ?name (has contact info: Jennifer)<br />
<br />
Blogs:<br />
* [http://www.lflegal.com LF Legal] [especially for policies and standards harmonization)<br />
<br />
Newsletters:<br />
* HeadStar [http://www.headstar.com/eablive/ E-Access Live] and [http://www.headstar.com/site/scripts/documents_info.php?categoryID=1&documentID=11 E-Access Bulletin] - Dan J. (has contact info: Jennifer, Shawn)<br />
<br />
E-mail lists:<br />
* webwatch@accessplace.net (subscribed: Jennifer)<br />
* VICUG-L@LISTSERV.ICORS.ORG 285 members (subscribed: Jennifer)<br />
<br />
Other:<br />
* ...<br />
<br />
== Miscellaneous Items That Need Closer Review/Consideration ==<br />
<br />
*See if any of these blogs seem worth hand-picking:<br />
http://www.d.umn.edu/itss/training/online/webdesign/sites.html<br />
*See if any of these associations seem worth targeting:<br />
http://www.d.umn.edu/itss/training/online/webdesign/associations.html<br />
<br />
<br />
<br />
__NOINDEX__</div>Jsutton2https://www.w3.org/WAI/EO/wiki/index.php?title=Promoting_Contact_Orgs_Inaccessible_Sites&diff=85Promoting Contact Orgs Inaccessible Sites2011-12-09T00:45:24Z<p>Jsutton2: /* Published Dec 2011 */</p>
<hr />
<div>Nav: [[Main Page|EOWG wiki main page]]<br />
<br />
'''''Important note:''''' ''This Wiki page is edited by participants of 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.''<br />
<br />
== Resources & Pointers ==<br />
* Document: [http://www.w3.org/WAI/users/inaccessible.html Contacting Organizations about Inaccessible Websites] - short uri: http://bit.ly/inaccessible2<br />
<br />
* [http://twitter.com/#!/w3c_wai/status/142632565071810560 Tweet 2 Dec 2011]<br />
<br />
* Blog post: [http://www.w3.org/QA/2010/01/encourage_accessibility_make_a_difference.html Take a few minutes to encourage web accessibility. You can make a difference.] Jan 2010 - short uri: http://bit.ly/inaccessible1<br />
<br />
* [http://lists.w3.org/Archives/Public/w3c-wai-ig/2010JanMar/0003.html WAI IG e-mail Jan 2010], [http://lists.w3.org/Archives/Public/w3c-wai-ig/2010AprJun/0010.html WAI IG e-mail April 2010], [http://www.w3.org/WAI/highlights/archive#x20100106a WAI highlight Jan 2010]<br />
* Translations:<br />
** [http://www.discapnet.es/Castellano/areastematicas/Accesibilidad/Direcciones%20interes/Paginas/Como_contactar_con_organizaciones_con_sitios_web_inaccesibles.aspx Spanish]<br />
<br />
== Audience & Messages ==<br />
<br />
# Audience: Users - people who want to report accessibility barriers.<br>Message: use this resource to help you - make it easier and hopefully more effective<br />
# Audience: Owners - websites owners & developers.<br>Message: point users to this resource to help them give you more useful feedback about accessibility issues (e.g., [http://www.pinsentmasons.com/en/accessibility/ example under Contacting Us])<br />
* More details of [http://www.w3.org/WAI/EO/changelogs/cl-responding.html#audience audience in contacting initial analysis]<br />
<br />
== Blog posts, newsletter blurbs, etc. ==<br />
<br />
=== Published Dec 2011 ===<br />
* e-mail lists:<br />
** webwatch@accessplace.net (Jennifer, 2 Dec 2011)<br />
** VICUG-L@LISTSERV.ICORS.ORG 285 members (Jennifer, 2 Dec 2011)<br />
** ...<br />
<br />
* blog posts:<br />
** [http://blog.knowbility.org/2011/12/06/retailers-help-your-customers-with-disabilities-help-you/ Knowbility Blog] 6 Dec 2011<br />
** [http://www.nfb.org/NewsBot.asp?MODE=VIEW&ID=888&SnID=247008194 Speaking up about inaccessible Web sites] (NFB Blog post, 8 Dec <br />
** [http://webaxe.blogspot.com/2011/12/podcast-93-teaching-mistakes.html Podcast 93: Teaching Mistakes] (Dennis L., 7 Dec 2011)<br />
<br />
* 2011) newsletters:<br />
** [http://paper.li/Hear_And_There/1306429577/2011/12/02 Hear and There #Accessibility News] 2 Dec 2011<br />
** Knowbility December 2011 Newsletter. 12 Dec 2011<br />
** ...<br />
<br />
''(Older WAI ones are listed in [[#Resources & Pointers]] above and others are listed in [[#Previous blogs, etc.]] below.)''<br />
<br />
=== Draft posts/blurbs ===<br />
<br />
==== Audience: Users - Short (initial editor: Jennifer Sutton) ====<br />
<br />
[disabilities audience] During the holidays, shopping online can be frustrating for people with disabilities. Does any of this sound familiar? You have the perfect gift in mind,...<br />
<br />
[broader audience] During the holidays, shopping online can be frustrating for people with disabilities. Imagine how you’d feel if you have the perfect gift in mind,...<br />
<br />
...but then, you can't read the site easily, you can't find the item amid all of the links on the page, you aren't sure whether the item is really in your shopping cart, or you can't check out independently. It's not fun when you can't keep a gift a secret because you can't buy it without help. Complaining on Twitter or Facebook won't help much in the longrun. So, how can you raise your concerns constructively, spread good cheer while helping to make the Web more accessible, and start getting positive results? Try visiting these two pages for some tips and sample email messages. See blog<br />
http://bit.ly/inaccessible1 and document http://bit.ly/inaccessible2<br />
<br />
==== Audience: Users - Longer (initial editor: Jennifer Sutton) ====<br />
<br />
''{To newsletter editors: You are welcome to use this verbatim attributed to Jennifer Sutton. If you would like to make edits, contact Jennifer at jsuttondc@gmail.com}''<br />
<br />
When I go online during the holidays, I just want to find what I'm looking for and check out without needing any help. But sometimes, by the time I'm done, my holiday cheer is beginning to fade. Trying to use an inaccessible site to buy a gift or make a donation on behalf of a loved one can take time I simply don't have during the busy holiday season.<br />
<br />
But if I spend a little extra time to report my experiences to the organizations that run the sites I visit, I believe my efforts will make the Web a better place next year. <br />
<br />
As I make my shopping list and gather links to the sites I plan to visit, I'm adding a couple of other links to my collection, so they'll be handy. I'm also setting up an email template or two in advance to help me quickly report my shopping experiences -- both the good ones and the ones that are harder than I might wish. Why not join me and start off your New Year positively by helping to make the Web a more accessible place?<br />
<br />
Find tips about giving accessibility feedback to Web sites by visiting these two Web pages, brought to you by the World Wide Web Consortium's Web Accessibility Initiative: blog http://bit.ly/inaccessible1 and document http://bit.ly/inaccessible2.<br />
<br />
==== Audience: Web Managers and Developers (initial editor: Sharron Rush) ====<br />
<br />
If you sell goods and services online, you have an eager market of more than 750 million people throughout the world. In the United States alone, this group maintains an aggregate income that now exceeds $1 trillion and boasts $220 billion in discretionary spending power, according to Fortune Magazine. <br />
<br />
As ideal as it sounds, many online retailers fail to reach this valuable market because their web sites are not accessible to the group described - people with disabilities. This large and growing group of customers is likely to lose interest when form inputs aren't labeled, graphic elements are not described, or the next step in a purchase process shows up in a modal dialogue that can't be found by assistive technology. These and other design barriers can make online shopping miserable for potential buyers with disabilities.<br />
<br />
If your customers are frustrated, you want to know about it. The [http://www.w3.org/WAI Web Accessibility Initiative] at the W3C has a resource to help them communicate with you in a constructive and useful way. Consider posting a link on your shopping pages for customers who encounter shopping barriers.<br />
<br />
The guide is called [http://www.w3.org/WAI/users/inaccessible Contacting Organizations about Inaccessible Websites] and can help your potential customers describe specific areas of pain. Open the channels of communication to potential customers with disabilities. You may make their holidays much merrier and give yourself the gift of a new customer who is likely to return. May all your holidays be bright!<br />
<br />
==== Audience: UN Organizations (initial editor: Vicki Menezes Miller) ====<br />
<br />
Web Accessibility - Watch This Corner:<br />
Help make the Web more accessible during the holidays.<br />
The UN Convention on the Rights of Persons with Disabilities, Article 9(g) requires that web sites are accessible to all.<br />
W3C Web Accessibility Initiative provides a wealth of resources and guidance,<br />
This month: If you want to contact an organization to suggest improvements in web accessibility, go to: http://bit.ly/inaccessible2<br />
<br />
=== Tweet ideas ===<br />
<br />
# If an inaccessible site frustrates you during the holidays, here's how you can take action: http://bit.ly/inaccessible2<br />
# Tired of yelling at your computer about inaccessible websites? A blog post describes what you can do: http://bit.ly/inaccessible1<br />
# Have you used sample emails to contact an organization about its inaccessible site? Start here to check them out: http://bit.ly/inaccessible2<br />
# Help make the Web more accessible during the holidays. Contact an organization to suggest improvements: http://bit.ly/inaccessible2<br />
# Finding a website inaccessible? Tell them! Tips & sample emails - blog http://bit.ly/inaccessible1 & doc http://bit.ly/inaccessible2 #a11y {[http://twitter.com/#!/w3c_wai/status/142632565071810560 WAI tweeted 2 Dec 2011]}<br />
<br />
== Previous blogs, references, etc. ==<br />
<br />
* BS8878<br />
* Use this to contact us: [http://www.pinsentmasons.com/en/accessibility/ pinsentmasons.com]<br />
* blogs, lists, etc.: [http://www.karlgroves.com/2011/08/07/users-must-become-their-own-advocates/ Users Must Become Their Own Advocates, Aug 2011], [http://dboudreau.posterous.com/contacting-organizations-about-inaccessible-w accessiWatch, May 2011], [http://webaim.org/discussion/mail_thread?thread=4677 WebAIM email list, April 2011], [http://answerpot.com/showthread.php?461180-Resource - Contacting Organizations about Inaccessible Websites answerpot, Nov 2010], [http://journal.brokenclay.org/wp_archives/2010/05/03/contacting-organizations-about-inaccessible-websites/ brokenclay.org/journal May 2010], [http://www.sitepoint.com/how-to-tell-organizations-their-website-is-inaccessible/ sitepoint, Feb 2010], [http://www.egov.vic.gov.au/website-practice/accessibility/accessibility-online-and-web/contacting-organizations-about-inaccessible-websites.html eGovernment Resource Centre, Feb 2010], [http://list.universaldesign.ie/pipermail/ceud-ict/2010/002118.html [CEUD-ICT], Jan 2010], [http://evolt.org/node/62403 e-volt, Jan 2010] &amp; [http://blog.adrianroselli.com/2010/01/w3c-contacting-organizations-about.html Adrian Roselli, Jan 2010], [http://www.456bereastreet.com/archive/201001/telling_organisations_that_their_websites_are_inaccessible/ 456 Berea Street, Jan 2010], [http://www.cmswire.com/cms/web-content/w3c-provides-guidance-for-brow-beating-inaccessible-websites-006389.php CMS wire, Jan 2010] "W3C Provides Guidance for Brow Beating Inaccessible Websites"<br />
<br />
<br />
== EOWG Recent Contacts ==<br />
<br />
...suggesting an organization do "a blog post that best reflects the organization's position in this matter." (Jennifer)<br />
<br />
'''''See also''' the [[#Published Dec 2011]] list above''<br />
* [http://www.afb.org American Foundation for the Blind]- suggested either [http://www.afb.org/blog a blog post] or an article in [http://www.afb.org/accessworld AccessWorld] - Paul S. (Jennifer, 2 Dec 2011)<br />
* [http://www.nfb.org/nfb/access_technology_blog.asp NFB Technology Access Blog] - Mark R & Clara V (Jennifer, 2 Dec 2011)<br />
* HeadStar [http://www.headstar.com/eablive/ E-Access Live] and [http://www.headstar.com/site/scripts/documents_info.php?categoryID=1&documentID=11 E-Access Bulletin] - Dan J. (Jennifer, 2 Dec 2011)<br />
* [http://www.nomensa.com/blog/ Nomensa's Humanizing Technology Blog] - Léonie W (Jennifer, 2 Dec 2011)<br />
* Blog: Do It Myself Blog - Glenda Watson-Hyatt (Char, 6 Dec 2011)<br />
* LinkedIn Groups - Jennison A. (Jennifer, 7 Dec 2011)<br />
* [http://www.visionaware.org Visionaware] - requested a blog post (Jennifer, 2 Dec 2011, via Twitter)<br />
* [http://www.lighthouse-sf.org/ San Francisco Lighthouse] - requested a blog post (Jennifer, 2 Dec 2011, via Twitter)<br />
* [http://www.acb.org The American Council of the Blind] (Jennifer, 7 Dec 2011, via Twitter)</div>Jsutton2