Re: [WSG] So this is *the* good accessible keyboard supported dropdown menu?
Hi all The linked example provided by tee i belive was taken from here: http://www.html5accessibility.com/index-aria.html the example: http://hanshillen.github.com/aegisdemo/ is provided as an alternative to the HTML5 menu control. The HTML5 menu control has not been implemented yet, but will almost certainly have the same or similar behaviour on each browser and interaction keystrokes will be same or similar to platforms standards for menu controls. The example uses standard interaction keystrokes for menu controls, it also exposes the correct semantics roles/states/properties for a menu widget, much like the menu control in HTML5 will when implemented. regards Stevef On 15 October 2010 03:09, Al Sparber aspar...@roadrunner.com wrote: From: tee weblis...@gmail.com At Menubar, try tab through the link using your keyboard, right after you hit File, the next link it headed is the download link below the Source. http://hanshillen.github.com/aegisdemo/ As a Superfish script and a frequent keyboard navigation user, I expect the second tabbing destination to be the Edit menu because of many comments and articles I read which were written by accessibility practitioners and those who never missed the opportunity to stone Superfish every time they see a chance. I was a bit lost when I didn't see the orange focus color for Edit after I tabbed through the File; first I thought it behaves like Superfish (which heads for 2nd level). Then I realized I must use the 'right arrow' to navigate to Edit, is this the absolute way for keyboard user to expect that a an accessible keyboard supported dropdown menu will only work like this using arrow keys? Probably. I think there is a faction in the accessibility community that believes a web page menu should work like a desktop application or OS menu. The problem is that web surfing civilians who use the keyboard are accustomed to the tab key (or equiv) and not the arrow keys for navigating a web page. Complicating the matter now, of course, are smart phones. In our own simplistic, unsophisticated way, we've taken a much different view of menu accessibility. While most experienced standards and accessibility experts seem to disagree with us, our testing lab, consisting of real people with real disabilities, seems to think it makes sense. http://www.projectseven.com/products/menusystems/pmm2/ug-examples/accessible/ I'm sure some here will disagree, so just consider it one possible solution. -- Al Sparber - PVII http://www.projectseven.com Dreamweaver Menus | Galleries | Widgets http://www.projectseven.com/go/hgm The Ultimate Web 2.0 Carousel *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Yes or No? HTML5 FOR WEB DESIGNERS
good places to start with HTML5 are: HTML: The Markup Language http://www.w3.org/TR/html-markup/ HTML5 (Edition for Web Authors) http://dev.w3.org/html5/spec-author-view/ regards stevef On 17 August 2010 16:18, Jason Grant ja...@flexewebs.com wrote: A good starting point is the spec itself I would say. You shouldn't be going far off with reading the spec or at least skimming through it. I think W3C now has the 'human optimised' version of the spec and not just the browser vendor 900+ page and growing version only. Cheers, Jason On Tue, Aug 17, 2010 at 4:12 PM, David Storey dsto...@opera.com wrote: On 17 Aug 2010, at 16:49, jeffrey morin wrote: Does anyone have an opinion on whether the book, HTML5 FOR WEB DESIGNERS by Jeremy Keith is worth the purchase? I want to learn more about HTML5 but am turned off by the shameless promotion they've done for this book. Does anyone have any suggestions on other books or if this is worth it? Depends what you want it for. I've not read it, but I heard it was a good primer to introduce you to the topic. It is a fairly short book, so doesn't go indepth. There is another book, Introducing HTML5 - introducinghtml5.com - which is more indepth. It covers the semantics and such in the first half and the JS APIs, Cavas and such in the second half. I've just started reading this, but it is by all accounts a good book. A disclaimer is that I work with one of the authors at Opera. Thanks, Jeff *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** David Storey Chief Web Opener / Product Manager, Opera Dragonfly W3C WG: Mobile Web Best Practices / SVG Interest Group Opera Software ASA, Oslo, Norway Mobile: +47 94 22 02 32 / E-Mail/XMPP: dsto...@opera.com / Twitter: dstorey *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** -- Jason Grant BSc, MSc CEO, Flexewebs Ltd. www.flexewebs.com ja...@flexewebs.com +44 (0)7748 591 770 Company no.: 5587469 www.flexewebs.com/semantix www.twitter.com/flexewebs www.linkedin.com/in/flexewebs *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
[WSG] HTML5: Techniques for providing useful text alternatives
HTML5: Techniques for providing useful text alternatives http://dev.w3.org/html5/alt-techniques/ This document is a work in progress currently edited by me, I encourage anyone with an interest to contribute to its development. Document aims: * Provide clear and practical advice on how to provide appropriate text alternatives for images using currently supported techniques * How to make use of the new features available in HTML5 and WAI-ARIA for providing text alternatives. * Understanding the advantages and disadvantages of each technique in reference to browser and assistive technology support. * Provide normative rules for each technique in regards to whether its correct use results in a conforming HTML5 document. * Harmonization of HTML5 document conformance in regards to image text alternatives with WCAG 2.0. The document has been put forward as a First Public Working Draft in the W3C HTML WG, it is expected this initial publication will occur next month. How you can help: If you are not a member of the W3C HTML WG: Email the HTML WG public comments list: public-html-comme...@w3.org Email me: faulkner.st...@gmail.com Or preferably File a bug If you are a member of the HTML WG email the list or me or preferably file a bug http://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WGcomponent=alt%20techniques%20(editor:%20Steven%20Faulkner) -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Assistance with flash example sites
hi russ the bbc childrens sites makes extensive use of flash for their games: cbeebies games for switch and special needs: http://www.bbc.co.uk/cbeebies/games/theme/switch/ keyboard: http://www.bbc.co.uk/cbeebies/games/theme/keyboard/ CBBC switch http://www.bbc.co.uk/cbbc/games/switch/ general: some are keyboard accessible http://www.bbc.co.uk/cbbc/games/ regards steve On 1 February 2010 03:52, Russ Weakley r...@maxdesign.com.au wrote: Hi people, A colleague has just asked me for some examples of Flash sites: 1. examples of flash sites which are not keyboard accessible (and/or poor tab ordering) 2. examples of flash sites which ARE keyboard accessible 3. examples of flash sites which work well with screen readers (He is aware of the Harry Potter Flash site, but is after other, possibly more recent examples) Please no comments about the merits or lack of merits of Flash. This is for some research he is conduction. :) Thanks Russ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] a WCAG 2.0 question
hi glenda, Changing the setting of any user interface component is changing some state in the control that will persist when the user is no longer interacting with it. So checking a checkbox or entering text into a text field changes its setting, but activating a link or a button does not. http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.html I think this makes it clear that on input does not refer to activating a link. regards stevef 2009/3/12 Glen Wallis glen.wal...@velocitynet.com.au: Hello all I am interested to know whether the people on this list consider opening a new window without alerting the user to be a failure to conform to Success Criterion 3.2.2 of WCAG 2.0. The success criterion is as follows: 3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behaviour before using the component. (Level A) The key phrases, I believe are “user interface component” and “change of context”. I looked up the definitions of both phrases. The glossary states quite clearly that a link is a user interface component and that a change of context includes opening a new window. However, the document “Understanding SC 3.2.2” says “Additional Techniques (Advisory) for 3.2.2 Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations. Giving users advanced warning when opening a new window. (future link)” This seems like a contradiction. The WCAG 2.0 Recommendation is the only normative document, so it should take precedence over the Understanding document. However, the Understanding document specifically states that warning the user is not required for conformance. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] The notion of accessibility [was: Javascript Accessibility]
HI Mathew So now a slight rant... I dont understand how: span role=aria-checkbox is better than: input type=checkbox ... ? 3 points 1. The ARIA spec recommends the use of native semantics where ever possible: Use native markup when possible. Use the semantic elements that are defined in the host markup language. For example, with HTML or XHTML, it is better to use the native checkbox than to use a div element with role checkbox as these should already be accessible through your browser. There may also be cases where ARIA can augment an existing element in the host language. For example, a grid and gridcell elements can reuse the functionality of a table when overlaying it. ARIA roles, states, and properties are best used when the markup language does not support all the semantics required. When a role attribute is added to an element, the semantics and behavior of the element are augmented or overridden by the role behavior. [1] 2. WAI-ARIA is not just for HTML, it is designed to be used with other languages such as XUL and SVG. SVG does not contain any native markup for controls, so this is a case where the ARIA roles for controls can be useful. 3. If a developer wants a tri-state checkbox in HTML it may be appropriate to use input type=image role=aria-checkbox aria-checked=mixed ... example: http://www.paciellogroup.com/blog/misc/ARIA/tristatecheck.html [1] http://www.w3.org/TR/wai-aria/#buildingaccessibleapplications regards stevef 2009/3/2 Mathew Robertson mat...@optusnet.com.au: On 3/2/09 2:02 AM, Mathew Robertson mat...@optusnet.com.au wrote: Its been possible to do ARIA style accessibility since about 1995 - its just now that people are starting to care. Matt Morgan-May matt...@adobe.com wrote: Not sure what value you were hoping to add to the conversation, but MSAA, the Windows accessibility API, didn't come out until April 1997. And that much of what ARIA has to offer is actually enabled by the IAccessible2 or User Interface Automation APIs, which are much more recent and comprehensive. ARIA is a very ambitious spec, and a number of companies contributing to its support in a very short period of time, relative to the work that's necessary. But, thanks for the cynicism! We don't get enough of that on the Internet these days. :) :) It was definitly meant as a little cynisism... I did say about 1995 - so I should have been more specific as to the actual year... so I'll expand my sentiment (it might be a little long-winded for some people...). Firstly, accessibilty is not *just* about being able to keystrokes, as its been possible to use braille devices in linux before 1995 (aka Win95 came out that year), using a serial console. Its not just about supporting disability, it also represents support for other languages, layouts, and so on. Indeed as someone quite bright wrote (I dont have a link), making applications more accessible, helps not only those that specifically need that extra help, but also those that simply make use of those features. For example: to using a serial console for text display, has been available since the first mainframes existed - so braille devices worked too. One would expect that new user interface paradigms could provide at least a similar equivalent - in browser terms, it should have been possible to navigate with keyboard and screen-reader only, and it was (albeit it was quite clunky). So one variation of accesbility, is to support multiple languages. Its easy to look back with hindsight, but it was pretty apparent that UTF8 and Unicode was the direction for accessible language support. This was available from about 1993 - the real issue here appers that software vendors chose a different path (eg: Java choosing to use double-byte characters), then became committed to it. And indeed we now see that braille support has been added to Unicode, abeit only recently - imagine the accessibility support that would currently be available, if Win95 had have support unicode natively (font rendering and keycode composition) from day dot... alt tags have been available since html 1, with its recommended practise to show blank for img's that dont mean anything. longdesc has been available since html 4 (1998). Using the tab-key to navigate between elements, has been available in pretty much all browsers, for a long time - however it was cumbersome. However, from MSIE 4 (1997), tabindex became available (it took some time longer before Netscape had support for tabindex) - this made it possible to produce decent navigation for web pages. Text language and direction was added in html 4 - making Hebrew (et. al.) accessible. Finally, the keypress event handler has be around in various incarnations, not long afer Javascript was added to browsers. Its not unreasonable to require web developers to acutally use it (as opposed to just relying on click
[WSG] As a web developer do you find the 'HTML5 the mark up language' a useful document?
The the W3C HTML working group is currently debating the usefulness of HTML 5: The Markup Language http://shrinkster.com/13zy vs HTML 5 A vocabulary and associated APIs for HTML and XHTML http://shrinkster.com/13zz as normative documents for web developers to use as a reference point in their work. What are you thoughts? If you twitter and would like to respond please use the hashtag #html5ml http://twitter.com/stevefaulkner/status/1154883169 -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Validating (X)HTML + ARIA
H Ben I think the more serious compatibility problem with ARIA is the immaturity and rapid pace of change of the draft specifications and implementations. The ARIA spec is expected to go to last call end of february, so the spec will be pretty stable by this point. From my understanding the stability of the spec in regards to landmark roles, there will be no further changes, so their use can be recommended. As fas as implementations go the same message applies. 2009/1/21 Benjamin Hawkes-Lewis bhawkesle...@googlemail.com: On 20/1/09 23:13, Anthony Ziebell wrote: because an implementation of ARIA without using JavaScript to do so would essentially mean a drop of support of legacy browsers If all you are doing is adding some unrecognized ARIA attributes to _existing_ HTML or XHTML content, then such attributes are (realistically) not going to harm users of legacy browsers. Some aspects of ARIA (such as tabindex for all elements and negative values of tabindex) were implemented in some older browsers, even though invalid in HTML 4.x and XHTML 1.x, long before ARIA was proposed. In so far as new assistive technology performs any DOM inspections for ARIA attributes in legacy browsers (probably not much), the presence of ARIA attributes might help users of those combinations. So long as you continue to use the same HTML 4.01 or XHTML 1.x elements to mark up the same content, I don't understand why the additional inclusion of ARIA attributes (say, landmark roles) should make any difference to support of legacy browsers. For example, if you enhanced a document with you a Skip to main content link by additionally marking up your navigation area with role=navigation and your main content area with role=main, the net effect of adding ARIA attributes on backwards compatibility could be positive. I can see a conflict with backwards compatibility if you let the presence of ARIA attributes change how you author your content. For example, if you _replaced_ a Skip to main content link by marking up your navigation area with role=navigation and your main content area with role=main, you'd be replacing a technique that works for a given set of older user agent software with a technique that works for a given set of newer user agent software. In that scenario, the net effect of adding ARIA attributes on backwards compatibility could be negative. Similarly, if you depended on ARIA to communicate semantics available in existing (X)HTML (say replacing h2 with div role='heading' aria-level='2') or if you introduce new semantics/functionality communicable with ARIA but not existing (X)HTML are essential to understanding/using your content rather than an enhancement , you'd lose backwards compatibility for your content. So as you can see, progressively enhancing with ARIA doesn't equate to adding ARIA attributes with JavaScript, but rather to using ARIA as an enhancement rather than replacement whether dependent on JS or not. I think the more serious compatibility problem with ARIA is the immaturity and rapid pace of change of the draft specifications and implementations. -- Benjamin Hawkes-Lewis *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] is there a way to force legend text shows in TWO lines?
hi tee, this article gives you some idea of how screen readers use fieldsets/legends http://www.paciellogroup.com/blog/?p=3 also worthwhile: Too much accessibility - FIELDSET LEGENDS (http://www.rnib.org.uk/wacblog/articles/too-much-accessibility/too-much-accessibility-fieldset-legends/) In your example, the legend includes instructional text. I suggest a more appropriate legend would be shipping estimate and the select elements label as destination -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Google chrome... Accessibility coming very soon???
Hi Christian, Just clear up my understanding, folks; is Internet Explorer accessible because Microsoft builds the accessibility features The short answer is yes Details of the accessibility of internet Explorer can be found in the VPAT (voluntary product accessibility template) supplied by Microsoft: (http://download.microsoft.com/download/c/2/3/c23bc250-5f80-4d0c-a29d-877355ff91e8/IE7_VPAT%20version%201%200.doc) - word doc and the VPAT for Firefox 3 is available here: http://www.mozilla.com/en-US/firefox/vpat-3.html I have reproduced the relevant VPAT info for Internet Explorer 7 below: Section 1194.21 Software Applications and Operating Systems - Detail Voluntary Product Accessibility Template (a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. Supported with Exceptions: Windows Internet Explorer 7 supports all standard keyboard features of the user interface. Windows Internet Explorer 7 provides Help functionality that includes easily accessible reference guides for keyboard shortcuts. In addition, documentation on Keyboard Shortcut keys are available online: http://windowshelp.microsoft.com/Windows/en-US/Help/fe192a3f-1401-4233-919e-cae97eca4c0c1033.mspx More documents on this subject can be found at: http://www.microsoft.com/enable/products/keyboard.aspx Windows Internet Explorer 7 provides a new user interface; keyboard users can use the Alt key to activate the classical menu. Exceptions: Windows Internet Explorer 7 browser arbitrary text content cannot be selected by the keyboard. Text can be selected by using a mouse or other pointing device. Windows Internet Explorer 7 supports all standard keyboard operation of the user interface. Java and in-page plug-ins for content such as Flash cannot be used with the keyboard so they must not be installed for keyboard-only users. The tab order skips over in-page objects completely, so form controls within them cannot be used without a mouse. (b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. Supported with Exceptions: Windows Internet Explorer 7 supports system StickyKeys, FilterKeys, MouseKeys, SerialKeys and ToggleKeys. Exceptions: Windows Internet Explorer 7 does not use the cursor width from the system setting. (c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes. Supported with Exceptions: Windows Internet Explorer 7 uses programming interfaces to expose the location of the focus indicator and Microsoft Active Accessibility(R) to expose its interface elements to assistive technologies. Microsoft Active Accessibility is a COM-based technology that improves the way accessibility aids work with applications running on the Microsoft Windows operating systems. It provides dynamic-link libraries that are incorporated into the operating system, as well as a COM interface and application programming elements that provide reliable methods for exposing information about user interface elements. Exceptions: The caret indication is neither visible nor programmatically exposed in read-only fields. (d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text. Supported: Windows Internet Explorer 7 user interface elements are exposed programmatically through native object models and programming interfaces such as Microsoft Active Accessibility. Standard Windows controls and interface elements automatically expose this information through Microsoft Active Accessibility. Labels are associated with controls, objects, icons and images in Internet Explorer user interface. (e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. Supported: Windows Internet Explorer 7 utilizes standard and consistent images throughout. (f) Textual information shall be provided through operating system functions for displaying text. The minimum
Re: [WSG] Google chrome... Accessibility coming very soon???
Hi Kevin I have written about some of the accessibility issues with google chrome: http://www.paciellogroup.com/blog/?p=92 regards stevef 2008/9/3 kevin erickson [EMAIL PROTECTED]: I have a huge concern about accessibility here. Apparently Jaws and other screen readers don't work on Google Chrome at all. Can others please confirm? kevin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Jump Menu Title attributes
Hi Kevin, What is the best title attribute wording to indicate a link is a jump link (page navigation links)? using the title attribute on a link to describe its purpose means that the information will not be available to the 2 user groups that the skip link is primarily designed to aid. 1. keyboard only users 2.screen reader users info about the accessibility of title attrbutes on links is available : http://www.paciellogroup.com/blog/?p=37 On 12/03/2008, Erickson, Kevin (DOE) [EMAIL PROTECTED] wrote: Hi All, What is the best title attribute wording to indicate a link is a jump link (page navigation links)? Thank you very much, Kevin *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] strong element being more semantical and accessible for required field
i have written up results from some tests i carried out: Screen Readers lack emphasis - http://www.paciellogroup.com/blog/?p=41 On 27/02/2008, tee [EMAIL PROTECTED] wrote: Hi Steven, On Feb 26, 2008, at 6:49 AM, Steven Faulkner wrote: don't know if this has been pointed out yet, but as far as screen readers like JAWS and Window Eyes are concerned the strong element does not convey any meaning. It is not recognised by them. bottom line is that for users these screen readers using strong as an indication of a required field won't be of any help. Thanks for the great info. Exactly what I am after. I like the way Mike grouped the required elements, will borrow the idea for the next form. tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] strong element being more semantical and accessible for required field
don't know if this has been pointed out yet, but as far as screen readers like JAWS and Window Eyes are concerned the strong element does not convey any meaning. It is not recognised by them. They do not change the way text within strong elements are announced, but neither do they do it for em or b or i etc. JAWS does have a speech and sound scheme that includes modified announements of italicised or bolded text (amogst other things), this is not a default scheme, though and is provided for tasks such as proofreading. but this facility is based on how the text is rendered on screen, not on how it is marked up. bottom line is that for users these screen readers using strong as an indication of a required field won't be of any help. On 25/02/2008, tee [EMAIL PROTECTED] wrote: I have this question about strong element being more semantical and accessible for required field in the web form and like to hear your opinion. I came to the conclusion after conducting my little user testing - it first started with an intention of spam and error monitoring over the form script I use, I then learned that despite the indication that asterisk is marked as required field, many people who took time to submit the forms on clients' sites still missed the *. Because I use no JS validation for the form, I decided to bold the required field using strong element for two new sites. It seems working as the bold texts caught people attention and I received no errors email notification on missing to enter requried fields. The result also gave me a though on how screen readers treat the strong element and that it's indeed more accessible and semantically correct. Working on a site, and thanks to Matt Fellows and his futher assistance, I implemented his JS form validation script to the web form. Using asterik to indicate the required field no longer is an issue with JS validation, however I decided to stick with the strong element. Much work had put into it to modify the code and css, but client came back to me to want the '*' over the strong because it's a conventional practice. Really want to stick with the strong element for the reason above, however I am also doubting my conclusion that it's more accessible for screen readers as I never tested on one. Before I try to convince client the strong element is better approach, I would love to hear your opinion. Thank you! tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Article: Vocalize Firefox (text-to-speech extensions for Firefox)
To get an idea of how screen readers vocalise content (it also many other features) I would recommend trying adesigner (http://www.alphaworks.ibm.com/tech/adesigner) On 06/12/2007, Jixor - Stephen I [EMAIL PROTECTED] wrote: That said how would it compare for a developer that is making an effort to correctly mark up their html just to get an impression of how it would work for a screen reader user? Steve Green wrote: A year ago I started to evaluate FireVox 2.6 and had a dialog with Charles Chen, its creator. At that time there is no way I would describe it as full-fledged screen reader as it had many shortcomings. I got the impression it was really just a hobby project, and Charles said he had pretty much abandoned it in order to work on more interesting stuff. I see it is now up to version 3.4 so it will be interesting to see how it has progressed. It was certainly usable, but it bears no comparison with a professional screen reader like JAWS, which is a far superior product. OK, it should be for $1500 but people should not think that they're getting a $1500 product for free when they install FireVox. It's more akin to products in the $200 price bracket. One example of the difference is in forms where label elements have not been used, and let's face it, that's 99% of all forms. JAWS applies heuristics to identify the text that is most likely to be the label, and associates it with the form control as if a label element had been used. 9 times out of 10 it gets it right. FireVox does not do this. Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Lo Sent: 05 December 2007 04:25 To: wsg@webstandardsgroup.org Subject: [WSG] Article: Vocalize Firefox (text-to-speech extensions for Firefox) I'm wondering if anyone has tried/tested the following potentially useful extensions and if so what their opinion was/is: Two recently released text-to-speech extensions can transform Firefox into a talking Web browser suitable for users with visual impairments -- and anyone else who can use a speech interface to the Web. Fire Vox is designed to be a full-fledged screen reader in a browser, usable for daily browsing even for unsighted users. CLiCk, Speak provides point-and-click screen reading, which can be helpful for partially-sighted users or sighted users who have written language difficulties (such as dyslexia). http://www.linux.com/feature/122197 Nick *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Article: Vocalize Firefox (text-to-speech extensions for Firefox)
Firevox also implemts much of WAI-ARIA, so it is useful for testing and demos of ARIA functionality. On 05/12/2007, Steve Green [EMAIL PROTECTED] wrote: A year ago I started to evaluate FireVox 2.6 and had a dialog with Charles Chen, its creator. At that time there is no way I would describe it as full-fledged screen reader as it had many shortcomings. I got the impression it was really just a hobby project, and Charles said he had pretty much abandoned it in order to work on more interesting stuff. I see it is now up to version 3.4 so it will be interesting to see how it has progressed. It was certainly usable, but it bears no comparison with a professional screen reader like JAWS, which is a far superior product. OK, it should be for $1500 but people should not think that they're getting a $1500 product for free when they install FireVox. It's more akin to products in the $200 price bracket. One example of the difference is in forms where label elements have not been used, and let's face it, that's 99% of all forms. JAWS applies heuristics to identify the text that is most likely to be the label, and associates it with the form control as if a label element had been used. 9 times out of 10 it gets it right. FireVox does not do this. Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Lo Sent: 05 December 2007 04:25 To: wsg@webstandardsgroup.org Subject: [WSG] Article: Vocalize Firefox (text-to-speech extensions for Firefox) I'm wondering if anyone has tried/tested the following potentially useful extensions and if so what their opinion was/is: Two recently released text-to-speech extensions can transform Firefox into a talking Web browser suitable for users with visual impairments -- and anyone else who can use a speech interface to the Web. Fire Vox is designed to be a full-fledged screen reader in a browser, usable for daily browsing even for unsighted users. CLiCk, Speak provides point-and-click screen reading, which can be helpful for partially-sighted users or sighted users who have written language difficulties (such as dyslexia). http://www.linux.com/feature/122197 Nick *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Article: Vocalize Firefox (text-to-speech extensions for Firefox)
Firevox also implemts much of WAI-ARIA, so it is useful for testing and demos of ARIA functionality. On 05/12/2007, Steve Green [EMAIL PROTECTED] wrote: A year ago I started to evaluate FireVox 2.6 and had a dialog with Charles Chen, its creator. At that time there is no way I would describe it as full-fledged screen reader as it had many shortcomings. I got the impression it was really just a hobby project, and Charles said he had pretty much abandoned it in order to work on more interesting stuff. I see it is now up to version 3.4 so it will be interesting to see how it has progressed. It was certainly usable, but it bears no comparison with a professional screen reader like JAWS, which is a far superior product. OK, it should be for $1500 but people should not think that they're getting a $1500 product for free when they install FireVox. It's more akin to products in the $200 price bracket. One example of the difference is in forms where label elements have not been used, and let's face it, that's 99% of all forms. JAWS applies heuristics to identify the text that is most likely to be the label, and associates it with the form control as if a label element had been used. 9 times out of 10 it gets it right. FireVox does not do this. Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Lo Sent: 05 December 2007 04:25 To: wsg@webstandardsgroup.org Subject: [WSG] Article: Vocalize Firefox (text-to-speech extensions for Firefox) I'm wondering if anyone has tried/tested the following potentially useful extensions and if so what their opinion was/is: Two recently released text-to-speech extensions can transform Firefox into a talking Web browser suitable for users with visual impairments -- and anyone else who can use a speech interface to the Web. Fire Vox is designed to be a full-fledged screen reader in a browser, usable for daily browsing even for unsighted users. CLiCk, Speak provides point-and-click screen reading, which can be helpful for partially-sighted users or sighted users who have written language difficulties (such as dyslexia). http://www.linux.com/feature/122197 Nick *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] accessible calendars? [SEC=UNCLASSIFIED]
Hi Leon, I am not sure what you meant by calendat application, but have a look at: Unobtrusive Date-Picker http://www.frequency-decoder.com/2006/10/02/unobtrusive-date-picker-widgit-update/ On 26/10/2007, Leon Wild [EMAIL PROTECTED] wrote: Hi all, Can anyone recommend a standards compliant, calendar application for a website? Cheers, Leon Leon Wild :: Web Manager :: Human Rights Commission :: ph +61 2 9284 9698 :: email [EMAIL PROTECTED] WARNING: The information contained in this email may be confidential. If you are not the intended recipient, any use or copying of any part of this information is unauthorised. If you have received this email in error, we apologise for any inconvenience and request that you notify the sender immediately and delete all copies of this email, together with any attachments. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Title attribute and screen readers
Hi Rebecca, announcing of title attribute values on links is not a default screen reader behaviour and for JAWS the announcing of the title attribute is an OR choice (read title or link content) so effectively the title attribute conentt for links is unavailable to most screen reader users. On 24/10/2007, Rebecca Cox [EMAIL PROTECTED] wrote: Hi all, I'm looking for up to date info on title attribute behaviour screen readers, especially where used on site global navigation. As an example, http://www.e.govt.nz uses fairly long title attributes for the main navigation links, and this repeats throughout the site (i.e., not just on the home page). For example, About e-govt in the left nav has: a href=http://www.e.govt.nz/about-egovt; span title=E-government enables people to use digital technology to find and use New Zealand government information and services.About e-govt/span /a Main thing I'm wondering is, with a screen reader, if reading out of title attribute text is enabled, are you forced to listen to the full title text each time it is encountered, or can you skip over it? In the above example, the title attribute is applied to a span nested inside the link, rather than to the link itself - would this make any difference? (Comparing this to phone customer support or online banking services - some force you to listen to the full spiel about each option before you can do anything, others don't - they allow you to activate your menu choice without listening to the full explanatory message.) Or are most screen reader users not using title attribute text - some time ago there was an article published suggesting most had it disabled... Would appreciate any information anyone might have on how this works! Cheers, Rebecca *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Title attribute and screen readers
Hi Frank, I would suggest that if you want the information available to screen reader users or keyboard only users (as title attribute content is not available to keyboard users), then don't place it in the title attribute on links. On 24/10/2007, Frank Palinkas [EMAIL PROTECTED] wrote: Hi Steve, If I may follow on to Rebecca's query and based your reply, is it then considered good practice (in general) _not_ to add title attributes and values to hyperlinks? Kind regards, Frank -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Faulkner Sent: Wednesday, 24 October, 2007 11:20 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Title attribute and screen readers Hi Rebecca, announcing of title attribute values on links is not a default screen reader behaviour and for JAWS the announcing of the title attribute is an OR choice (read title or link content) so effectively the title attribute conentt for links is unavailable to most screen reader users. On 24/10/2007, Rebecca Cox [EMAIL PROTECTED] wrote: Hi all, I'm looking for up to date info on title attribute behaviour screen readers, especially where used on site global navigation. As an example, http://www.e.govt.nz uses fairly long title attributes for the main navigation links, and this repeats throughout the site (i.e., not just on the home page). For example, About e-govt in the left nav has: a href=http://www.e.govt.nz/about-egovt; span title=E-government enables people to use digital technology to find and use New Zealand government information and services.About e-govt/span /a Main thing I'm wondering is, with a screen reader, if reading out of title attribute text is enabled, are you forced to listen to the full title text each time it is encountered, or can you skip over it? In the above example, the title attribute is applied to a span nested inside the link, rather than to the link itself - would this make any difference? (Comparing this to phone customer support or online banking services - some force you to listen to the full spiel about each option before you can do anything, others don't - they allow you to activate your menu choice without listening to the full explanatory message.) Or are most screen reader users not using title attribute text - some time ago there was an article published suggesting most had it disabled... Would appreciate any information anyone might have on how this works! Cheers, Rebecca *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Title attribute and screen readers
Also, sighted keyboard users will never see them either. If they use IE. although users of firefox can access the title attribute via the keyboard, there is no way for them to know that there is a title there to be queried, unlike mouse users who are presented with the title as a tooltp when they mouse over a link (or any other element). So effectively they will never be seen. Also there is no method that I know of to access the title attribute content in other browser (Opera etc) On 24/10/2007, Chris Price [EMAIL PROTECTED] wrote: Patrick H. Lauke wrote: Also, sighted keyboard users will never see them either. If they use IE. Kind Regards -- Chris Price Choctaw [EMAIL PROTECTED] http://www.choctaw.co.uk Tel. 01524 825 245 Mob. 0777 451 4488 Beauty is in the Eye of the Beholder while Excellence is in the Hand of the Professional ~~~ -+- Sent on behalf of Choctaw Media Ltd -+- ~~~ Choctaw Media Limited is a company registered in England and Wales with company number 04627649 Registered Office: Lonsdale Partners, Priory Close, St Mary's Gate, Lancaster LA1 1XB United Kingdom *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Investigating the proposed alt attribute recommendations in HTML 5
If the developers of flickr.com or Photobucket were to implement the recommendations regarding the omission of the alt attribute within the current HTML 5 draft what are the potential effects upon the accessibility of the sites for users of assistive technology such as screen readers? Investigating the proposed alt attribute recommendations in HTML 5 - http://www.paciellogroup.com/resources/articles/altinhtml5.html -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Investigating the proposed alt attribute recommendations in HTML 5
From Laura Carlson: The HTML WG charter does say: The HTML Working Group will cooperate with the Web Accessibility Initiative to ensure that the deliverables will satisfy accessibility requirements. Coordination with WAI will be primarily conducted through the Protocol and Formats Working Group, but direct coordination with other WAI groups, such as Web Content Accessibility Guidelines Working Group and User Agent Accessibility Guidelines Working Group, will also be done when appropriate. http://www.w3.org/2007/03/HTML-WG-charter.html#wai On 30/08/2007, Alastair Campbell [EMAIL PROTECTED] wrote: Does the HTML working group have to take into account accessibility guidelines? What I mean is, does it have to make alt mandatory because WCAG (any version) does? -Alastair *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Does the HTML working group have to take into account accessibility guidelines?
alastair campbell wrote: Does the HTML working group have to take into account accessibility guidelines? What I mean is, does it have to make alt mandatory because WCAG (any version) does? I asked around and got some answers that may answer your question: Charles McCathieNevile wrote: The answer to the question is that it has to satisfy WAI that its approach to accessibility is reasonable and practical. As a sometime WAI member I will be arguing that WAI is unlikely to accept anything that is a step backwards from alt, and while it is possible to improve it the volume of existing content and of existing guidance to use it means that it must be supported even if there is a better approach proposed to replace it in the future (like the case of img and object...) Laura Carlson wrote: The charter does say: The HTML Working Group will cooperate with the Web Accessibility Initiative to ensure that the deliverables will satisfy accessibility requirements. Coordination with WAI will be primarily conducted through the Protocol and Formats Working Group, but direct coordination with other WAI groups, such as Web Content Accessibility Guidelines Working Group and User Agent Accessibility Guidelines Working Group, will also be done when appropriate. http://www.w3.org/2007/03/HTML-WG-charter.html#wai *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Colour Contrast Analyser for MAC now available
Cedric Trevisan of TPG (Europe) and WAT-C has developed a version of the Colour Contrast Analyser for the Mac OS X 10.4.6 or later [http://www.paciellogroup.com/resources/contrast-analyser.html#macdownload ] It can be used to check for conformance with the WCAG 1 2 checkpoints relating to contrast issues. using the colour brightness/colour difference formulas and the contrast ratio algorithm. -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] The Web Accessibility Toolbar 2.0 beta is now available.
The Web Accessibility Toolbar 2.0 beta is now available. [http://www.paciellogroup.com/resources/wat-ie-about.html] Feedback welcome. Whats new version 2.0 Compatible with IE 7 and Vista All functions (except third party) no longer rely upon external scripts. Most functions now work when javascript is disabled Most functions (where applicable) work across frames iframes HTML validator - checks files from a local server or folder. New functionality: log window: when the log text box is opened, any messages that a function provides are written to the log window (instead of an alert box). Text can also be entered into the log text box. this info can be saved to a text file. Open in Firefox and opera buttons: opens the current page in firefox or Opera (if installed) HTML validation quick check: returns summary check results from the W3C validator. frames list: provides access to any framed documents generated source highlighter: generated source views with elements highlighted. Focus highlighter Functional Accessibility Evaluator plus others and upgrades to existing functions -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] contrast analyser 2.0 released
The Contrast Analyser 2.0 http://www.paciellogroup.com/resources/contrast-analyser.html This version implements the updated contrast algorithm and provides results based on Guideline 1.4 of the May 2007 working draft of WCAG 2.0 -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Re: contrast analyser 2.0 released
Please note: there was an issue with some text labels and the results for color deficits, this has now been resolved, please take the time to download another copy of the software if you have downloaded it in the first hour of its release. On 18/05/07, Steven Faulkner [EMAIL PROTECTED] wrote: The Contrast Analyser 2.0 http://www.paciellogroup.com/resources/contrast-analyser.html This version implements the updated contrast algorithm and provides results based on Guideline 1.4 of the May 2007 working draft of WCAG 2.0 -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Screen Readers and JavaScript
Screen Readers and JavaScript - presentation at CSUN 2007 http://www.paciellogroup.com/CSUN/csun-javascript-presentation.html -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Colour Contrast Analyser - Firefox Extension 0.2
Gez Lemon, of Juicy Studio has released a Colour Contrast Analyser - Firefox Extension 0.2 [http://juicystudio.com/article/colour-contrast-analyser-firefox-extension.php] The Colour Contrast Analyser Firefox extension lists colour combinations used in the document in a table that summarises the foreground colour, background colour, luminosity contrast ratio, and the colour difference and brightness difference used in the algorithm suggested in the 26th of April 2000 working draft for Accessibility Evaluation and Repair Tools (AERT). Each element is also listed with its parent elements, and class and id attribute values when specified to make it easier to locate the elements. with regards Steven Faulkner Web Accessibility Consultant vision australia - information library service 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] www.accessibleinfo.org.au | www.wat-c.org Download the Web Accessibility Toolbar [http://www.visionaustralia.org.au/ais/toolbar/] ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Web Accessibility Workshops 28 29 November 2005 - Canberra
Web Accessibility Workshops 28 29 November 2005 - Canberra These one-day workshops introduce accessibility issues in terms of Australian policy contexts and internationally recognised requirements. For further details visit: http://www.visionaustralia.org.au/info.aspx?page=684 Writing for the Web Workshop 1 December 2005 - Sydney This practical workshop focuses on enhancing the usability and accessibility of your web content and will teach you how to communicate effectively with your readers. For further details visit: http://www.visionaustralia.org.au/info.aspx?page=685 Tania Conlan Research and Administration Officer Vision Australia - Accessible Information Solutions PO Box 860, Hawthorn VIC 3122 454 Glenferrie Road, Kooyong VIC 3144 Ph: (03) 9864 9249 Fax: (03) 9864 9370 [EMAIL PROTECTED] www.accessibleinfo.org.au www.visionaustralia.org.au Vision Australia was formed through the merger of Royal Blind Society, the Royal Victorian Institute for the Blind, Vision Australia Foundation and the National Information and Library Service. ABN: 67 108 391 831. ACN: 108 391 831 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] screenshot of title display in safari - screenshots received.
Thanks to those who have emailed me with screenshots! with regards Steven Faulkner Web Accessibility Consultant vision australia - information library service 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] Download the Web Accessibility Toolbar [http://www.nils.org.au/ais/web/resources/toolbar/] |-+-- | | [EMAIL PROTECTED]| | | alia.org.au| | | Sent by: | | | [EMAIL PROTECTED]| | | rg | | | | | | | | | 20/09/2005 03:23 PM| | | Please respond to wsg | | | | |-+-- ---| | | | To: wsg@webstandardsgroup.org | | cc: | | Subject: [WSG] screenshot of title display in safari | ---| Hi can someone using Safari have a look at this page [http://www.sf.id.au/we05/title.html] and move the mouse over the text title attribute and do a screenshot of the page for me? I want to see how and if the title attribute content on the containing (P element) is displayed. I believe that Safari shows title attribute content in the status bar and would like to have an image example of this. with regards Steven Faulkner Web Accessibility Consultant vision australia - information library service 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] Download the Web Accessibility Toolbar [http://www.nils.org.au/ais/web/resources/toolbar/] ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] screenshot of title display in safari
Hi can someone using Safari have a look at this page [http://www.sf.id.au/we05/title.html] and move the mouse over the text title attribute and do a screenshot of the page for me? I want to see how and if the title attribute content on the containing (P element) is displayed. I believe that Safari shows title attribute content in the status bar and would like to have an image example of this. with regards Steven Faulkner Web Accessibility Consultant vision australia - information library service 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] Download the Web Accessibility Toolbar [http://www.nils.org.au/ais/web/resources/toolbar/] ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Press release: Official launch of the Web Accessibility Tool Consortium (WAT-C, www.wat-c.org]
Leading Accessibility Organisations Launch International Development Consortium Australia, Europe, Japan and United States form WAT-C to create real time web and software accessibility analysis tools via GPL. - Thursday, September 15, 2005 Melbourne, Australia. Today organisations representing four continents announced the official launch of the Web Accessibility Tool Consortium (WAT-C, www.wat-c.org). The new consortium is developing a series of browser-based web accessibility analysis tools under a general public license agreement. By harnessing the passion, knowledge, and creativity of this international group of web accessibility practitioners, stated Steven Faulkner WAT-C founder, We have a unique opportunity to provide tools to promote the understanding and development of an accessible web. WAT-C is a collaboration of some of the world's leading accessibility practitioners. These developers of free web accessibility testing software services include: Accessible Information Solutions [Australia] Infoaxia [Japan] Juicy Studio [UK] The Paciello Group [USA] Wrong HTML [Japan] The consortium will promote and pursue software development goals including: Free web accessibility testing software Enhanced development of existing web accessibility testing tools The internationalization of web accessibility testing software There is an international movement to harmonise divergent web accessibility guidelines, such as WCAG by the W3C, Section 508 in the US, and JIS in Japan, Makoto Ueki of Infoaxia and co-founder of WAT-C. We want to support this process through international collaboration in the development of tools to help all web developers produce accessible websites. WAT-C will shortly release an updated version of the Web Accessibility Toolbar for Internet Explorer, and recently announced the release of a Colour Contrast Analyser utility. Toolbar versions for Mozilla/Firefox and Opera are in development. Contacts Steven Faulkner Accessible Information Solutions [EMAIL PROTECTED] www.accessibleinfo.org.au Makoto Ueki Infoaxia, Inc. [EMAIL PROTECTED] www.infoaxia.co.jp Mike Paciello The Paciello Group [EMAIL PROTECTED] www.paciellogroup.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] web accessibility toolbar
Hi designer As the person who developed the web accessibility toolbar (WAT) I do not recommend the use of its magnify function as a way to overcome the pixel issue in internet explorer. This function is simply intended to give an idea to designers/developers of how some people may view a web page. it does not work across pages, so a user would have to reactivate the function each time they opened a page. As a web accessibility consultant I reccommend the use of em's or % over pixels, but if a designer decides they must use pixels to set font-size users of internet explorer can override this by using the IE menu Internet options accessibility ignore font sizes specified on web pages this allows users to change the text size via the IE menu view text size function. This is a rather convoluted process and many users are not aware of it, so give clear instructions on its use if you choose to go down this path. PS: both the accessibility dialog and the text size functions are also available through the WAT IE options menu. they have been put there to make it easier for designers/developers to test their pages (in IE) to ensure that their designs don't break when settings are changed by the user. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] Get the Web Accessibility Toolbar [http://www.nils.org.au/ais/web/resources/toolbar/] |-+--- | | designer| | | [EMAIL PROTECTED]| | | rnet.co.uk | | | Sent by:| | | [EMAIL PROTECTED]| | | p.org | | | | | | | | | 20/08/2005 10:34 PM | | | Please respond to wsg | | | | |-+--- ---| | | | To: webstandards group [EMAIL PROTECTED] | | cc: | | Subject: [WSG] web accessibility toolbar | ---| Good afternoon (or whatever), Does the web accessibility toolbar let me off the hook as far as using pixels for text sizing in IE is concerned? I have recently got the excellent WAT from http://www.nils.org.au/ais/ and it has an excellent zoom facility, like opera. (A great, and very educational tool anyway). I ask the question partly tongue-in-cheek, but it does make me wonder if tools such as this should be the butt of responsibility? I just wondered, as it does seem to put the pixel argument into a different perspective. No rants please: this is intended as an intelligent question, expecting and wanting the same type of response. Thanks, Bob ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] tabbing through links
Also See Keyboard Navigation and Internet Explorer : http://juicystudio.com/article/ie-keyboard-navigation.php with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. |-+- | | Andy Kirkwood | | | | Motive| | | [EMAIL PROTECTED]| | || | | Sent by: | | | [EMAIL PROTECTED]| | | dsgroup.org | | | | | | | | | 22/08/2005 10:59 | | | AM| | | Please respond to | | | wsg | | | | |-+- ---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: [WSG] tabbing through links | ---| Watch out for IE keyboard navigation bug. Depending on your method for setting the destination anchor, things can go a little awry. For details, see: http://www.motive.co.nz/glossary/anchor.php Cheers, -- Andy Kirkwood | Creative Director Motive | web.design.integrity http://www.motive.co.nz ph: (04) 3 800 800 fx: (04) 970 9693 mob: 021 369 693 93 Rintoul St, Newtown PO Box 7150, Wellington South, New Zealand ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Online GIF flicker tesing tool
An english language version of an online tool (developed by by Renzo Giust) for checking flicker rates in animated gifs. is now available. http://www.webaccessibile.org/test/check.aspx best regards stevef ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] detecting css display properties
I have been trying to detect ,using javascript , the css display property (set via an external @import style sheet) of an element Example page: http://www.jimthatcher.com/site_resources.htm has a LI (class=skip with CSS display:none. but when i try to find this via the (IE DOM) i cannot locate it. any ideas? with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Online screen viewer
Is there free online screen reader like Delorie Lynx Viewer available that allows to test sites? this one does: http://www.yellowpipe.com/yis/tools/lynx/lynx_viewer.php with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. |-+- | | tee | | | [EMAIL PROTECTED]| | | t| | | Sent by: | | | [EMAIL PROTECTED]| | | dsgroup.org | | | | | | | | | 16/06/2005 01:16 | | | AM| | | Please respond to | | | wsg | | | | |-+- ---| | | | To: wsg@webstandardsgroup.org | | cc: | | Subject: [WSG] Online screen viewer | ---| Is there free online screen reader like Delorie Lynx Viewer available that allows to test sites? Delorie Lynx Viewer required user to have a delorie.html file in the server, this is only good for my own project testing but sometimes I need to help friends to test their sites. Regards, Tee ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Accessible form test
Hi Erwin 1. i would ditch the accesskeys: see these articles for why: http://wats.ca/articles/accesskeys/19 http://wats.ca/articles/accesskeyconflicts/37 2. use javascript to clear the comments textarea on focus (if it contains the default text). 3. mark up abbreviations and acronyms abbr title=numberNr/abbr FYI here is an example read out of the form using IBM homepage reader note: using spans to style characters within words causes the word to be read out incorrectly example departure becomes de- e -parture or the read out for 'nr. persons' is (note repetition of s ) 'Nr. of person Press Alt + Shift + ss'(i think this is a bug in homepage reader) Name Press Alt + Shift + m [Text.] Surname Press Alt + Shift + s [Text.] E-mai Press Alt + Shift + ll [Text.] Comments Press Alt + Shift + o [TextArea.] Enquiry Details Arrival Date Press Alt + Shift + d (Start of select menu with 32 items.) [Collapsed.] Choose day [Selected.] (End of select menu.) (Start of select menu with 13 items.) [Collapsed.] Choose month [Selected.] (End of select menu.) (Start of select menu with 4 items.) [Collapsed.] choose year [Selected.] (End of select menu.) Departure Date Press Alt + Shift + p (Start of select menu with 32 items.) [Collapsed.] Choose day [Selected.] (End of select menu.) (Start of select menu with 13 items.) [Collapsed.] Choose month [Selected.] (End of select menu.) (Start of select menu with 4 items.) [Collapsed.] choose year [Selected.] (End of select menu.) Nights Press Alt + Shift + i [Text.] Room Press Alt + Shift + r (Start of select menu with 8 items.) [Collapsed.] Choose one [Selected.] (End of select menu.) Nr. of person Press Alt + Shift + ss [Text.] How did you hear about Read's? Press Alt + Shift + y [Text.] Additional enquiries or comments Press Alt + Shift + q [TextArea: If interested in any particular package...] [Send: Submit button.] [Clear: Reset button.] (End of form 2.) with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. |-+- | | Erwin Heiser | | | [EMAIL PROTECTED]| | | Sent by: | | | [EMAIL PROTECTED]| | | dsgroup.org | | | | | | | | | 10/06/2005 03:27 | | | AM| | | Please respond to | | | wsg | | | | |-+- ---| | | | To: wsg@webstandardsgroup.org | | cc: | | Subject: [WSG] Accessible form test | ---| Hi all, I'm sorry for sending this againg but the link for the new form was wrong, that's what happens when you've been staring at a screen for too long... I¹m pretty new to marking up forms so I decided to ³get it right² right from the start. I¹ve recoded a contact form they are using on a website I¹m working on. The old form (the one currently in use) is here: http://www.pixelsandtext.be/tests/oldform.html The new form is here: http://www.pixelsandtext.be/tests/newform.html Both forms validate to their respective DTD. The old one is marked-up using tables, the new one uses a definition list and a few CSS-rules for the layout. I've read Joe Clarks book building accessible websites and applied most of the stuff in the Forms chapter. (Funny thing, even when adding all the CSS rules and the accessiblity extra's to the HTML the file size is roughly the same as the old form) Would some of the WSG accessibility gurus please have a look at this form? I'd welcome any comment and/or suggestions... Thanks in advance, Erwin Heiser ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help
[WSG] drempelvrij.nl toolbar - web accessibility testing tool
The Bartiméus Accessibility Foundation (http://www.accessibility.nl/) have released a free a web accessibility testing tool http://www.drempelvrij.nl/toolbar/index.html (internet explorer add-on) that is intended for use in conjunction with an online step by step testing procedure that they have developed. Currently it available in Dutch, I believe they also plan to release an English language version. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] why doesn't this validate with w3c.org and what to do about it
checked it and w3c css validator didn't complain?
once i changed test-align to text-align
with regards
Steven Faulkner
Web Accessibility Consultant
National Information Library Service (NILS)
454 Glenferrie Road
Kooyong Victoria 3144
Phone: (613) 9864 9281
Fax: (613) 9864 9210
Email: [EMAIL PROTECTED]
National Information Library Service
A subsidiary of RBS.RVIB.VAF Ltd.
|-+
| | Bruce Gilbert|
| | [EMAIL PROTECTED]|
| | om |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | group.org|
| ||
| ||
| | 27/05/2005 12:25 |
| | PM |
| | Please respond to|
| | wsg |
| ||
|-+
---|
|
|
| To: wsg@webstandardsgroup.org
|
| cc:
|
| Subject: [WSG] why doesn't this validate with w3c.org and what to do
about it |
---|
I have some comments within my CSS to let me or anyone else know what
is controlling what
eg:
/*aligns list in middle of page*/
p.middle{test-align:center}
validation doesn't like this.is there a fix? or should I just ignore???
TIA
--
::Bruce::
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
[WSG] help with Linux version of the colour contrast analyser 1.0
We have had a number of requests for a linux version of the colour contrast analyser [CCA], a freeware tool,(http://www.nils.org.au/ais/web/resources/contrast_analyser/index.html), but do not have the skills to do this ourselves, is anybody who does have the skills ,or knows someone, interested? if so please email me... The CCA is written in delphi. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Ireland web accessibility law?
This may be helpful, Irish National Disability Authority IT Accessibility Guidelines Legislation and Policy http://accessit.nda.ie/policy_and_legislation.html with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. |-+- | | Andrey Stefanenko | | | andrey.stefanenko| | | @it.net.ua | | | Sent by: | | | [EMAIL PROTECTED]| | | roup.org | | | | | | | | | 21/04/2005 10:07 | | | PM| | | Please respond to | | | wsg | | | | |-+- ---| | | | To: wsg@webstandardsgroup.org | | cc: | | Subject: [WSG] Ireland web accessibility law? | ---| Dear Sirs. Please give me some advice on Ireland web accessibility guidelines. Is it exist? Some links would be fine. Thanx. Andrey Stefanenko ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Please review http://www.mad4f1.com
A few comments: - the 'driver standings' and 'team standings' are data tables and need to be marked up as tables using the appropriate elements -appears to contain no semantic structure elements (e.g no heading or list markup) -invalid html -no alt attributes on IMG elements with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] colour contrast analyser
Andreas Boehmer wrote: But it seems you cannot manually enter HEX codes? you can now! with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. |-+ | | Andreas Boehmer| | | [EMAIL PROTECTED]| | | dia.com.au | | | Sent by: | | | [EMAIL PROTECTED]| | | p.org| | || | || | | 04/02/2005 04:45 PM | | | Please respond to wsg| | || |-+ ---| | | | To: wsg@webstandardsgroup.org | | cc: | | Subject: Re: [WSG] colour contrast analyser | ---| a colour contrast analyser, useful for checking foreground background colour combinations is now available. (http://www.nils.org.au/ais/web/resources/contrast_analyser/index.html) I like it. The colour picker is useful. But it seems you cannot manually enter HEX codes? ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] colour contrast analyser
a colour contrast analyser, useful for checking foreground background colour combinations is now available. (http://www.nils.org.au/ais/web/resources/contrast_analyser/index.html) with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] colour contrast analyser
Felix I know about the juicy studio tool i use it on a daily basis, there is also one from HP at http://h10014.www1.hp.com/accessibility/color_tool.html the reason why the exe was developed was to allow colour sampling which cannot be done using an online application. which saves me time trying to find the values of colours used on a page. It also gives results for various types of colour blindness which currently no online tool does. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. |-+ | | Felix Miata | | | [EMAIL PROTECTED] | | | Sent by: | | | [EMAIL PROTECTED]| | | group.org| | || | || | | 04/02/2005 11:01 | | | AM | | | Please respond to| | | wsg | | || |-+ ---| | | | To: wsg@webstandardsgroup.org | | cc: | | Subject: Re: [WSG] colour contrast analyser | ---| [EMAIL PROTECTED] wrote: a colour contrast analyser, useful for checking foreground background colour combinations is now available. (http://www.nils.org.au/ais/web/resources/contrast_analyser/index.html) This one doesn't need to be downloaded: http://www.juicystudio.com/services/colourcontrast.asp -- He who believes in me will live, even though he dies; and whoever lives and believes in me will never die. John 11:25 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/auth/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] 2005 Web Accessibility Workshops in Melbourne and Canberra
Web Accessibility Workshops in Melbourne and Canberra The National Information and Library Service (NILS) is running Web and Online Accessibility Workshops in Melbourne on 10 February and in Canberra on 16 and 17 February 2005. These workshops introduce accessibility issues in terms of Australian policy contexts and internationally recognised requirements. (NILS is a subsidiary of RBS.RVIB.VAF Ltd, formerly Royal Blind Society of NSW, Royal Victorian Institute for the Blind and Vision Australia Foundation). Details and registration forms are at: Melbourne - http://www.nils.org.au/ais/web/workshops/0502-melb.html Canberra - http://www.nils.org.au/ais/web/workshops/0505-canb.html These full-day workshops are targeted at web-development team leaders, corporate communications professionals, business managers, along with content authors, web programmers, designers and web contract managers. Tania Conlan Research and Administration Officer Accessible Information Solutions National Information and Library Service (NILS) A subsidiary of RBS.RVIB.VAF Ltd PO Box 860, Hawthorn VIC 3122 454 Glenferrie Road, Kooyong VIC 3144 Ph: (03) 9864 9249 Fax: (03) 9864 9370 [EMAIL PROTECTED] www.accessibleinfo.org.au with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] discussion at juicy studio: It's all in the MIME
I have been following this discussion (belatedly) It's all in the MIME http://www.juicystudio.com/all-in-the-mime.asp first paragraph: There have been a lot of articles recently about web standards; in particular, using XHTML and serving it as text/html. Personally, I'm not that bothered whether people serve XHTML as text/html, but think it's important that authors understand why this is wrong. Although I'm not bothered about content developers serving XHTML as text/html, I don't agree with people encouraging content developers to deliver XHTML as text/html. I wondered what other memebrs on the list thought about it and its implications? with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] discussion at juicy studio: It's all in the MIME
Thanks Susan, i spent a while trawling through old posts to find the thread , but found it instructive, The article Serving XHTML 1.0 (http://www.w3.org/International/articles/serving-xhtml/) helped clarify the subject for me. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Susan R. GrossmanTo: [EMAIL PROTECTED] susan.rgrossman@cc: gmail.com Subject: Re: [WSG] discussion at juicy studio: It's all in the MIME Sent by: [EMAIL PROTECTED] group.org 11/11/2004 09:57 AM Please respond to wsg On Thu, 11 Nov 2004 09:23:43 +1100, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I don't agree with people encouraging content developers to deliver XHTML as text/html. I wondered what other memebrs on the list thought about it and its implications? The problem from my point is the lack of support by IE and the hoops to jump through to serve otherwise, so I will continue using xhtml 1.0 strict served as text/html. There was a discussion of this on the list in early October , I believe the heading was is XHTML Dangerous that if you haven't read, you'd probably find interesting. -- Susan R. Grossman [EMAIL PROTECTED] ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] realtime CSS editor feedback pleased
Hi all I have been playing around with a bookmarklet script that I found last year by simon willison (edit styles [http://simon.incutio.com/archive/2003/06/03/bookmarkletsAndCSS]) the bookmarklet opens a new window in which you can write CSS statements that will be applied to the page. this script has been included in the web accessibility toolbar since it first incarnation, but i have always wanted to beef it up and include some new features, which i have now done,. It is available as a bookmarklet (for IE only at the moment), if you want a something similar for mozilla (go to slayeroffice http://slayeroffice.com/?c=/content/tools/style_tweak.html), but i intend to also incorporate it into the toolbar. the current features are: select lists: 1.all styles found in linked styles sheets (filters out stylesheets of media type print) 2.common elements 3. a sub-set CSS properties 4. common colours and buttons to insert some common names/characters/symbols used in CSS I would appreciate any feedback/comments about the functionality (I don't need feedback about the html as i know it is crap and needs to be fixed) It dosn't always work (sometimes access denied errors occur) it can be got here: http://web_accessibility_toolbar.blogspot.com/ with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] links with same names
So the ability to have the titles of links read out by screenreaders can be influenced by a setting? Relying on that setting is dangerous, don't you think? If the users have the reading of title attributes turned off, they won't hear any difference between the links. In fact, no users of screenreaders I have met so far could hear the title attributes. Good point Andreas, that is why i think that title attributes should be used with caution, if the text is important don't put it in the title attribute. plain text is best. Also remember that title attributes are device dependent, keyboard users cannot access them. A reasonable way around the issue is what they do on the age/sydney morning herald They have the heading as a link and and also a more link (both point to the full text of the article) Example: Police arrest possible sex attacker [11:30am] A Sydney rail commuter believes he saw someone resembling the identikit picture of a serial sex attacker. more it would be better if the more link had a title attribute, but the main point is that screen reader users have at least one clearly stated link to the article. In reference to to title content: I think it is better to have repeated words such as more or full text at the end of the title text rather than the beginning Examples: america has spoken - full text police arrest sex attacker -full text As when read out of context the important and defining information is frontloaded and allows easier identification of a particular link with a list of links. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Observing Users Who Work With Screen Readers
Interesting observational study of screen reader users (PDF) Guidelines for Accessible and Usable Web Sites: Observing Users Who Work With Screen Readers http://www.redish.net/content/papers/InteractionsPaperAuthorsVer.pdf with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Observing Users Who Work With Screen Readers
sorry forgot to say that it is a big file - 904kb Interesting observational study of screen reader users (PDF) with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. [EMAIL PROTECTED] alia.org.auTo: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED] Subject: [WSG] Observing Users Who Work With Screen Readers 01/11/2004 10:04 AM Please respond to wsg Interesting observational study of screen reader users (PDF) Guidelines for Accessible and Usable Web Sites: Observing Users Who Work With Screen Readers http://www.redish.net/content/papers/InteractionsPaperAuthorsVer.pdf with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Help with fieldset in a li
Firstly, am I using fieldset and legend in the correct semantic manner? Fieldset and legend elements are useful for explicitly identifying groups of form controls and assigning a label [legend] that relates to a group of controls. The example of their use you provided looks fine. Fieldsets can also be nested to identify sub-groups there are a few examples (with code) of their use here: http://www.nils.org.au/ais/web/resources/WSG_Oct_04/slide16.html with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Damian Sweeney [EMAIL PROTECTED]To: [EMAIL PROTECTED] .edu.au cc: Sent by: Subject: [WSG] Help with fieldset in a li [EMAIL PROTECTED] group.org 28/10/2004 01:25 PM Please respond to wsg Hi folks, I'm having some trouble with a series of questions in a questionnaire that I'd like to put in an ordered list. I'd like to use fieldset and legend to mark up each question, thereby separating them easily for people with assistive devices. However, I'd also like to keep the original look and feel pre-fieldset for 'unassisted' users. An example of the differences can be found at : http://members.iinet.net.au/~damianfs/sample.html Safari and Opera 7.5 on the Mac seem to handle this conversion well, but Firefox and IE tend to put the list marker under level of the legend. So, a couple of questions: Firstly, am I using fieldset and legend in the correct semantic manner? Secondly, if I am using it correctly, are there suggestions for fixing the display in Firefox and IE? Many thanks, Damian -- Damian Sweeney Instructional Designer, AIRport Project Equity, Language and Learning Programs University of Melbourne 723 Swanston St Parkville 3010 www.services.unimelb.edu.au/ellp/ ph 03 8344 9370, fax 03 9349 1039 This email and any attachments may contain personal information or information that is otherwise confidential or the subject of copyright. Any unauthorised use, disclosure or copying of any part of it is prohibited. The University does not warrant that this email or any attachments are free from viruses or defects. Please check any attachments for viruses and defects before opening them. If this email is received in error please delete it and notify us by return email or by phoning (03) 8344 9370. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Help with fieldset in a li
If no fieldset is used for the individual questions, how does a screen reader associate the question with the radio group? The label will differentiate the options, but what about the questions? Essentially it does not as their is no explicit structural association between the radio buttons and the question. while there is an implicit association [they are within the same container element/ they are contiguous visually and or in the reading order] for the most part the screen reader only knows what you tell it through the code. If fieldsets are nested, how does a screen reader handle the legends? Are they concatenated for each form control or is only the legend from the parent fieldset used? using JAWS 4.51 the legends are not concatenated. It sounds like a long legend is a bad idea - correct? I'd agree with this. In a page where there is only one form and one semantically linked set of form controls is a fieldset necessary/desirable? I think while desirable it is not necessary, unless you have a radio button or checkbox group. But why not use the fieldset element to structure the form instead of putting in a div or some other container? remeber the legend is optional. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Damian Sweeney [EMAIL PROTECTED]To: [EMAIL PROTECTED] .edu.au cc: Sent by: Subject: RE: [WSG] Help with fieldset in a li [EMAIL PROTECTED] group.org 29/10/2004 10:29 AM Please respond to wsg Thanks to Susan, Steven and Roger for the replies so far. A couple of questions for clarification: * If no fieldset is used for the individual questions, how does a screen reader associate the question with the radio group? The label will differentiate the options, but what about the questions? * It sounds like a long legend is a bad idea - correct? * In a page where there is only one form and one semantically linked set of form controls is a fieldset necessary/desirable? * If fieldsets are nested, how does a screen reader handle the legends? Are they concatenated for each form control or is only the legend from the parent fieldset used? Cheers, Damian One benefit of using fieldset and legend for screen reader users is that nearly all readers will read the legend before every input label within a fieldset. This can be very helpful with forms that require the same information within different sections of the form. For example, if you need put in name, phone number etc for a number of different people, the form input labels for each person will be the same - the layout of the form may make the different sections of the form obvious for visual users of the site, but the difference may not be obvious if you can't see. However, when you use fieldset and legend (with say a legend of purchaser for one person) then the reader will read the labels within this fieldset as purchaser name, purchaser phone number etc
RE: [WSG] Help with fieldset in a li
Hi Damian, I misunderstood what you meant when you wrote: In a page where there is only one form and one semantically linked set of form controls is a fieldset necessary/desirable? I didn't realize that you will still referring to your example, I thought you meant a simple form such as a text label + input + submit. I now understand and think that the use of a list in you form is appropriate. Also, I would have thought that modern screen readers would be able to group radio and checkbox groups based on name attributes. Is this not the case? from what i have read they do not group controls in this way. The info here: The HTML Forms Challenge [http://www.freedomscientific.com/HTML_challenge/files/forms_challenge.html] may be helpful for better understanding how a screen reader (JAWS) interacts with forms. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Damian Sweeney [EMAIL PROTECTED]To: [EMAIL PROTECTED] .edu.au cc: Sent by: Subject: RE: [WSG] Help with fieldset in a li [EMAIL PROTECTED] group.org 29/10/2004 12:20 PM Please respond to wsg In a page where there is only one form and one semantically linked set of form controls is a fieldset necessary/desirable? I think while desirable it is not necessary, unless you have a radio button or checkbox group. But why not use the fieldset element to structure the form instead of putting in a div or some other container? remeber the legend is optional. The main reason for using an ol is that this is a well-established convention for questionnaires and helps to structure the feedback for responses (which is often per question for my purposes). Also, I would have thought that modern screen readers would be able to group radio and checkbox groups based on name attributes. Is this not the case? Anyway, based on the responses I'm currently thinking I'll do things this way: http://members.iinet.net.au/~damianfs/sample2.html where the fieldset only encloses the radio buttons in a group. This fixes the positioning problem for the list items in Firefox and IE and seems semantically sound to me. No legends are used. Thanks again for the excellent responses, Damian -- Damian Sweeney Instructional Designer, AIRport Project Equity, Language and Learning Programs University of Melbourne 723 Swanston St Parkville 3010 www.services.unimelb.edu.au/ellp/ ph 03 8344 9370, fax 03 9349 1039 This email and any attachments may contain personal information or information that is otherwise confidential or the subject of copyright. Any unauthorised use, disclosure or copying of any part of it is prohibited. The University does not warrant that this email or any attachments are free from viruses or defects. Please check any attachments for viruses and defects before opening them. If this email is received in error please delete it and notify us by return email or by phoning (03) 8344 9370
Re: [WSG] that darn IE
I tried overflow and other things on both the
select and option elements, didn't seem to make any difference in IE
with regards
Steven Faulkner
Web Accessibility Consultant
National Information Library Service (NILS)
454 Glenferrie Road
Kooyong Victoria 3144
Phone: (613) 9864 9281
Fax: (613) 9864 9210
Email: [EMAIL PROTECTED]
National Information Library Service
A subsidiary of RBS.RVIB.VAF Ltd.
Jason Foss
[EMAIL PROTECTED]To: [EMAIL PROTECTED]
.comcc:
Sent by: Subject: Re: [WSG] that darn IE
[EMAIL PROTECTED]
group.org
28/10/2004 10:12
AM
Please respond to
wsg
I see what you mean. What happens if you set overflow to visible?
On Wed, 27 Oct 2004 15:55:33 -0700, Ted Drake
[EMAIL PROTECTED] wrote:
Here's a question that I haven't seen mentioned very often. probably
because form elements normally make the strong-willed folks quiver and
those of us that are a bit weaker throw up our arms and scream for our
mommies. So, here it is.
We have select boxes that show the entire word on firefox, if the word is
long, it stretches the dropdown to fit it.
In IE 6win, I don't know about the others at this time, the width of the
dropdown is constrained to a set width and overflow is hidden.
Here is the appropriate style
#leftquote select {width:48%; float:left;margin:2px 0; }
You can see the effect on this page http://www.csatravelprotection.com
look at the destination dropdown in the left side.
Thanks for any feedback
Ted
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
--
Jason Foss
Almost Anything Desktop Publishing
www.almost-anything.com.au
Windows Messenger: [EMAIL PROTECTED]
North Rockhampton, Queensland, Australia
We can do almost anything!
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] select as form label
This is what a user (accessing with IBM homepage reader) hears for your example form: (Start of select menu with 6 items.) work[Selected.] (End of select menu.) [Text.] doesn't appear very informative? with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] select as form label
Please do not associate multiple label elemnts with an input or multiple inputs with a single label element, both things will bugger up the associations for assistive tech (which is a major reason to use labels in the first place. ) in either case it is also not valid HTML. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Patrick H. Lauke To: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: .co.uk Subject: Re: [WSG] select as form label Sent by: [EMAIL PROTECTED] group.org 22/10/2004 11:44 AM Please respond to wsg Nick Lo wrote: Perhaps this is a case where it needs a nested label like... p label class=blank for=input_phone_1 label class=blank for=input_phone_1_typePhone type/label select name=input_phone_1_type id=input_phone_1_type option value=Please Select/option option value=workwork/option option value=homehome/option option value=faxfax/option option value=mobilemobile/option option value=otherother/option /select /label br / input type=text name=input_phone_1 id=input_phone_1 value= /p I think you may be wanting a FIELDSET here. And don't get hung up on wrapping the form element in its own label...I'd say it's perfectly ok NOT to do that, as long as FOR is properly tied to an ID. fieldset legendYour phone details/legend label class=blank for=input_phone_1_typePhone type/label select name=input_phone_1_type id=input_phone_1_type option value=Please Select/option option value=workwork/option option value=homehome/option option value=faxfax/option option value=mobilemobile/option option value=otherother/option /select br / label for=input_phone_1Phone number/label input type=text name=input_phone_1 id=input_phone_1 value= /fieldset Patrick H. Lauke _ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See
Re: [WSG] select as form label
Nick, i think your second solution is on the money. you wrote: However notice how the first is actually less laborious visually in terms of how we use desktop applications. You can hide the visual display of text labels if you want see: Invisible Form Prompts - http://www.juicystudio.com/invisible-form-prompts.asp for a discussion on methods. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Nick Lo [EMAIL PROTECTED]To: [EMAIL PROTECTED] ctive.com cc: Sent by: Subject: Re: [WSG] select as form label [EMAIL PROTECTED] group.org 22/10/2004 12:18 PM Please respond to wsg Wow, so many responses... must type fast...just knocked up what must be a better solution: http://www.trikeinteractive.com/form_example.html However notice how the first is actually less laborious visually in terms of how we use desktop applications. I'm thinking of for example OS X Address Book where you select the type of label for items then enter the data for the item. Of course it's really a balance of accessibility which is what I was trying to achieve. Steven your point... (Start of select menu with 6 items.) work[Selected.] (End of select menu.) [Text.] doesn't appear very informative? ...was actually partly because my example had a preselected element. However I'm glad now I accidentally left that in as you demonstrated exactly the reason for having the double label as used in my second solution, so very much appreciated. Darren: I like the idea...but have a look at it in firefox 1.0 and you'll see why it probably isn't a good idea. each time I click on the dropdown the input box gets the focus, thus proving v.difficult to actually select something from the dropdown. Hey, whaddya think I'm testing in? IE!! ;-) But yes that was another issue and funnily enough I have another problem that cropped up on that note: The CMS auto-generates forms for the users address(es). So in the users info you could have: General User Info Address 1 Address 2 etc... So if the user has 3 different addresses then it just replicates an address form 3 times and fills in each with the differing data. The problem is however that means there could be 3 lots of label class=blank for=input_phone_1 for example. Now with regards to the functionality of each separate form that makes no difference but it does however completely mess up the accessibility of the form as now that label refers to a field in 3 separate forms. Plenty to think about with all this! Thanks, Nick ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http
Re: [WSG] Solutions for testing in speech/text readers
Nick You can download a trial (30 days) copy of IBM homepage reader (web browser): [windows only] http://www-3.ibm.com/able/solution_offerings/hpr.html this is a good tool for getting a feel for how your pages are heard as it is simpler/easier to use than full blown screen readers such as JAWS. there is also a screen reader [outSPOKEN] for the mac which you can download a demo of, but i think it may have stopped being produced. http://www.synapseadaptive.com/alva/outspoken/outspoken_for_mac.htm with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Nick Lo [EMAIL PROTECTED]To: [EMAIL PROTECTED] ctive.com cc: Sent by: Subject: [WSG] Solutions for testing in speech/text readers [EMAIL PROTECTED] group.org 22/10/2004 12:31 PM Please respond to wsg Steven Faulkner just made me realise I've not yet seen or asked about set-ups for actually testing sites using speech/text readers. There are plenty of articles on browser testing but how would you go about setting up an environment for testing via speech/text readers. I use a Mac for development (OS X) but do have an old PC for browser testing. What are the solutions available? Thanks, Nick ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] select as form label
Hi TIA, in Nicks' example, which i was referring to, there were label elements inside other label elements wrapped around a form control, which is not valid, but thanks for pointing out about the explicit [for/id] association of multiple labels to a control, it hadn't occured to me before. I will do some testing with assitive tech to see how they handle multiple explicit labels. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Terrence Wood [EMAIL PROTECTED]To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: Re: [WSG] select as form label group.org 22/10/2004 01:23 PM Please respond to wsg Multiple labels for a single form control is valid HTML, however a single label for multiple form controls is not: http://www.w3.org/TR/html4/interact/forms.html#h-17.9 Steven, can you be more specific about the barriers multiple labels present? TIA ./tdw On 2004-10-22 2:56 PM, [EMAIL PROTECTED] wrote: Please do not associate multiple label elemnts with an input or multiple inputs with a single label element, both things will bugger up the associations for assistive tech (which is a major reason to use labels in the first place. ) in either case it is also not valid HTML. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Solutions for testing in speech/text readers
looks like its 40 minutes not 40 hours :-(( The Free Demo download of JAWS for Windows is a full featured product. It includes the synthesizer and everything you'll need to install and operate JAWS for 40 minutes. Please continue below to download and begin using it today. http://www.freedomscientific.com/fs_downloads/jaws_form.asp with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Jason Foss [EMAIL PROTECTED]To: [EMAIL PROTECTED] ing.com.aucc: Sent by: Subject: RE: [WSG] Solutions for testing in speech/text readers [EMAIL PROTECTED] oup.org 22/10/2004 02:03 PM Please respond to wsg Someone said once that there was a version of JAWS that would work for 40 hours or something like that - which is a LOT of testing. (40 hours as in 10 minutes here, 5 minutes there etc) Can anyone confirm that? ** Jason Foss Almost Anything Desktop Publishing www.almost-anything.com.au Telephone: (07) 4927 8033 Facsimile: (07) 4927 5312 Windows Messenger: [EMAIL PROTECTED] 9 Unmack Street, North Rockhampton, Queensland 4701 We can do almost anything! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, 22 October 2004 12:53 PM To: [EMAIL PROTECTED] Subject: Re: [WSG] Solutions for testing in speech/text readers Nick You can download a trial (30 days) copy of IBM homepage reader (web browser): [windows only] http://www-3.ibm.com/able/solution_offerings/hpr.html this is a good tool for getting a feel for how your pages are heard as it is simpler/easier to use than full blown screen readers such as JAWS. there is also a screen reader [outSPOKEN] for the mac which you can download a demo of, but i think it may have stopped being produced. http://www.synapseadaptive.com/alva/outspoken/outspoken_for_mac.htm with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Nick Lo [EMAIL PROTECTED]To: [EMAIL PROTECTED] ctive.com cc: Sent by: Subject: [WSG] Solutions for testing in speech/text readers [EMAIL PROTECTED] group.org 22/10/2004 12:31 PM Please respond to wsg Steven Faulkner just made me realise I've not yet seen or asked about set-ups for actually testing sites using speech/text readers. There are plenty of articles on browser testing but how would you go about setting up an environment
Re: [WSG] braille style sheet
Hi ted, This information from [http://www.codestyle.org/css/media/braille-BrowserSummary.shtml] may be helpful: Test case results for media types aural, braille, embossed, handheld, tty and tv are equivalent in all the mainstream browsers tested to date, none of which support these media. I haven't heard and cannot find any mention of any user agent that supports any media type other than screen, print and projector (opera only). with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Ted Drake [EMAIL PROTECTED]To: [EMAIL PROTECTED] ection.com cc: Sent by: Subject: [WSG] braille style sheet [EMAIL PROTECTED] p.org 07/10/2004 07:53 AM Please respond to wsg Has anyone on the list ever made a braille style sheet? What is involved? Are there any templates to suggest a standard braille sheet? What about Aural style sheets? I'm referring to the w3c media descriptors: http://www.w3.org/TR/REC-html40/types.html#h-6.13 braille Intended for braille tactile feedback devices. aural Intended for speech synthesizers. I'd love to offer a special style sheet for these if it is helpful. Ted ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Web and Online Accessibility Workshop, Canberra on 9 November 2004
The National Information and Library Service (NILS) is running a Web and Online Accessibility Workshop in Canberra on 9 November 2004. These workshops introduce accessibility issues in terms of Australian policy contexts and internationally recognised requirements. (NILS is a subsidiary of RBS.RVIB.VAF Ltd, formerly Royal Blind Society of NSW, Royal Victorian Institute for the Blind and Vision Australia Foundation). Details and registration forms are at: http://www.nils.org.au/ais/web/workshops/0911-canb.html This full-day workshop is targeted at web-development team leaders, corporate communications professionals, business managers, along with content authors, web programmers, designers and web contract managers. Tania Conlan Research and Administration Officer Accessible Information Solutions National Information and Library Service (NILS) A subsidiary of RBS.RVIB.VAF Ltd PO Box 860, Hawthorn VIC 3122 454 Glenferrie Road, Kooyong VIC 3144 Ph: (03) 9864 9249 Fax: (03) 9864 9370 [EMAIL PROTECTED] www.accessibleinfo.org.au with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] PDF to HTML conversions
Hi Chaudry, the PDF to html conversion tools i know of do not create accessible HTML, merely flaky html versions of the inaccessible PDF's your best bet is to mark up the content as HTML in the first place and offer the PDF as an alternative. I presume this is not what you wanted to hear... with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. CHAUDHRY, BhuvneshTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: v.auSubject: RE: [WSG] PDF to HTML conversions Sent by: [EMAIL PROTECTED] group.org 06/10/2004 08:51 AM Please respond to wsg There are a few tools and some suggestions to make PDF documents accessible but do you think there is one solution/process/tool which can actually convert a typical PDF file containing 2 column text flow a few graphs a couple of tables and a few images into a usable (not only accessible) document for the web? I still have a feeling that you can click on all these links to gather some information but at the end of the day you still don't have a solution. I just feel helpless. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kershaw, Lilania Sent: Tuesday, 5 October 2004 15:57 To: [EMAIL PROTECTED] Subject: RE: [WSG] PDF to HTML conversions OminPage is an OCR program. Haven't used it yet, but supposed to convert PDFs to any document type - word, excel, htm, etc, and retain formatting. pretty cheap too, under 1K Lilania Kershaw -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chris Bentley Sent: Tuesday, 5 October 2004 3:44 PM To: [EMAIL PROTECTED] Subject: Re: [WSG] PDF to HTML conversions Does anyone have ideas about the tools in market to convert PDF into HTML http://sourceforge.net/projects/pdftohtml/ cheers, Chris ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** * This e-mail message (along with any attachments) is intended only for the named addressee and could contain information that is confidential or privileged. If you are not the intended recipient you are notified that any dissemination, copying or use of any of the information
RE: [WSG] default place-holders for forms
Hi Andreas, not sure about the article, but we do recommend to our clients that they not use default place holding cahracters. from what i have read on the various accessibility lists, it appears that it is pretty safe to say that the checkpoint is no longer relevant. but i may be wrong.. some relevant list discussions Paul Bohman from webaim was saying its no longer needed back in 02' http://www.webaim.org/discussion/mail_message.php?id=2113 Updating specs and tools Re: place-holding characters in edit/text boxes: http://lists.w3.org/Archives/Public/w3c-wai-ig/2003JulSep/0399.html with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] default place-holders for forms
I would recommend leaving them out, from my experience with blind users,
the placeholders cause more trouble than they are worth. quite often users
are not aware of them and as a consequence they will fill in an input
without first clearing the place holder, which may well result in a form
validation error.
if you do use them it may be wise to include a javascript that clears the
default value when the input accepts focus
input type=text onfocus=if(this.value=='poot'){this.value=''}
value=poot/
PS. bobby is a piece of dumb software, don't rely upon it to tell you if
your site is:
a. accessible
b. conforms to the WCAG guidelines.
with regards
Steven Faulkner
Web Accessibility Consultant
National Information Library Service (NILS)
454 Glenferrie Road
Kooyong Victoria 3144
Phone: (613) 9864 9281
Fax: (613) 9864 9210
Email: [EMAIL PROTECTED]
National Information Library Service
A subsidiary of RBS.RVIB.VAF Ltd.
Andreas Boehmer
andreas_boehmer@To: [EMAIL PROTECTED]
gmx.net cc:
Sent by: Subject: [WSG] default place-holders
for forms
[EMAIL PROTECTED]
group.org
04/10/2004 02:06
PM
Please respond to
wsg
Hi guys,
I have got a website (www.jet.org.au) that passes Bobby almost with AAA,
with the exception of the default place holders. The reason I do not want
to
put them into the site is because every page has got a login form at the
top. With the default place-holders, the login form would look something
like this:
Username: Enter username
Password:
The password place-holder looks pretty useless and confusing to me. Most
users will plain wonder what that is supposed to do, it's not really
helpful
at all.
So I'd love to hear your opinions on this one? Shall I enter them just to
pass the accessibility tests, or leave them out for (in my opinion) better
usability? Being so close to AAA and not reaching it is frustrating.
Thanks!
Andreas.
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] Duplicate buttons
I have found that having multiple submit buttons can cause problems for screen reader users. A possible solution is to place the both submit buttons at the bottom of the form (within the code) and use CSS to position one of the buttons in the middle/or wherever (visually) of the form. As screenreaders read the page as it is written in the code (ignoring css positioning) a screen reader user will not encounter the submit button(s) until the end of the form. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Taco Fleur [EMAIL PROTECTED]To: [EMAIL PROTECTED] net.au cc: Sent by: Subject: [WSG] Duplicate buttons [EMAIL PROTECTED] group.org 27/08/2004 08:31 PM Please respond to wsg I have been putting duplicate buttons on one form when its a long form, so the user does not have to scroll. I have been told its not good for accessibility, what's the go? Taco Fleur Tell me and I will forget Show me and I will remember Teach me and I will learn ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Web and Online Accessibility Workshop - Sydney 18th August
The National Information and Library Service (NILS) is running a Web and Online Accessibility Workshop in Sydney on 18 August 2004. These workshops introduce accessibility issues in terms of Australian policy contexts and internationally recognised requirements. (NILS is a subsidiary of Vision Australia Foundation, Royal Blind Society of NSW and the Royal Victorian Institute for the Blind). Details and registration forms are at: http://www.visionaustralia.org.au/webaccessibility/workshops/0408-sydney.htm l This full-day workshop is targeted at web-development team leaders, corporate communications professionals, business managers, along with content authors, web programmers, designers and web contract managers. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] more title discussions
Some points to consider: For screen reading software that supports the title attribute the user has the choice to read out either img elements alt or title attribute, not both. (based on limited testing) The londesc attribute is only permitted on the img/frame iframe elements The permitted value for a longdesc attribute is either an absolute or relative URL.(pointing to a document containg the long description) The londesc is not widely supported (no browser support for it on frame/iframe). (source:http://www.blooberry.com/indexdot/html/) To view long descriptions in Internet Explorer 6.0, Netscape 6.1?, and Mozilla 0.9?, hover over the image and select Properties from the context menu. The resulting dialog box contains the long description URL. To view long descriptions in iCab, hover over the image and bring up the context menu, then select Description from the Images submenu. (source:http://www.robinlionheart.com/stds/html4/results.xhtm) with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Tabindex tags not necessary here?
I think that if the default tab order of the page is logical you don't need to use tabindex. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Smooth fonts with CSS
The font-smooth property is part of the CSS3 working draft: http://www.w3.org/TR/css3-fonts/#font-smooth-prop with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] access keys and tab index
Hi ted, recommend you read (if you haven't already) this article More reasons why we don't use accesskeys: http://www.wats.ca/articles/accesskeyconflicts/37 with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] semantic way to mark up form help?
There are a number of things that need to be considered: 1. title attribute content is not accessible to users who cannot use a mouse (as the tool tip only appears on mouseover not onfocus) 2. the title attribute content is only available to a subset of screen reading software (latest versions of JAWS) users and only if it is on certain elements (most inputs and links). It is not recognised on the label element. When a title is placed on the text input it overrides the assoicated label text (for JAWS users at least). 3. an important consideration (for screen reader users ) is the placement of the instructions in the reading order. It is strongly recommended the instructions come before the input they apply to even though they may be visually displayed after the input, so that screen reader users get this information before they encounter the input. Example code for 3: div div style=float:rightThis is the title of your news post, which does not accept HTML input/div div label for=f-title.../label input id=f-title type=text... //div /div with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] css and cms (elegant product sought)
Xstandard is worth a look for using with browser based CMS http://xstandard.com/default.asp with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Roly [EMAIL PROTECTED]To: [EMAIL PROTECTED] .co.uk cc: Sent by: Subject: [WSG] css and cms (elegant product sought) [EMAIL PROTECTED] group.org 23/07/2004 01:44 PM Please respond to wsg a couple of questions, somewhat off topic I would like to capture an image of the the whole html page i.e. what is not visible in the scroll region, so the image would capture something like an 800 x 3000 region to be printed in a brochure. I am looking for an elegant CMS tool which will still supports CSS and which will allow me to create a 5 or 7 page user editable website. Mamboserver and similari CMS products are way to big for the clients I am currently working with. Regards Roly * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Titles Acronyms Abbr etc
Shortened forms on the Web - Abbreviations, Contractions, Acronyms, Initialisms, Symbols and other things. http://www.nils.org.au/ais/web/resources/ozewai2003/short_forms.htm with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. Jackie Reid [EMAIL PROTECTED]To: [EMAIL PROTECTED] e.com.aucc: Sent by: Subject: [WSG] Titles Acronyms Abbr etc [EMAIL PROTECTED] group.org 21/07/2004 03:36 PM Please respond to wsg Hi all Confusion is setting in.is the following piece of code correct or not... h5a name=ventdoor/aacronym title=Vent Door SystemsVent Door Systems/acronym/h5 Looks distinctly like a case of totally unnecessary to me but we have a difference of opinion in the office...so thought i should check before i go through and start removing all the offending stuff that has been inserted into my code in my absence. Have looked online to find out when and how to use titles etc but cant find anything clear and precise so would appreciate someone pointing me to a resource in relation to abbr, acronyms and titles etc Thanks heaps Jackie Reid * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Underlining tabbed to links
This method works in IE 6/ netscape 7/ mozilla 1.3 (requires use of javascript event handlers) a href=contrast.html style=text-decoration:none; onfocus=this.style.textDecoration='underline' onblur=this.style.textDecoration='none'Reduced Contrast Simulation/a | a href=test.html style=text-decoration:none; onfocus=this.style.textDecoration='underline' onblur=this.style.textDecoration='none'Untitled Document/a | a href=testform.html style=text-decoration:none; onfocus=this.style.textDecoration='underline' onblur=this.style.textDecoration='none'Need Money - Finance Lease Calculator/a note: the inline styles etc. are only for demonstation purposes. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Web Accessability IE Toolbar
Donna web accessibility toolbar: http://www.nils.org.au/ais/web/resources/toolbar/ with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
RE: [WSG] Web Accessability IE Toolbar
The reasons why the new version of the web accessibility toolbar is IE only: 1. there was a gap in the market, no tools comparable to those available for mozilla were/are available for IE 2. our programming expertise is limited (if somebody wants to work with us on versions for other browsers/operating systems we'd be interested) 3. our resources are very limited as this project is unfunded so we work on it between paid work and in our spare time. 4. while some people realise that there are better browsers than IE out there, their uptake is still very small , and my original idea was to raise awareness of accessibility issues and provide the tools to the masses. 5. For better or worse many assistive technology users use IE for web browsing, so i tend to use it for accessibility testing and browsing due to this circumstance. 6. What time I have had to work on developing the toolbar has so far been directed at improving the functionality and collaborating with others to create versions in other languages. with regards Steven Faulkner Web Accessibility Consultant National Information Library Service (NILS) 454 Glenferrie Road Kooyong Victoria 3144 Phone: (613) 9864 9281 Fax: (613) 9864 9210 Email: [EMAIL PROTECTED] National Information Library Service A subsidiary of RBS.RVIB.VAF Ltd. * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
