From vinux.development at googlemail.com Tue Jun 1 12:05:36 2010 From: vinux.development at googlemail.com (Tony Sales) Date: Tue, 1 Jun 2010 13:05:36 +0100 Subject: Vinux 3.0 released! Message-ID: On behalf of the whole Vinux community I am happy to announce the 3rd release of Vinux - Linux for the Visually Impaired, based on Ubuntu 10.04 - Lucid Lynx. This version of Vinux provides three screen- readers, two full-screen magnifiers, dynamic font-size/colour-theme changing as well as support for USB Braille displays. Vinux is now available both as an installable live CD and as a .deb package which will automatically convert an existing installation of Ubuntu Lucid into an accessible Vinux system! In addition, we now have our own Vinux package repository (from which you can install our customised packages with apt-get/synaptic) and a dedicated Vinux IRC channel. In the very near future we will also be launching a Vinux Wiki and releasing special DVD, USB and Virtual Editions of Vinux 3.0! To download Vinux 3.0 or to get more information on the project please visit the Vinux Project Homepage at http://vinux.org.uk or use these direct links: Download: http://sina.fi.ncsu.edu/Vinux-3.0.iso (685MB, MD5: 7cc8ac0ed5eaef45dbf215279da3660f) Mirrors: http://vinux.org.uk/downloads.html drbongo Dig that crazy beat on the drums: The best is getting better! From vinux.development at googlemail.com Tue Jun 1 12:19:01 2010 From: vinux.development at googlemail.com (Tony Sales) Date: Tue, 1 Jun 2010 13:19:01 +0100 Subject: Duplicate Posts... Message-ID: I am sorry if more then one version of the Vinux 3.0 release announcements gets posted on the mailing list - I tried to send them yesterday from my College Outlook account and I got a delayed delivery error message, I tried again this morning but with the same result so I opened a new account using my googlemail account and sent the announcement again. If the earlier version get through I am sorry and I hope the administrators can delete them! drbongo Dig that crazy beat on the drums: The best is getting better! From tony.sales at rncb.ac.uk Tue Jun 1 11:02:26 2010 From: tony.sales at rncb.ac.uk (Anthony Sales) Date: Tue, 1 Jun 2010 12:02:26 +0100 Subject: FW: Vinux 3.0 Released! In-Reply-To: References: Message-ID: On behalf of the whole Vinux community I am happy to announce the 3rd release of Vinux - Linux for the Visually Impaired, based on Ubuntu 10.04 - Lucid Lynx. This version of Vinux provides three screen-readers, two full-screen magnifiers, dynamic font-size/colour-theme changing as well as support for USB Braille displays. Vinux is now available both as an installable live CD and as a .deb package which will automatically convert an existing installation of Ubuntu Lucid into an accessible Vinux system! In addition, we now have our own Vinux package repository (from which you can install our customised packages with apt-get/synaptic) and a dedicated Vinux IRC channel. In the very near future we will also be launching a Vinux Wiki and releasing special DVD, USB and Virtual Editions of Vinux 3.0! To download Vinux 3.0 or to get more information on the project please visit the Vinux Project Homepage at http://vinux.org.uk or use these direct links: Download: http://sina.fi.ncsu.edu/Vinux-3.0.iso (685MB, MD5: 7cc8ac0ed5eaef45dbf215279da3660f) Mirrors: http://vinux.org.uk/downloads.html drbongo From pstowe at gmail.com Sat Jun 5 13:55:44 2010 From: pstowe at gmail.com (Penelope Stowe) Date: Sat, 5 Jun 2010 09:55:44 -0400 Subject: Follow-up From May 25th Meeting/Accessibility Team Goals for Maverick Meerkat Message-ID: Hiya, Sorry this e-mail is so late, I've spend the last week and a half moving house and recovering. On May 25th we met and had a quite successful meeting. The main point of the meeting was to follow up from the UDS session and run the decisions there past people and create a plan. The biggest decision from UDS that was confirmed at the meeting was that while we will have an overreaching Accessibility Team, the team will mostly be broken into two teams: a development team headed by Luke Yelavich (TheMuso on IRC) and an outreach/documentation team that I will head. Luke can expand more on what he's looking for for his team as I don't know :-) My team is going to be focusing on two major action items: 1) Updating the wiki pages about the team. Nigel Babu and charlie-tca (sorry Charlie, I don't know your name!) are working on this. I suspect they're happy for any help they can get as I've already found out it's more work than at least one of them expected ;-) 2) Creating personas that can be given to the Ubuntu design team, developers, and other open source accessibility teams. These would create profiles of people with specific impairments and accessibility needs to give people less familiar with accessibility needs something to work with when thinking about their software. Alan Bell and I are working on this, and I know we'd love to hear from any volunteers. We've decided on monthly full group meetings (both development and outreach/documentation together) and I will be sending out an e-mail shortly to see when is best for people for these meetings. I'm very excited by what looks to be happening with this team and hope we can have a really successful cycle! ~Penelope From nigelbabu at ubuntu.com Sat Jun 5 14:14:03 2010 From: nigelbabu at ubuntu.com (Nigel Babu) Date: Sat, 05 Jun 2010 19:44:03 +0530 Subject: Reworking the Accessibility Team Wiki Message-ID: <1275747243.2655.12.camel@nigelbabu-laptop> Hello folks: At UDS, Charlie (err, he's Charlie Kravetz) and I agreed to help on cleaning up the Accessibility Team wiki. Unlike, the other wiki pages that I've worked on, I understand that wiki pages for the Accessibility Team need to be carefully worked on so that its accessible friendly. So, I'd like your feedback on what we've come up so far. We've decided on a Menu on the top like most other teams have [1][2]. I'd like your feedback on how accessible it would be if we had one. We've also come up with a menu structure =Home= =How to use= =Getting Started= =Development= =Personas= =TODO= =Contacts= =Meetings= =Home= The content in /Accessibility can go here, link to "How to Use Accessibility Software" section, also talk about the 2 arms of the team - development and outreach How to use Ubuntu Accessibility software What there is, and how to use it - sorted by disability perhaps?, also including stuff about how to boost your productivity by using, accessibilty software if you are able bodied (such as speech to text for gwibber for example) Getting Started Launchpad team, mailing list, and how to contribute all go here Development All development related stuff go in here Personas List and link to personas that we come up with Most Wanted list of features missing (inc packaging requirements) other open source software not yet in universe TODO Just general action tracker Contacts List people who can be contacted for different stuff - like UK Loco's contact page [3] Meetings Meetings agenda and logs tracker So, thats all we've come up with. Any suggestions are welcome. If you'd like to help with this wiki work, please feel free to get in touch with Charlie (charlie-tca) or me (nigelb). My IRC is connected all the time, so if you poke, I'll reply at some point when I see it. [1] https://wiki.ubuntu.com/ReviewersTeam/Header [2] https://wiki.ubuntu.com/BeginnersTeam/Includes/Header [3] https://wiki.ubuntu.com/UKTeam/Contact Warm Regards Nigel Babu -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: From francesco.fumanti at gmx.net Sat Jun 5 16:28:31 2010 From: francesco.fumanti at gmx.net (Francesco Fumanti) Date: Sat, 05 Jun 2010 18:28:31 +0200 Subject: Reworking the Accessibility Team Wiki In-Reply-To: <1275747243.2655.12.camel@nigelbabu-laptop> References: <1275747243.2655.12.camel@nigelbabu-laptop> Message-ID: <4C0A7B2F.4090704@gmx.net> Hi, What about creating a page that has an overview of the accessibility tools and features with different informations for each tool. Let me for example start myself with a few points: Pointer only users: onboard is an onscreen keyboard for pointer-only users; it is available out of the box in ubuntu; it is available during login, and the desktop session; todo: convince ubuntu to not hide its desktop files by default in the desktop session. Dwelling: available out of the box in ubuntu in the Mouse control panel; todo: it is not possible for a dwell user to activate it by himself during login (a patch is waiting to be accepted to solve this in upstream GNOME); it is not possible for a dwell user to activate it by himself in the desktop session until someone has installed the dwell applet on the gnome panel. Switch access: there is no solution out of the box; gok is an onscreen keyboard for switch access; it is available in universe; I do not know how stable it is. Such an overview page would in my opinion be useful not only for the public who is looking for an accessible distribution, but also for the Ubuntu developers so they have a reference about what is available and more important, what is still missing in their distribution. It however only make sense if it has a maintainer that keeps it up to date and this person will probably have to remain in contact with the different developers... Cheers Francesco On 06/05/10 16:14, Nigel Babu wrote: > Hello folks: > > At UDS, Charlie (err, he's Charlie Kravetz) and I agreed to help on > cleaning up the Accessibility Team wiki. Unlike, the other wiki > pages that I've worked on, I understand that wiki pages for the > Accessibility Team need to be carefully worked on so that its > accessible friendly. So, I'd like your feedback on what we've come up > so far. > > We've decided on a Menu on the top like most other teams have > [1][2]. I'd like your feedback on how accessible it would be if we > had one. > > We've also come up with a menu structure > > =Home= =How to use= =Getting Started= =Development= =Personas= > =TODO= =Contacts= =Meetings= > > =Home= The content in /Accessibility can go here, link to "How to > Use Accessibility Software" section, also talk about the 2 arms of > the team - development and outreach > > How to use Ubuntu Accessibility software What there is, and how to > use it - sorted by disability perhaps?, also including stuff about > how to boost your productivity by using, accessibilty software if you > are able bodied (such as speech to text for gwibber for example) > > Getting Started Launchpad team, mailing list, and how to contribute > all go here > > Development All development related stuff go in here > > Personas List and link to personas that we come up with > > Most Wanted list of features missing (inc packaging requirements) > other open source software not yet in universe > > TODO Just general action tracker > > Contacts List people who can be contacted for different stuff - like > UK Loco's contact page [3] > > Meetings Meetings agenda and logs tracker > > So, thats all we've come up with. Any suggestions are welcome. If > you'd like to help with this wiki work, please feel free to get in > touch with Charlie (charlie-tca) or me (nigelb). My IRC is connected > all the time, so if you poke, I'll reply at some point when I see > it. > > [1] https://wiki.ubuntu.com/ReviewersTeam/Header [2] > https://wiki.ubuntu.com/BeginnersTeam/Includes/Header [3] > https://wiki.ubuntu.com/UKTeam/Contact > > Warm Regards Nigel Babu > From nigelbabu at ubuntu.com Sat Jun 5 16:43:30 2010 From: nigelbabu at ubuntu.com (Nigel Babu) Date: Sat, 05 Jun 2010 22:13:30 +0530 Subject: Reworking the Accessibility Team Wiki In-Reply-To: <4C0A7B2F.4090704@gmx.net> References: <1275747243.2655.12.camel@nigelbabu-laptop> <4C0A7B2F.4090704@gmx.net> Message-ID: <1275756210.2655.15.camel@nigelbabu-laptop> On Sat, 2010-06-05 at 18:28 +0200, Francesco Fumanti wrote: > Hi, > > > What about creating a page that has an overview of the accessibility tools and features with different informations for each tool. Let me for example start myself with a few points: The how to use accessibility software page should address that. I'll keep the contents of this mail to add to that page once we create it. Warm Regards Nigel Babu -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: From elle.uca at ubuntu.com Sat Jun 5 17:40:29 2010 From: elle.uca at ubuntu.com (Luca Ferretti) Date: Sat, 05 Jun 2010 19:40:29 +0200 Subject: Reworking the Accessibility Team Wiki In-Reply-To: <4C0A7B2F.4090704@gmx.net> References: <1275747243.2655.12.camel@nigelbabu-laptop> <4C0A7B2F.4090704@gmx.net> Message-ID: <1275759629.2895.11.camel@turnip> Il giorno sab, 05/06/2010 alle 18.28 +0200, Francesco Fumanti ha scritto: > > Pointer only users: onboard is an onscreen keyboard for pointer-only > users; it is available out of the box in ubuntu; it is available > during login, and the desktop session; todo: convince ubuntu to not > hide its desktop files by default in the desktop session. Francesco, have you seen the new assistive tools panel[1] available in gnome-control-center 2.31.x? (maybe only on git master by now) I wasn't able to build it in my jhbuild sandbox, but opening the gtkbuilder file in glade it seems it provides a new way to manager and start a11y tools. For instance, in Typing tab, you have the ability to turn on and off the "typing assistant" (I suppose the program you can select in Default applications panel) Due to this new way to manage a11y tools, maybe hiding onboard is not a big issue. [1] previously know as capplets, now planes From themuso at ubuntu.com Sun Jun 6 03:09:16 2010 From: themuso at ubuntu.com (Luke Yelavich) Date: Sun, 6 Jun 2010 13:09:16 +1000 Subject: OpenTTS 0.1 released. Message-ID: <20100606030915.GA7577@strigy.yelavich.home> I am proud to announce the very first release of OpenTTS, version 0.1. Thanks to everybody who made this release possible, you know who you are. The first release series is focused on delivering a text to speech framework for the GNOME orca screen reader, that is the same, and hopefully better, than the deprecated gnome-speech solution that has been in use ever since the GNOME accessibility project's inception. The OpenTTS development team is also planning on making further usability improvements, which will aid both system administrators, and end users alike. PLEASE NOTE: This release is NOT considered stable. It is recommended that only those who are willing to test, and report bugs use this first release of OpenTTS. Since we are aiming to provide a usable solution for orca, our aim is to deliver a stable release at the time GNOME 3 officially ships. Between now and September therefore, we hope to make regular monthly releases for the community to track our work, test, and give feedback. These releases will not necessarily be considered stable, but will give users a snapshot they can use, which is free of major show stopper bugs. Release notes: * OpenTTS can be used as a system wide service, however at the moment, this is slightly extra work. The OpenTTS development team hopes to make OpenTTS as a system service much easier to use in the near future. Where can I get it? OpenTTS 0.1 is available from the following locations: Tarball: http://files.opentts.org/opentts/opentts-0.1.tar.gz git: git://git.opentts.org/opentts.git Getting involved: We are always willing to accept any help, no matter where it comes from, or what skills you bring to the table. If you would like to contact us and get involved, please do so in the following ways: * OpenTTS project mailing lists, at http://lists.opentts.org. Please sign up to the opentts-dev mailing list for development discussions. Moderate traffic, low signal to noise ratio. There is also opentts-users, for user questinos, and support. Extremely low traffic, currently low signal to noise ratio. * Reporting/triaging bugs on the OpenTTS issue tracker, available at http://www.opentts.org. Bugs can also be reported on the mailing lists, if you prefer. We welcome any and all contributions. Changelog: For those interested, below you will find a shortlog of work that has been done since the project was started just over 2 months ago: Andrei Kholodnyi (46): moved spd_audio_endian to AudioID moved log_level from spd_audio.h to spd_audio.c and rename it moved pulse.c from spd_audio.c to Makefile.am moved alsa.c from spd_audio.c to Makefile.am moved oss.c from spd_audio.c to Makefile.am moved libao.c from spd_audio.c to Makefile.am moved nas.c from spd_audio.c to Makefile.am moved AudioID alloc into plugins move pulse specific data from AudioID to pulse.c move nas specific data from AudioID to nas.c move oss specific data from AudioID to oss.c move alsa specific data from AudioID to alsa.c remove AudioOutputType split spd library and spd plugin headers added plugin name to audio plugin structure move audio static plugins initialization into static_plugins.c moved module_main.c from the dummy.c to Makefile.am moved module_main.c from cicero.c to Makefile.am moved module_main.c from espeak.c to Makefile.am moved module_main.c from festival.c to Makefile.am moved module.main.c from flite.c to Makefile.am moved module_main.c from generic.c to Makefile.am moved module_main.c from ibmtts.c to Makefile.am moved module_main.c from ivona.c to Makefile.am moved fdsetconv.c from module_utils.c to Makefile.am added pkgconfig support moved debug defines to libspeechd.c update pkg-config support added dynamic load of audio plugins fix module_dbgfile memory leak fix rep_line memory leak replace EPunctMode with SPDPunctuation replace ECapLetRecogn with SPDCapitalLetters replace ESpellMode with SPDSpelling replace EVoiceType with SPDVoiceType replace VoiceDescription with SPDVoice replace ENotification with SPDNotification replace int ssml_mode with SPDDataMode replace-int-priority-with-SPDPriority moved EMessageType to SPDMessageType in opentts_types.h moved SPDMsgSettings from fdset.h to module_utils.h fix refs to fdset.h, general text review fix p_client_socket memory leak fix o_buf memory leak fix o_buf memory_leaks in parse.c fix make distcheck Christopher Brannon (113): Prevent automake from failing when we have no ChangeLog. Added spd_audio_get_playcmd function. Removed SPDAudioSettings Add missing include directives. Use const * consistently for function tables. Fix memory leaks in module_audio_init_spd. Fix copyright oversight. Give Andrei credit in the AUTHORS file. Add prototypes for module_utils_addvoice.c. Add a prototype for festival_read_response. Fix calls to ivona_get_msgpart. Declare functions from ivona_client.c in a header file. Possibly include sndfile.h in ivona_client.c. Fix inclusion of config.h for two files. Add ivona_client.h to Makefile.am. Remove use of strdup in do_list_voices. Change LIST VOICES in the internal module protocol. Use glib consistently in command handlers. Don't redefine PACKAGE and VERSION. Reorganized options.c and options.h for the "say" client. Cleanup options.c and options.h for the server. Stop using xfree in the audio subsystem. Fix link order in the modules. Use ltdl to handle static plugins. Use glib allocation in the server. Use glib allocation in the modules. Use glib allocation in the audio subsystem. Use glib allocation in the common library. Surround calls to OL_RET with braces, and add semicolons. Remove some complex macros. Simplify a macro in parse.c. Indent remaining files. Properly indent header files. Replace calls to free with g_free. Fix segfault when compiled against libao 1.0.0. Remove redundant library from modules/Makefile.am. Add new code for generating timestamps. Rename the Python bindings, including the speechd_config suite. Fix a mistake in the python subdirectory. Use automake in the session subdirectory. Convert the python subdirectory to use the autotools. spd_audio_endian should be id->format. Use otts_getline instead of getline. Fix module_add_config_option in module_utils.c. Change the way that lines are read in the server. Do not include the common library in libopentts. Reopen the connection to pulseaudio when the audio format changes. Add an extra newline when writing to .profile. Add the Unix socket communication method, and use it by default. The communication method is now configurable. Support Unix sockets in the C client API. Autospawn is controlled by an argument to spd_open2. Make autospawn optional for clients. The daemon no longer checks SPEECHD_PORT. Don't require the ~/.speech-dispatcher directory to already exist. Autospawn mechanism fine-tuning Redirect stderr when autospawning in the Python library. Check for the existence of the pid file before handling autospawn. Update otts-conf to generate config for Unix sockets. Do not require ~/.speech-dispatcher to exist. Remove some unused options from the configure script. Put Unix sockets in the home directory, and respect SPEECHD_SOCK. Don't try to compile OSS support if OSS is not available. Fix compilation on Mac OS X. Correct the loop boundary in a convenience function. Properly handle the return value of spd_sayf in the otts-say client. Improved portability checks. Don't store pointers to strings that dotconf will free. Move spd_audio.c and spd_audio.h to the modules subdirectory. Fix prefixes of entry functions in the audio modules. Adjust init_settings_tables to account for renaming of constants. Add constants for reporting errors. Install opentts_types.h. More renaming. Remove the "Future Design" section. More replacement. Change pathnames in the documentation. Rename speech-dispatcher.texi to opentts.texi. Let the otts-say client speak messages that begin with dash. Additional renaming in the otts-say client. Change names of files. Fix a bug in libopentts.c. Replace many references to Speech Dispatcher. Fix two memory leaks in the parse_set function. Use proper comparisons while traversing the history list. Prevent another macro from storing pointers to dotconf's strings. Fix: two command-line options had no effect. Fix a nasty off-by-one bug in the Festival module. Bugfix: ALSA now resumes when suspended. Fix an error-handling clause in alsa_play. Change the test-runner program to use Unix sockets. Update the documentation to reflect the code. Replace the SPEECHD_* environment variables with OPENTTSD_*. Add an introduction to the C API section of the manual. Only change endianness for 16-bit audio. Set correct endianness during libao playback. The function flite_set_voice should be a no-op. Discuss our history in the documentation. Fix the help and version messages for the server. Change speechd to openttsd in log messages. Change speechd to openttsd in error messages and comments. Amend authorship and copyright info for the docs. otts-say.texi needs more authorship and copyright info. Cast return value of lt_dlsym to the proper type. Update the AUTHORS file. Document the process of building ibmtts for 64-bit. Unknown voice types should map to SPD_NO_VOICE. Refactor spd_open2 and fix spd_close. Properly handle autospawning in the Python library. Break out of a loop in pulse_play when an error occurs. Wait for the auto-spawned server process to terminate. Use the same parameter to listen() for both Unix and TCP sockets. Break out of a loop in libao_play when an error occurs. Jason White (1): fix otts-conf default port José Vilmar Estácio de Souza (1): memory leak Luke Yelavich (15): Initial OpenTTSd git repository creation based on unofficial 0.6.68 release of speech-dispatcher session - Re-add accidentally lost Makefile.in Re-add lost python build file Remove reference to ChangeLog file in top directory Reset version to 0.0 Re-add yet another lost file from the openttsd repo transition Set correct audio endianness for audio playback using pulseaudio server - change last references to speech-dispatcher config file directories to opentts Change all other ~/.speech-dispatcher references to ~/.opentts Change more speech-dispatcher references in the pulseaudio output code Rename speechd/spd-say/Speech Dispatcher to their OpenTTS equivalents in otts-conf Don't refer to non-existant fdset.h file in src/common Distribute fdset.h in the tarball Link against libcommon.la in the build dir, not the src dir Release 0.1 Rui Batista (1): Renamed Speech Dispatcher naming to Opentts in INSTALL and minor cleanups on that file Steve Holmes (2): Updated documentation to reflect OpenTTS name. Updated opentts.desktop file. Trevor Saunders (24): change calls to signal to sigaction clean up module_utils update docs rename variables and functions in the server rename spdsend to otts-send cleanup documentation for otts-send rename files in src/clients/send/ change references to spdsend to otts-send update comment in libao.c rename spd_audio_log_level to audio_log_level renamed several audio types rename some audio functions change LIBSPEECHD_DEBUG macro to LIBOPENTTS_DEBUG rename SPEECHD_DEBUG to OPENTTSD_DEBUG and move it to openttsd.h rename SpeechdSocket to openttsd_sockets renamed multiple functions update several comments rename options.home_speechd_dir to options.opentts_dir rename SPEECHD_OPTION_xxx macros change the include guard in openttsd.h to use openttsd instead of speechd change TSpeechDQueue to queue_t rename TSpeechDSock to sock_t rename speechd_queue_alloc to queue_alloc rename SPEECHD_DEFAULT_PORT to OPENTTSD_DEFAULT_PORT William Hubbs (83): rename configure.in to configure.ac fixed typo updated extra_dist in main makefile update documentation Makefile rearranged the api and client directories fix issues with installation only build test binaries when make check is run clean up several makefiles distribute the API's for common lisp and guile started cleaning up configure.ac detect sound systems before speech synthesizers define installed headers correctly don't declare libraries in LDFLAGS more makefile cleanup fixed an autotools conflict include config.h in all sources move the code in intl to a convenience library tests should use the convenience library remove PACKAGE and VERSION definitions from server's makefile clean up ignore patterns cleaned up EXTRA_DIST for modules added more ignore patterns convert libsdaudio to a convenience library configuration system update remove rule for html documentation fixed a comment remove old speech dispatcher announcement disable session integration support by default clean up the modules makefile removed extra_dist from src/audio/Makefile.am install spd_audio_plugin header file rename the C API library tests should link against libopentts fix include in the say client fixed an include in the guile bindings updated the header in libopentts.h updated an include in libopentts.c rename directories from speech-dispatcher to opentts audio subsystem updates move the modules sub directory rename ottslibdir to audiodir fixed variable in audio makefile include spd_audio_plugin.h from spd_audio.c instead of spd_audio.h. Revert "include spd_audio_plugin.h from spd_audio.c instead of spd_audio.h." ran code through Lindent python build updates session build fixes do not install Czech documentation fix declaration of festival_connection_crashed fix include in spd_audio.c fix declaration of current_index_mark convert global variable declarations to externs consolidate global variables in modules remove DBG macro from modules remove the prefix from the module names rename the daemon make better use of conditionals in modules makefile rename fixes move public header files to common include directory build system updates remove the session directory add configure option to disable the installation of the python bindings remove prefix from audio plugin names Revert "remove prefix from audio plugin names" removed several change logs remove prefix from names of audio plugins fix includes of libopentts.h and opentts_types.h in the say client and api change main config file to openttsd.conf fix config makefile remove duplicate include directive in openttsd.conf move desktop autostart file to config directory clean up config files fix permissions on the socket permission fixes fix typo remove dotconf from pkg-config file fix Makefile substitutions clarify the contact information in the SSIP document fix copyright assignment request make configure fail when necessary libraries are not on the system build fixes for the audio subsystem remove ability to disable autospawn from server fix implicit declaration of g_unlink jose vilmar estacio de souza (1): possible memory leaks tbsaunde (1): refactor module_main to use disatch_cmd instead of macros Regards Luke Yelavich OpenTTS Project lead. From phillw at phillw.net Sun Jun 6 04:07:10 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Sun, 6 Jun 2010 05:07:10 +0100 Subject: gtk2 and gnome Message-ID: Hi, I read of things being done that are for gnome, I'm guessing that they are gnome only? Does that mean that those running xfce, lxde, etc. as desktop environments can not use them without pulling in all of the gnome libraries? I understand that the newer gtk standard is compatible across the different flavours of desktop environments, without getting too technical, could some one tell me what the differences are. Thanks, Phill. -------------- next part -------------- An HTML attachment was scrubbed... URL: From themuso at ubuntu.com Sun Jun 6 23:50:44 2010 From: themuso at ubuntu.com (Luke Yelavich) Date: Mon, 7 Jun 2010 09:50:44 +1000 Subject: gtk2 and gnome In-Reply-To: References: Message-ID: <20100606235044.GI3956@strigy.yelavich.home> On Sun, Jun 06, 2010 at 02:07:10PM EST, Phillip Whiteside wrote: > Hi, > > I read of things being done that are for gnome, I'm guessing that they are > gnome only? Does that mean that those running xfce, lxde, etc. as desktop > environments can not use them without pulling in all of the gnome libraries? > I understand that the newer gtk standard is compatible across the different > flavours of desktop environments, without getting too technical, could some > one tell me what the differences are. What things are you referring to exactly? As to XFCE for example, since it uses GTK, and since the accessibility bits are being abstracted away from GNOME as much as possible, XFCE should be able to use the accessibility infrastructure. Parts of XFCE, at least when I last tried, were accessible to Orca, but certainly not everything. It also doesn't help that XFCE doesn't really have the right bits in place to start accessbility infrastructure pieces properly. I have been meaning to help them with that, but haven't got around to it. Also when I last tried, there were not any useful keyboard shortcuts ofor a fair number of tasks. I should really grab the Xubuntu lucid disk and install it into a VM and have another play. Luke From phillw at phillw.net Mon Jun 7 00:05:09 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Mon, 7 Jun 2010 01:05:09 +0100 Subject: gtk2 and gnome In-Reply-To: <20100606235044.GI3956@strigy.yelavich.home> References: <20100606235044.GI3956@strigy.yelavich.home> Message-ID: Hi Luke, I'm now running lubuntu which is lxde based but also GTK2 compliant, I'm only a tester of things but would be happy to assist in anyway I can for testing this newer flavour with accessibility options. Regards, Phill. On Mon, Jun 7, 2010 at 12:50 AM, Luke Yelavich wrote: > On Sun, Jun 06, 2010 at 02:07:10PM EST, Phillip Whiteside wrote: > > Hi, > > > > I read of things being done that are for gnome, I'm guessing that they > are > > gnome only? Does that mean that those running xfce, lxde, etc. as desktop > > environments can not use them without pulling in all of the gnome > libraries? > > I understand that the newer gtk standard is compatible across the > different > > flavours of desktop environments, without getting too technical, could > some > > one tell me what the differences are. > > What things are you referring to exactly? > > As to XFCE for example, since it uses GTK, and since the accessibility bits > are being abstracted away from GNOME as much as possible, XFCE should be > able to use the accessibility infrastructure. Parts of XFCE, at least when I > last tried, were accessible to Orca, but certainly not everything. It also > doesn't help that XFCE doesn't really have the right bits in place to start > accessbility infrastructure pieces properly. I have been meaning to help > them with that, but haven't got around to it. > > Also when I last tried, there were not any useful keyboard shortcuts ofor a > fair number of tasks. I should really grab the Xubuntu lucid disk and > install it into a VM and have another play. > > Luke > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanke at brailcom.org Mon Jun 7 15:34:47 2010 From: hanke at brailcom.org (Hynek Hanke) Date: Mon, 07 Jun 2010 17:34:47 +0200 Subject: OpenTTS 0.1 released. In-Reply-To: <20100606030915.GA7577@strigy.yelavich.home> References: <20100606030915.GA7577@strigy.yelavich.home> Message-ID: <4C0D1197.2090905@brailcom.org> On 6.6.2010 05:09, Luke Yelavich wrote: > I am proud to announce the very first release of OpenTTS, version 0.1. Dear Luke Yelavich, It is a pure nonsense that the development of OpenTTS started two months ago. You know very well that it is a fork of the Speech Dispatcher project which has been developed in the course of the past 10 years. The real developers are different from who you wrote in your announce. The project was not started to become a replacement for gnome-speech, as you state, instead being a generic speech service available to different client applications, Gnome and Orca being one of them. The decision of Orca to migrate to Speech Dispatcher has been made over the past year and was announced before OpenTTS was ``created'', as is described on Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=606975 Please let us remind you that the architecture and design are what is most important. It took us time and resources to come up with the current architecture and we don't think OpenTTS is introducing anything significantly new over Speech Dispatcher. Although some work has been done in the fork, in the big picture, these have been so far just minor code improvements. Before the fork, there was a face-to-face agreement between you and Brailcom, that you will keep an unofficial development repository, where we will gather patches and changes, which will later be reviewed and released in the official version. While we were doing so, we evaluated the quality of the patches gathered in this way and found it was very various. There were good code improvements, but they were mixed with very amateurish hacks (such as totally random port assignment or completely missing documentation), which we could not release as serious software without first finding time to rework them significantly, which takes resources and time. The whole fork is an unnecessary fragmentation of the limited resources we all have for accessibility. If there was capacity to move Speech Dispatcher forward, it could have been done in the same project. We still continue the development of Speech Dispatcher from our own resources for the benefit of all of you, in our own serious and systematic way, and preparing the 0.7 release. It is however impossible now for us to use fixes and improvements from the OpenTTS Git due to reorganization of its code and especially the unnecessary renaming of all identifiers in the code. As the real developers of Speech Dispatcher, which some of you now call OpenTTS, we must say that a lot of work is currently being wasted. We continue to see this as very bad. The new name OpenTTS is very unfortunate, because it is technically wrong. Speech Dispatcher/OpenTTS doesn't do and shouldn't do any TTS (Text-to-Speech). It is merely an interface between applications and Text-to-Speech engines. Serious developers must understand and use terminology correctly. We still don't see a technical reason for such duplication of effort. We asked for responsibility and cooperation several times publicly and also privately without any effect. We are a non profit organization and our main goal is to help visually impaired people. All our projects are strictly Free Software projects and Speech Dispatcher is one of our key long term projects for the last 10 years. We believe that it is a major benefit for every project to be backed up by a stable company which provides quality controll and stability of the future development. We don't understand the motivations behind rebranding Speech Dispatcher to OpenTTS. We believe that a constructive solution is still possible. Our offer of cooperation is still valid, nothing has changed. There are two possibilities for cooperation: as a volunteer contributor and in the future as a paid member of our development team. Anyone who wishes to cooperate, please contact us, we are very open. Best regards, Hynek Hanke Speech Dispatcher maintainer Brailcom, o.p.s. From waywardgeek at gmail.com Mon Jun 7 16:24:24 2010 From: waywardgeek at gmail.com (Bill Cox) Date: Mon, 7 Jun 2010 12:24:24 -0400 Subject: [orca-list] OpenTTS 0.1 released. In-Reply-To: <4C0D1197.2090905@brailcom.org> References: <20100606030915.GA7577@strigy.yelavich.home> <4C0D1197.2090905@brailcom.org> Message-ID: I'll throw out my preferred solution, though as I often state, my opinion on this matter doesn't count. Hynek, as the original author and maintainer, you have as much or more to contribute than anyone else. Why not join the OpenTTS team? The system they've set up seems to be working very well, and progress has accelerated greatly. It would be even better with you on the team, and it would eliminate duplication of effort. Just my $0.01 Bill From phillw at phillw.net Mon Jun 7 14:49:50 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Mon, 7 Jun 2010 15:49:50 +0100 Subject: Flash Security alert Message-ID: Hi folks, this one has just hit one of my mailing lists, I suggest you action it and pass it on. http://www.adobe.com/support/security/advisories/apsa10-01.html Regards, Phill. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hanke at brailcom.org Tue Jun 8 08:13:51 2010 From: hanke at brailcom.org (Hynek Hanke) Date: Tue, 08 Jun 2010 10:13:51 +0200 Subject: [orca-list] OpenTTS 0.1 released. In-Reply-To: References: <20100606030915.GA7577@strigy.yelavich.home> <4C0D1197.2090905@brailcom.org> Message-ID: <4C0DFBBF.1080301@brailcom.org> On 7.6.2010 18:24, Bill Cox wrote > Hynek, as the original author and maintainer, you have as much or more to contribute than anyone > else. Why not join the OpenTTS team? Sorry, but you do not understand. We work as a team. There is not just me. Best regards, Hynek Hanke From halim.sahin at freenet.de Wed Jun 9 07:59:47 2010 From: halim.sahin at freenet.de (Halim Sahin) Date: Wed, 9 Jun 2010 09:59:47 +0200 Subject: does maverick contain a working at-spi2 infrastrcture? Message-ID: <20100609075947.GA29301@gentoo.local> Hi, I want to give it a try but don't want to build all needed stuff myself. Are the packages at-spi2[atk/core] and pyatspi2 already included in the maverick live cds? BR. Halim From themuso at ubuntu.com Wed Jun 9 23:20:42 2010 From: themuso at ubuntu.com (Luke Yelavich) Date: Thu, 10 Jun 2010 09:20:42 +1000 Subject: does maverick contain a working at-spi2 infrastrcture? In-Reply-To: <20100609075947.GA29301@gentoo.local> References: <20100609075947.GA29301@gentoo.local> Message-ID: <20100609232042.GA2734@strigy.yelavich.home> On Wed, Jun 09, 2010 at 05:59:47PM EST, Halim Sahin wrote: > Hi, > I want to give it a try but don't want to build all needed stuff myself. > Are the packages at-spi2[atk/core] and pyatspi2 already included in the > maverick live cds? Maverick will not ship at-spi2 by default, but the at-spi2 packages wil lshortly be in a PPA for users to test them and report bugs upstream. Luke From halim.sahin at freenet.de Thu Jun 10 05:45:01 2010 From: halim.sahin at freenet.de (Halim Sahin) Date: Thu, 10 Jun 2010 07:45:01 +0200 Subject: does maverick contain a working at-spi2 infrastrcture? In-Reply-To: <20100609232042.GA2734@strigy.yelavich.home> References: <20100609075947.GA29301@gentoo.local> <20100609232042.GA2734@strigy.yelavich.home> Message-ID: <20100610054501.GA23098@gentoo.local> Hi Luke, Just wondering about this decision: maverick will ship gnome 3.0 right? gnome 3 doesn't ship bonobo and other stuff so I am interested to know how you can reintegrate bonobo there. BR. Halim From themuso at ubuntu.com Thu Jun 10 22:21:45 2010 From: themuso at ubuntu.com (Luke Yelavich) Date: Fri, 11 Jun 2010 08:21:45 +1000 Subject: does maverick contain a working at-spi2 infrastrcture? In-Reply-To: <20100610054501.GA23098@gentoo.local> References: <20100609075947.GA29301@gentoo.local> <20100609232042.GA2734@strigy.yelavich.home> <20100610054501.GA23098@gentoo.local> Message-ID: <20100610222144.GA4004@strigy.yelavich.home> On Thu, Jun 10, 2010 at 03:45:01PM EST, Halim Sahin wrote: > Hi Luke, > > Just wondering about this decision: > maverick will ship gnome 3.0 right? > gnome 3 doesn't ship bonobo and other stuff so I am interested to know > how you can reintegrate bonobo there. Ubuntu Maverick will not be shipping everything from GNOME 3, we will still have pieces that require bonobo, particularly gnome panel. Since the GNOME/GTK/bonobo framework is used by several different Ubuntu variants, things have to be managed conservatively, so things don't break too badly for everyone at once. There is also code maturity from upstrea to consider. As for at-spi2 packages, I should have them ready to go in a PPA later today for maverick and lucid. Luke From themuso at ubuntu.com Thu Jun 10 22:37:45 2010 From: themuso at ubuntu.com (Luke Yelavich) Date: Fri, 11 Jun 2010 08:37:45 +1000 Subject: Vinux to be used as Ubuntu Accessibility testing platform. Message-ID: <20100610223744.GB4004@strigy.yelavich.home> Hi all I may have told a few people here and there over the past few weeks, but I have decided to use Vinux as a test platform for accessibility related features. The plan is to test such features, make sure they are well implemented, and then as time and code/setup maturity permits, they will be merged into the main Ubuntu distribution proper. This work will start by moving Vinux disk building over to a the same framework used to build official Ubuntu CDs. Canonical won't be building the disks, but I know how to set up the framework. This will allow for much easier development of Vinux, and allow for much more rapid development, as there will be the opportunity for daily builds, basing different builds on different Ubuntu releases, etc. Regards Luke From tony.sales at rncb.ac.uk Thu Jun 10 23:03:41 2010 From: tony.sales at rncb.ac.uk (Anthony Sales) Date: Fri, 11 Jun 2010 00:03:41 +0100 Subject: Vinux to be used as Ubuntu Accessibility testing platform. In-Reply-To: <20100610223744.GB4004@strigy.yelavich.home> References: <20100610223744.GB4004@strigy.yelavich.home> Message-ID: Hi Luke, I would just like to thank Luke, the Vinux development team and everyone else (Orca, Gnome, Speakup, Speech-Dispatcher and Compiz etc) whose contributions have made it possible for this to happen. We all hope that this relationship will enable Linux accessibility to improve at a faster rate and in the meantime provide a very beginner friendly introduction to Linux for VI users, as well as a cutting edge distro which can be used to test the latest accessibility packages and fix bugs. The ultimate aim is of course to make Ubuntu and all Linux distributions as accessible as possible as well as matching or exceeding the quality of accessibility packages currently available on Windows and Mac etc. (Thus making Vinux unnecessary - yes we are the first distro whose main aim is to disappear in a puff of orange smoke!) It is only by combining our efforts, rather than pulling in different directions that we can do this, and we would encourage people who would like to get involved in the development of Vinux and related technologies to get in touch. There are many different ways to help apart from the obvious programming and bug squashing roles e.g. testing, documentation, user support etc. We hope to hear from you soon! Tony Sales (aka drbongo) From keithint1234 at gmail.com Fri Jun 11 04:50:37 2010 From: keithint1234 at gmail.com (Keith Hinton) Date: Fri, 11 Jun 2010 00:50:37 -0400 Subject: My apologys for my recent developer panic attack Message-ID: Sorry all for the way I must have come off in my prior message. But like I just stated in the previous message, I just don't want to see the time Bill took to get things that now work better than in the present day Ubuntu in my personal opinion such as Pulse audio, to suddenly go backwards and stop working due to so many developpers working on the project. How will the development team be kept together with so many people doing daily builds? As Canonical won't be building the disks, is Bill supposed to build them all then? especially if daily builds are beginning to show up? Luke, perhaps you could help to clarify. I'm more than a bit confused-I suppose. Thanks! -- Regards, --Keith Skype: skypedude1234 MSN Messenger: keithint37 at hotmail.com Yahoo/AIM/Twitter: keithint1234 Facebook: http://facebook.com/keith.hinton1 From phillw at phillw.net Sun Jun 13 02:13:07 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Sun, 13 Jun 2010 03:13:07 +0100 Subject: Docs Team and Ubuntu Manual Project: Toward future cooperation In-Reply-To: <1276384605.1976.3.camel@panther> References: <1276384605.1976.3.camel@panther> Message-ID: The ubuntu-manual guys have been very successful in getting screenshots into the docs. It's a lead that ubuntu-docs should follow, so long as we don't go overboard and start (over-)using screenshots in inappropriate places. I think we should work on cracking this particular issue once and for all this release cycle. Hi, Can I give a +1 for use of images, one of the ones I was interested doing was installing LAMP, in the meantime, there are people having problems, the sooner a couple of simple screen-shots can be included the better. I was going to do a 1 hour presentation on it, except that it takes all of 10 minutes to do. Yes, we do have to make allowances for those who do not have internet access speeds / limits to allow the downloading of many images, so we must bear those in mind. Can the docs team also have a look at Rule508 that does require an explanation is put into the ? http://www.section508.gov/index.cfm?FuseAction=content&ID=12#Web That will, possibly drag all the documentation together. I've cc'd this discussion to the accessibilty mailing list, as I have not seen any mention of it and I do think it is important that these needs are considered. Just my $0.02 Regards, Phill, On Sun, Jun 13, 2010 at 12:16 AM, Phil Bull wrote: > Hi guys, > > I'm back from my break now. Where did we get to with this discussion? > Did the planned meeting occur, and if so, are there any logs that I can > review? > > I'll reply to a couple of points that were made a while ago. > > On Tue, 2010-05-18 at 08:10 +0100, Matthew East wrote: > > > Our team feels that there are some unaddressed gaps in Ubuntu > > > documentation. For example, there is a lack of official linear > > > documentation -- a guide, hence the UMP project's manual. > > > > As I said quite early on in the last release cycle [1], I can see a > > market for a single printable manual. We tend to make a clear > > distinction in documentation writing between linear manuals and > > onscreen help - they are two very different formats with separate > > uses. But both of them have a place in helping users in different > > contexts and situations. My problem with the manual team's work hasn't > > been their goal of producing a single linear piece of documentation, > > but rather it's been the fact that the team has sought to reinvent the > > wheel by writing content from scratch, in circumstances where > > ubuntu-doc's material was essentially suitable, with modification, > > improvement and customisation, to being reused. > > I agree that both linear and topic-based docs can be useful, but I don't > think any of us have a good enough idea of where we should be using > either of them. It's true that there are situations where one form of > documentation is a more sensible choice than another. But are we > actually choosing a documentation format because it's the right fit for > a given situation, or just because we feel like using that particular > format? > > I think we need to work harder on understanding our users' needs. I > don't think statements like "I can see a market for X" or "there is a > lack of Y" are helpful on their own - show me the evidence of a market > for X, or the adverse impact of the lack of Y, please! > > > > There is > > > still a lack of centrally-produced, localized documentation. There is > > > very little visual aid in the docs, and no focus on multimedia. > [...] > > As to the second sentence, we have discussed many times, most recently > > in the past release cycle [2], the use of screenshots in the > > documentation. My personal view tends to be that the difficulties of > > arranging for translation of the screenshots (because it can't be done > > through Rosetta) has meant that using them is undesirable. However, if > > a way can be found to facilitate translation of screenshots, then that > > may be a way to resolve the problem. > > The ubuntu-manual guys have been very successful in getting screenshots > into the docs. It's a lead that ubuntu-docs should follow, so long as we > don't go overboard and start (over-)using screenshots in inappropriate > places. I think we should work on cracking this particular issue once > and for all this release cycle. > > > > We also felt that the Docs Team's process was somewhat rigid, and too > > > slow for certain types of contributions. While this approach is very > > > consistent with the docs team's emphasis on long-term sustainability > > > and quality of the docs process, there was. in our view. much less > > > emphasis on widening the scope of documentation and simplifying > > > community input. > > > > Lowering the barrier to entry and improving community input is > > definitely a key goal of every Ubuntu team, including ubuntu-doc. > > While we have made some progress towards (for example) encouraging > > people to submit material in plain text, we've clearly not done enough > > on this front. I think that ubuntu-manual has shown how to attract > > contributors by using a lot of publicity and clear instructions about > > how to contribute, and I think this is something that ubuntu-doc could > > definitely learn from. I think the major problem is that the team > > members frequently don't have much time to promote the team on blogs, > > microblogs and websites, and equally sometimes potential new > > contributors don't get as much attention and encouragement as they > > deserve. ubuntu-manual's enthusiasm could help with that. > > I can work on improving doc team "outreach" over the summer, because > I'll actually have some free time over the next couple of months! I'll > start a thread on this at some point. > > Thanks, > > Phil > > -- > Phil Bull > https://launchpad.net/~philbull > > > > -- > ubuntu-doc mailing list > ubuntu-doc at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phillw at phillw.net Tue Jun 15 01:15:01 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Tue, 15 Jun 2010 02:15:01 +0100 Subject: VEDICS Speech Assistant In-Reply-To: <20100522070321.GE14174@blackbox.hittsjunk.net> References: <4BF6EB61.6080500@harvee.org> <20100522070321.GE14174@blackbox.hittsjunk.net> Message-ID: Hi Kenny, Wounds licked, I've been as you will have read been some what disheartened over things. But, on the new slimmed down version of ubuntu (lubuntu) we have some one who is interested in seeing what it can do. The horrible news? lubuntu is gtk(2) (uses lxde, but gtk compliant) based, so no it is not going to have gnome unless and until they code to gtk.? As a part of these discussions http://forum.phillw.net/viewforum.php?f=14 has a new person. Heck, I may even get a tester for some things. As that baby forum is in the midst of moving to a new host provider, new members replies are moderated so as to keep out the spammers (there is a discussion on capchta on it). To every one, you are welcome to pop over. if you email back I will remove any person from this mailing list to remove them from the moderation queue. One of things I have reflected upon is that there are people who are frustrated, I do not mind a good hearted discussion but can we try to have a positive note to the end of the frustrations, even if it is just "I feel better getting that out of my system"? I'll see how the area progresses, if it does okay, I can split it into 'get if your chest' and technical discussions for web stuff. For the 'team' would it be okay to recommend to people that they join this mailing list to see what is going on with life? Also, would it be okay to tell them of http://ubuntuforums.org/forumdisplay.php?f=145 In my view, the more that know the better, but I ask permission first. With vinux etc., being about, there is a lot going on, but little reporting of it. I do get the usual bots like google, bling etc, come wandering round so it may help when people are looking for information. Regards, Phill. On Sat, May 22, 2010 at 8:03 AM, Kenny Hitt wrote: > Hi. > > On Fri, May 21, 2010 at 04:21:53PM -0400, Eric S. Johansson wrote: > > On 5/21/2010 11:04 AM, Nischal Rao wrote: > > > > > > > > Currently the software doesn't support the dictation facility. However, > > > we are planning to add this feature in the future. > > > The best part of this software is that it is speaker independent, no > > > training is required and it can recognize words not present in the > > > English dictionary. > > > > > > Currently it works well on ubuntu 9.10 and ubuntu 10.04 > > > > > > You can find the source code at : > http://sourceforge.net/projects/vedics/ > > > > very nice. have you thrown away your keyboard yet? please do so and > send a > > message to the list without keyboard. > > > Before you post such a negative message, you should really read first. > This is not even a stable tarball release yet. The author stated clearly > dictation wasn't available, but is planned to be added. > If he had claimed that you could do dictation, your post would make since, > but since > he didn't, you look like a winy ass. > When a project like this is still at such an early stage, bad attitude will > cause a developer > to wonder if the trouble is really worth it. > > One note to those people who have recently started to get a ubuntu > accessibility group going again: > you really need to subscribe to gnome-accessibility. All the developments > in accessibility are happening > in upstream gnome and not ubuntu. > There was a more complete discussion about this particular app on > gnome-accessibility. > > Kenny > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbr100uk at gmail.com Tue Jun 15 05:11:38 2010 From: jbr100uk at gmail.com (John Robinson) Date: Tue, 15 Jun 2010 06:11:38 +0100 Subject: Requesting audio description support in Totem Message-ID: <4C170B8A.9070202@googlemail.com> Hi everyone. Sorry if this seems a bit off topic, but I'm really not sure where else to ask. I would like to contact the developers of Totem to ask if they can incorporate support for audio description into future versions of the player. The problem is that Totem doesn't appear to have a mailing list or anything like that, so I'm unsure how best to contact its development team. If anyone has any advice as to the best way to contact the Totem developers, I'd really appreciate it. Many thanks in advance. John From elle.uca at ubuntu.com Tue Jun 15 08:04:26 2010 From: elle.uca at ubuntu.com (Luca Ferretti) Date: Tue, 15 Jun 2010 10:04:26 +0200 Subject: Requesting audio description support in Totem In-Reply-To: <4C170B8A.9070202@googlemail.com> References: <4C170B8A.9070202@googlemail.com> Message-ID: <1276589066.13340.6.camel@turnip> Il giorno mar, 15/06/2010 alle 06.11 +0100, John Robinson ha scritto: > I would like to contact the developers of Totem to ask if they can > incorporate support for audio description into future versions of the > player. Totem is yet able to automatically (same file name in same directory) and manually load subtitles, as well as query opensubtitles.org (via plugin, maybe disabled by default) > The problem is that Totem doesn't appear to have a mailing list > or anything like that, so I'm unsure how best to contact its development > team. mailing list: http://mail.gnome.org/mailman/listinfo/gnome-multimedia web: bugzilla.gnome.org (search for an existing bug, if it doesn't exist, open it) IRC: #totem on GIMPNet email: Bastien Nocera - main developer, but don't say him you are an ubuntu user ;) From philbull at gmail.com Tue Jun 15 10:34:24 2010 From: philbull at gmail.com (Phil Bull) Date: Tue, 15 Jun 2010 11:34:24 +0100 Subject: Docs Team and Ubuntu Manual Project: Toward future cooperation In-Reply-To: References: <1276384605.1976.3.camel@panther> Message-ID: <1276598064.21095.102.camel@panther> Hi Phill, On Sun, 2010-06-13 at 03:13 +0100, Phillip Whiteside wrote: [...] > Yes, we do have to make allowances for those who do not have internet > access speeds / limits to allow the downloading of many images, so we > must bear those in mind. Can the docs team also have a look at Rule508 > that does require an explanation is put into the ? > > http://www.section508.gov/index.cfm?FuseAction=content&ID=12#Web As far as I'm aware, the Yelp help viewer inserts the correct alt tags from the documentation. Thanks, Phil -- Phil Bull https://launchpad.net/~philbull From hanke at brailcom.org Wed Jun 16 14:51:12 2010 From: hanke at brailcom.org (Hynek Hanke) Date: Wed, 16 Jun 2010 16:51:12 +0200 Subject: Speech Dispatcher 0.7 Released Message-ID: <4C18E4E0.3020106@brailcom.org> Speech Dispatcher 0.7 Released ==================== The Brailcom organization is happy to announce the availability of Speech Dispatcher 0.7 developed as a part of the Free(b)Soft project. Please read `NOTES' bellow. * What is new in 0.7? * Speech Dispatcher uses UNIX style sockets as default means of communication, thus avoiding the necessity to choose a numeric port and greatly easying session integration and adressing several security issues * Autospawn -- server is started automatically when a client requests it It can be forbidden in the appropriate server configuration file (thanks to Luke Yelavich) * Pulse Audio output reworked and fixed (thanks to Rui Batista) * Dispatcher runs as user service (not system service) by default and doesn't require the previous presence of ~/.speech-dispatcher directory * Graceful audio fallback (e.g. if pulse is not working, use Alsa...) (thanks to Luke Yelavich) * Various bugfixes and fine-tunnings * Updated documentation NOTES for packagers: The communication mechanism of Speech Dispatcher and the way of starting it has been severely reworked in this release. Some ./configure variables as PIDPATH are no longer relevant. It is highly recommended to start Speech Dispatcher per-user in his user session and avoid starting it as a system service via /etc/init.d/. Please check the updated documentation, especially the part Technical Specification. * Where to get it? You can get the distribution tarball of the released version from http://www.freebsoft.org/pub/projects/speechd/speech-dispatcher-0.7.tar.gz We recommend you to fetch the sound icons for use with Speech Dispatcher. They are available at http://www.freebsoft.org/pub/projects/sound-icons/sound-icons-0.1.tar.gz Corresponding Debian, Gentoo and Ubuntu packages will soon be available at your distribution mirrors. The home page of the project is http://www.freebsoft.org/speechd * What is Speech Dispatcher? Speech Dispatcher is a device independent layer for speech synthesis, developed with the goal of making the usage of speech synthesis easier for application programmers. It takes care of most of the tasks necessary to solve in speech enabled applications. What is a very high level GUI library to graphics, Speech Dispatcher is to speech synthesis. Key Speech Dispatcher features are: - Message priority model that allows multiple simultaneous connections to Speech Dispatcher from one or more clients and tries to provide the user with the most important messages. - Different output modules that talk to different synthesizers so that the programmer doesn't need to care which particular synthesizer is being used. Currently Festival, Flite, Epos, Espeak and (non-free) Dectalk software, IBM TTS are supported. Festival is an advanced Free Software synthesizer supporting various languages. Espeak is a very fast multi-lingual synthesizer. - Client-based configuration allows users to configure different settings for different clients that connect to Speech Dispatcher. - Simple interface for programs written in C, C++ provided through a shared library. Python, Common Lisp and Guile interface. An Elisp library is developed as a sperate project speechd-el. Possibly an interface to any other language can be developed. * How to report bugs? Please report bugs at . For other contact please use Best Regards, Brailcom, o.p.s. http://www.brailcom.org From phillw at phillw.net Thu Jun 17 11:22:17 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Thu, 17 Jun 2010 12:22:17 +0100 Subject: Screen Reader Message-ID: Hi, I currently use a system advised by http://www.webaim.org/techniques/css/invisiblecontent/ for a hidden link on a site designed to catch only harvesting robots, that being the *display: none*. I use http://totalvalidator.com/ for validation, it came highly recommended and is certainly more capable than the Rule508 'Cynthia Says' one that comes with the Firefox WebDeveloper. I've had a quick 'chat' with the team that are responsible for Total Advisor and they inform me that it does not check for CSS compliance so is flagging up the hidden link as being a problem, although it's abilities for checking other parts of WCAG / WAI coding is exceptionally good and even picked up a couple of spelling mistakes ;-) Could some one with a screen reader have a quick look at http://mgjuddltd.co.uk and check that the reader does NOT read out "Hidden Link - Security link only" which would be after the last navigation button "Stop Press" in the navigation list on the left. (If you get chance, could you also ensure that this behaviour is repeated when Full Navigation list is toggled Off). Thanks in advance, Regards, Phill. -------------- next part -------------- An HTML attachment was scrubbed... URL: From waywardgeek at gmail.com Fri Jun 18 13:18:54 2010 From: waywardgeek at gmail.com (Bill Cox) Date: Fri, 18 Jun 2010 09:18:54 -0400 Subject: Call for C++ coders make Orca work better with Firefox Message-ID: If there are C++ coders on this list who hate the problems when using Orca with Firefox, please consider joining my Firefox debugging team. We have many bugs to track down, and by myself, it will take many months. Together, I bet we could fix Firefox in weeks. Feel free to reply to this post, or to me personally. Thanks, Bill From phillw at phillw.net Fri Jun 18 22:17:29 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Fri, 18 Jun 2010 23:17:29 +0100 Subject: Screen Reader In-Reply-To: References: Message-ID: Hi Alex, thanks ever so much for that. As I'm sure you realise, the robot testing is only so good. Whilst I know that a site of engineers parts and drawings on is not exactly a 'run of the mill site', if I can get that sort of site to compliance I can say to to others that there is no excuse. I know I still have more work to do on there, but at least I know I am making (slow) progress :-) Thanks, Phill. On Fri, Jun 18, 2010 at 10:34 PM, Alex H. wrote: > Hi Phill, > > Everything seems to work correctly using NVDA, a screenreader for > windows and using Mozilla Firefox 3.6.3. > After Stop Press, it says text tutorials. I tried this with full > navigation on and off. > > Thanks, > > Alex > > On 6/17/10, Phillip Whiteside wrote: > > Hi, > > > > I currently use a system advised by > > http://www.webaim.org/techniques/css/invisiblecontent/ for a hidden link > on > > a site designed to catch only harvesting robots, that being the *display: > > none*. I use http://totalvalidator.com/ for validation, it came highly > > recommended and is certainly more capable than the Rule508 'Cynthia Says' > > one that comes with the Firefox WebDeveloper. I've had a quick 'chat' > with > > the team that are responsible for Total Advisor and they inform me that > it > > does not check for CSS compliance so is flagging up the hidden link as > being > > a problem, although it's abilities for checking other parts of WCAG / WAI > > coding is exceptionally good and even picked up a couple of spelling > > mistakes ;-) > > > > Could some one with a screen reader have a quick look at > > http://mgjuddltd.co.uk and check that the reader does NOT read out > "Hidden > > Link - Security link only" which would be after the last navigation > button > > "Stop Press" in the navigation list on the left. (If you get chance, > could > > you also ensure that this behaviour is repeated when Full Navigation list > is > > toggled Off). > > > > Thanks in advance, > > > > Regards, > > > > Phill. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kenny at hittsjunk.net Sun Jun 20 12:06:01 2010 From: kenny at hittsjunk.net (Kenny Hitt) Date: Sun, 20 Jun 2010 07:06:01 -0500 Subject: Screen Reader In-Reply-To: References: Message-ID: <20100620120601.GA2455@hittsjunk.net> Hi. Sorry for replying to your reply. I lost my root partition which contained /var/mail. Unfortunately, no backup of my in box. It works fine with Firefox 3.6.3 and orca 2.30.1. I tried it with full navigation list turned on and off. Kenny On Fri, Jun 18, 2010 at 11:17:29PM +0100, Phillip Whiteside wrote: > Hi Alex, > > thanks ever so much for that. As I'm sure you realise, the robot testing is > only so good. Whilst I know that a site of engineers parts and drawings on > is not exactly a 'run of the mill site', if I can get that sort of site to > compliance I can say to to others that there is no excuse. I know I still > have more work to do on there, but at least I know I am making (slow) > progress :-) > > Thanks, > > Phill. > > On Fri, Jun 18, 2010 at 10:34 PM, Alex H. wrote: > > > Hi Phill, > > > > Everything seems to work correctly using NVDA, a screenreader for > > windows and using Mozilla Firefox 3.6.3. > > After Stop Press, it says text tutorials. I tried this with full > > navigation on and off. > > > > Thanks, > > > > Alex > > > > On 6/17/10, Phillip Whiteside wrote: > > > Hi, > > > > > > I currently use a system advised by > > > http://www.webaim.org/techniques/css/invisiblecontent/ for a hidden link > > on > > > a site designed to catch only harvesting robots, that being the *display: > > > none*. I use http://totalvalidator.com/ for validation, it came highly > > > recommended and is certainly more capable than the Rule508 'Cynthia Says' > > > one that comes with the Firefox WebDeveloper. I've had a quick 'chat' > > with > > > the team that are responsible for Total Advisor and they inform me that > > it > > > does not check for CSS compliance so is flagging up the hidden link as > > being > > > a problem, although it's abilities for checking other parts of WCAG / WAI > > > coding is exceptionally good and even picked up a couple of spelling > > > mistakes ;-) > > > > > > Could some one with a screen reader have a quick look at > > > http://mgjuddltd.co.uk and check that the reader does NOT read out > > "Hidden > > > Link - Security link only" which would be after the last navigation > > button > > > "Stop Press" in the navigation list on the left. (If you get chance, > > could > > > you also ensure that this behaviour is repeated when Full Navigation list > > is > > > toggled Off). > > > > > > Thanks in advance, > > > > > > Regards, > > > > > > Phill. > > > > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From phillw at phillw.net Sun Jun 20 12:52:29 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Sun, 20 Jun 2010 13:52:29 +0100 Subject: Screen Reader In-Reply-To: <20100620120601.GA2455@hittsjunk.net> References: <20100620120601.GA2455@hittsjunk.net> Message-ID: Hi Kenny, Bad news about your mail, thanks for taking the time to check it out. I'm pretty certain that I've gotten the whole site up to Level 2 (AA) compliance now, unless you guys and gals tell me something I've got wrong :-) Regards, Phill. On Sun, Jun 20, 2010 at 1:06 PM, Kenny Hitt wrote: > Hi. Sorry for replying to your reply. I lost my root > partition which contained /var/mail. Unfortunately, no backup of my > in box. > > It works fine with Firefox 3.6.3 and orca 2.30.1. > I tried it with full navigation list turned on and off. > > Kenny > > On Fri, Jun 18, 2010 at 11:17:29PM +0100, Phillip Whiteside wrote: > > Hi Alex, > > > > thanks ever so much for that. As I'm sure you realise, the robot testing > is > > only so good. Whilst I know that a site of engineers parts and drawings > on > > is not exactly a 'run of the mill site', if I can get that sort of site > to > > compliance I can say to to others that there is no excuse. I know I still > > have more work to do on there, but at least I know I am making (slow) > > progress :-) > > > > Thanks, > > > > Phill. > > > > On Fri, Jun 18, 2010 at 10:34 PM, Alex H. > wrote: > > > > > Hi Phill, > > > > > > Everything seems to work correctly using NVDA, a screenreader for > > > windows and using Mozilla Firefox 3.6.3. > > > After Stop Press, it says text tutorials. I tried this with full > > > navigation on and off. > > > > > > Thanks, > > > > > > Alex > > > > > > On 6/17/10, Phillip Whiteside wrote: > > > > Hi, > > > > > > > > I currently use a system advised by > > > > http://www.webaim.org/techniques/css/invisiblecontent/ for a hidden > link > > > on > > > > a site designed to catch only harvesting robots, that being the > *display: > > > > none*. I use http://totalvalidator.com/ for validation, it came > highly > > > > recommended and is certainly more capable than the Rule508 'Cynthia > Says' > > > > one that comes with the Firefox WebDeveloper. I've had a quick 'chat' > > > with > > > > the team that are responsible for Total Advisor and they inform me > that > > > it > > > > does not check for CSS compliance so is flagging up the hidden link > as > > > being > > > > a problem, although it's abilities for checking other parts of WCAG / > WAI > > > > coding is exceptionally good and even picked up a couple of spelling > > > > mistakes ;-) > > > > > > > > Could some one with a screen reader have a quick look at > > > > http://mgjuddltd.co.uk and check that the reader does NOT read out > > > "Hidden > > > > Link - Security link only" which would be after the last navigation > > > button > > > > "Stop Press" in the navigation list on the left. (If you get chance, > > > could > > > > you also ensure that this behaviour is repeated when Full Navigation > list > > > is > > > > toggled Off). > > > > > > > > Thanks in advance, > > > > > > > > Regards, > > > > > > > > Phill. > > > > > > > > > > -- > > Ubuntu-accessibility mailing list > > Ubuntu-accessibility at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -------------- next part -------------- An HTML attachment was scrubbed... URL: From splyt.lists at gmail.com Fri Jun 18 15:41:47 2010 From: splyt.lists at gmail.com (=?ISO-8859-1?Q?Marlon_Brand=E3o_de_Sousa?=) Date: Fri, 18 Jun 2010 12:41:47 -0300 Subject: [orca-list] Call for C++ coders make Orca work better with Firefox In-Reply-To: References: Message-ID: Hello, As a suggestiom, have you tried to talk to folks who coded the vbuffers to firefox for NVDA? I know that there are two diferent operating systems here and such and such, but if the firefox is coded the same way (I do think it is so cinse it wouldm be hard to maintain two diferent flavours of code), then perhaps a good part of the c++ v buffer implemented in NVDA could be used to process pages in firefox to orca. Sinse the two readers are written in python, chances are even greater that some code interchange might be possible. Marlon 2010/6/18, Bill Cox : > If there are C++ coders on this list who hate the problems when using > Orca with Firefox, please consider joining my Firefox debugging team. > We have many bugs to track down, and by myself, it will take many > months. Together, I bet we could fix Firefox in weeks. > > Feel free to reply to this post, or to me personally. > > Thanks, > Bill > _______________________________________________ > orca-list mailing list > orca-list at gnome.org > http://mail.gnome.org/mailman/listinfo/orca-list > Visit http://live.gnome.org/Orca for more information on Orca. > The manual is at > http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions > Netiquette Guidelines are at > http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines > Log bugs and feature requests at http://bugzilla.gnome.org > Find out how to help at http://live.gnome.org/Orca/HowCanIHelp > -- When you say "I wrote a program that crashed Windows," people just stare at you blankly and say "Hey, I got those with the system, for free." Linus Torvalds From felramfab at alum.us.es Mon Jun 21 10:05:06 2010 From: felramfab at alum.us.es (felramfab at alum.us.es) Date: Mon, 21 Jun 2010 12:05:06 +0200 Subject: VEDICS Speech Assistant Message-ID: Dear Sir/Madam, I'm doing some research about speech recognition systems specially designed for accesibility purposes and I would like to get the source code of Vedic Speech Assitant. Also, I'd be grateful if I could get some addtional information about this project. Thank you very much in advance. Yours sincerely, Felipe Ramón From waywardgeek at gmail.com Tue Jun 22 19:20:02 2010 From: waywardgeek at gmail.com (Bill Cox) Date: Tue, 22 Jun 2010 15:20:02 -0400 Subject: Speakup wont compile in Ubuntu Maverick Message-ID: I was able to fix two bugs, but the third has me confused still. First, /usr/bin/module-assistant needs to be modified to look in /usr/src/linux-headers-/include/generated, rather than include/linux to find utsrelease.h. Second, three speakup files need to include linux/slab.h to have access to kmalloc. These files are i18n.c, kobjects.c, and selection.c. This let's speakup compile. However, speakup.ko doesn't work because the Maverick kernel does not provide the k_handle function. Does anyone know how to enable the k_handle function in the Linux kernel? Bill From rberger at rogers.com Tue Jun 22 20:15:12 2010 From: rberger at rogers.com (Rick Berger) Date: Tue, 22 Jun 2010 16:15:12 -0400 Subject: how does one enable XEvIE in 9.10? Message-ID: <1277237712.2172.15.camel@sx2800> Hi, I need some extra audio feedback on some of the keyboards I use. I want to try something called "annoyme", just to see how it works and if I can tweak it for my needs. The only problem is that it requires XEvIE (X Event Interception Extension) to be enabled in your X configuration. This was done by change the Extensions section in your xorg.conf, but xorg.conf is no longer used in 9.10 and my attempts to create one have failed. Can anyone tell me how to enable XEvIE in Ubunu 9.10? Rick From brunogirin at gmail.com Tue Jun 22 20:38:22 2010 From: brunogirin at gmail.com (Bruno Girin) Date: Tue, 22 Jun 2010 21:38:22 +0100 Subject: how does one enable XEvIE in 9.10? In-Reply-To: <1277237712.2172.15.camel@sx2800> References: <1277237712.2172.15.camel@sx2800> Message-ID: <1277239102.1744.114.camel@nuuk> On Tue, 2010-06-22 at 16:15 -0400, Rick Berger wrote: > Hi, > > I need some extra audio feedback on some of the keyboards I use. I want > to try something called "annoyme", just to see how it works and if I can > tweak it for my needs. The only problem is that it requires XEvIE (X > Event Interception Extension) to be enabled in your X configuration. > This was done by change the Extensions section in your xorg.conf, but > xorg.conf is no longer used in 9.10 and my attempts to create one have > failed. Can anyone tell me how to enable XEvIE in Ubunu 9.10? Rick, There is a forum thread about the subject [1]. Basically, it all comes down to the fact that if you have an /etc/x11/xorg.conf file, the xserver will read it and use default settings for everything that is not specified in that file. So you should be able to create an xorg.conf that only includes XEvIE specific settings. [1] http://ubuntuforums.org/showthread.php?t=1260518 Bruno From phillw at phillw.net Tue Jun 22 22:25:30 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Tue, 22 Jun 2010 23:25:30 +0100 Subject: Fwd: http://mgjuddltd.co.uk compliance, In-Reply-To: References: Message-ID: ---------- Forwarded message ---------- From: Phillip Whiteside Date: Tue, Jun 22, 2010 at 11:23 PM Subject: http://mgjuddltd.co.uk compliance, To: Kenny Hitt , "Alex H." , Bob Trevithick Cc: ubuntu Hi Kenny, Alex & Bob, firstly, thank you for helping me on this one. I have re-written the site in terms of headers etc. along with changes to table descriptions / column descriptions. I have made so many changes that I ask if you would have a good check on the site and check that it is usable, in the "find parts" think of 'oil', 'spanner', 'filter' etc. I'm up to http://www.accessifyforum.com/viewtopic.php?t=16289 ::sigh:: at negative comments :-( Hi Mailing list, I'm dipping my toe back into the mailing list, after the last time went bad. If any of you have chance, please have a look. I'd also appreciate any views on whether I should code to WCAG version 1 or version 2 ? Has any one has worked out the answer to 'until' from the http://www.w3.org/TR/WAI-WEBCONTENT/#tech-divide-links where the word 'until' has its own entry as I use a programming routine that seems to work fine with readers, yet am told "until" the readers can handle them, i am not allowed to? I know that there is still a lot of for me to learn on the difference between a robot site saying it is okay and someone with using a screen reader, or any other accessibility access (Do shout now, while I am learning), I ask this time that only those who will give *constructive* criticism reply. I do need people who will do the manual testing against what the robots reply. Regards, Phill. -------------- next part -------------- An HTML attachment was scrubbed... URL: From PhillW at UK.VPOLink.com Tue Jun 22 22:23:03 2010 From: PhillW at UK.VPOLink.com (Phillip Whiteside) Date: Tue, 22 Jun 2010 23:23:03 +0100 Subject: http://mgjuddltd.co.uk compliance, Message-ID: Hi Kenny, Alex & Bob, firstly, thank you for helping me on this one. I have re-written the site in terms of headers etc. along with changes to table descriptions / column descriptions. I have made so many changes that I ask if you would have a good check on the site and check that it is usable, in the "find parts" think of 'oil', 'spanner', 'filter' etc. I'm up to http://www.accessifyforum.com/viewtopic.php?t=16289 ::sigh:: at negative comments :-( Hi Mailing list, I'm dipping my toe back into the mailing list, after the last time went bad. If any of you have chance, please have a look. I'd also appreciate any views on whether I should code to WCAG version 1 or version 2 ? Has any one has worked out the answer to 'until' from the http://www.w3.org/TR/WAI-WEBCONTENT/#tech-divide-links where the word 'until' has its own entry as I use a programming routine that seems to work fine with readers, yet am told "until" the readers can handle them, i am not allowed to? I know that there is still a lot of for me to learn on the difference between a robot site saying it is okay and someone with using a screen reader, or any other accessibility access (Do shout now, while I am learning), I ask this time that only those who will give *constructive* criticism reply. I do need people who will do the manual testing against what the robots reply. Regards, Phill. -------------- next part -------------- An HTML attachment was scrubbed... URL: From PhillW at UK.VPOLink.com Tue Jun 22 23:52:40 2010 From: PhillW at UK.VPOLink.com (Phillip Whiteside) Date: Wed, 23 Jun 2010 00:52:40 +0100 Subject: http://mgjuddltd.co.uk compliance, In-Reply-To: References: Message-ID: Hi, They're taking the urine now. 68 OL/OP007/1 68 68 69 69 [image: next problem] <#p2>[image: previous problem] <#p0>E836 <#E836> [WCAG v1 13.1 (AA)] Use different values for 'title' attributes with links that use the same link text: 69 - 69 Ermm. , and they have two different 'title' tags? the link text is different per item WTF? Confused @ phill Regards, Phill. On Tue, Jun 22, 2010 at 11:33 PM, Bob Trevithick wrote: > Hi, > > All I see so far is the issue with using the same text to link to > different places. Try running tv on: > > > http://mgjuddltd.co.uk/search.php?LookFor=chain&MyImpSize=NULL&MyMetSize=NULL > > Is there a page in particular that we should look at? I just did that > search at random. > > Best, > Bob > > On Tue, Jun 22, 2010 at 6:23 PM, Phillip Whiteside > wrote: > > Hi Kenny, Alex & Bob, > > firstly, thank you for helping me on this one. I have re-written the site > in > > terms of headers etc. along with changes to table descriptions / column > > descriptions. I have made so many changes that I ask if you would have a > > good check on the site and check that it is usable, in the "find parts" > > think of 'oil', 'spanner', 'filter' etc. > > I'm up to http://www.accessifyforum.com/viewtopic.php?t=16289 ::sigh:: > at > > negative comments :-( > > Hi Mailing list, > > I'm dipping my toe back into the mailing list, after the last time went > bad. > > If any of you have chance, please have a look. > > I'd also appreciate any views on whether I should code to WCAG version 1 > or > > version 2 ? > > Has any one has worked out the answer to 'until' from > > the http://www.w3.org/TR/WAI-WEBCONTENT/#tech-divide-links where the > word > > 'until' has its own entry as I use a programming routine that seems to > work > > fine with readers, yet am told "until" the readers can handle them, i am > not > > allowed to? > > I know that there is still a lot of for me to learn on the difference > > between a robot site saying it is okay and someone with using a screen > > reader, or any other accessibility access (Do shout now, while I am > > learning), I ask this time that only those who will give > > constructive criticism reply. I do need people who will do the manual > > testing against what the robots reply. > > Regards, > > Phill. > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob.trevithick at gmail.com Tue Jun 22 23:58:54 2010 From: bob.trevithick at gmail.com (Bob Trevithick) Date: Tue, 22 Jun 2010 19:58:54 -0400 Subject: http://mgjuddltd.co.uk compliance, In-Reply-To: References: Message-ID: There is one URL you are going to: href='display_part.php?PID=218' But there are multiple descriptions (titles) of that URL. In one case, you call it title='M.G. Judd Part Number' but in another case you call it title='Original Equipment Manufacturers Part Number'. It's the same URL, but you're potentially confusing the reader by giving it two different names. I think that's what they're getting at. Make scents? :) Bob On Tue, Jun 22, 2010 at 7:52 PM, Phillip Whiteside wrote: > > Hi, > They're taking the urine now. > > > 68 OL/OP007/1 > 68 > 68 > 69 > 69 E836 [WCAG v1 13.1 (AA)] Use different values for 'title' attributes with links that use the same link text: > > 69 - > 69 > > Ermm. , and they have two different 'title' tags? the link text is different per item WTF? > > Confused @ phill > Regards, > Phill. > On Tue, Jun 22, 2010 at 11:33 PM, Bob Trevithick wrote: >> >> Hi, >> >> All I see so far is the issue with using the same text to link to >> different places.  Try running tv on: >> >> http://mgjuddltd.co.uk/search.php?LookFor=chain&MyImpSize=NULL&MyMetSize=NULL >> >> Is there a page in particular that we should look at?  I just did that >> search at random. >> >> Best, >> Bob >> >> On Tue, Jun 22, 2010 at 6:23 PM, Phillip Whiteside >> wrote: >> > Hi Kenny, Alex & Bob, >> > firstly, thank you for helping me on this one. I have re-written the site in >> > terms of headers etc. along with changes to table descriptions / column >> > descriptions. I have made so many changes that I ask if you would have a >> > good check on the site and check that it is usable, in the "find parts" >> > think of 'oil', 'spanner', 'filter' etc. >> > I'm up to http://www.accessifyforum.com/viewtopic.php?t=16289 ::sigh:: at >> > negative comments :-( >> > Hi Mailing list, >> > I'm dipping my toe back into the mailing list, after the last time went bad. >> > If any of you have chance, please have a look. >> > I'd also appreciate any views on whether I should code to WCAG version 1 or >> > version 2 ? >> > Has any one has worked out the answer to 'until' from >> > the http://www.w3.org/TR/WAI-WEBCONTENT/#tech-divide-links where the word >> > 'until' has its own entry as I use a programming routine that seems to work >> > fine with readers, yet am told "until" the readers can handle them, i am not >> > allowed to? >> > I know that there is still a lot of for me to learn on the difference >> > between a robot site saying it is okay and someone with using a screen >> > reader, or any other accessibility access (Do shout now, while I am >> > learning), I ask this time that only those who will give >> > constructive criticism reply. I do need people who will do the manual >> > testing against what the robots reply. >> > Regards, >> > Phill. >> > >> > >> > >> > >> > > From PhillW at UK.VPOLink.com Wed Jun 23 00:20:25 2010 From: PhillW at UK.VPOLink.com (Phillip Whiteside) Date: Wed, 23 Jun 2010 01:20:25 +0100 Subject: http://mgjuddltd.co.uk compliance, In-Reply-To: References: Message-ID: Hi, according to the "rules" if I use the same link (href='display_part.php?PID=218') then I must must make a difference to it. So, if I choose, I can visually put in as many links per item, heck, I can even link it to the same image on section 2 ? Whatever the visual table displays, and it can be two different numbers between the MGJudd part number and the OEM part number they are the same item. The URL changes per item each has a unique PID, this is required by MySQL and means one part has one PID. Try entering 'stihl filter' into search and you will get the MGJ part number and the OEM one. They are the same item, so have only one entry on the database, with their unique ID number. Puzzled @ phillw On Wed, Jun 23, 2010 at 12:58 AM, Bob Trevithick wrote: > There is one URL you are going to: href='display_part.php?PID=218' > > But there are multiple descriptions (titles) of that URL. In one > case, you call it title='M.G. Judd Part Number' but in another case > you call it title='Original Equipment Manufacturers Part Number'. > > It's the same URL, but you're potentially confusing the reader by > giving it two different names. I think that's what they're getting > at. Make scents? :) > > Bob > > On Tue, Jun 22, 2010 at 7:52 PM, Phillip Whiteside > wrote: > > > > Hi, > > They're taking the urine now. > > > > href='display_part.php?PID=218'> > > 68 OL/OP007/1 > > 68 > > 68 > > 69 > > 69 E836 [WCAG v1 13.1 (AA)] Use different values for 'title' attributes > with links that use the same link text: > > > > 69 - > > 69 > > > > Ermm. , and they have two different 'title' tags? the link text is > different per item WTF? > > > > Confused @ phill > > Regards, > > Phill. > > On Tue, Jun 22, 2010 at 11:33 PM, Bob Trevithick < > bob.trevithick at gmail.com> wrote: > >> > >> Hi, > >> > >> All I see so far is the issue with using the same text to link to > >> different places. Try running tv on: > >> > >> > http://mgjuddltd.co.uk/search.php?LookFor=chain&MyImpSize=NULL&MyMetSize=NULL > >> > >> Is there a page in particular that we should look at? I just did that > >> search at random. > >> > >> Best, > >> Bob > >> > >> On Tue, Jun 22, 2010 at 6:23 PM, Phillip Whiteside > >> wrote: > >> > Hi Kenny, Alex & Bob, > >> > firstly, thank you for helping me on this one. I have re-written the > site in > >> > terms of headers etc. along with changes to table descriptions / > column > >> > descriptions. I have made so many changes that I ask if you would have > a > >> > good check on the site and check that it is usable, in the "find > parts" > >> > think of 'oil', 'spanner', 'filter' etc. > >> > I'm up to http://www.accessifyforum.com/viewtopic.php?t=16289 ::sigh:: > at > >> > negative comments :-( > >> > Hi Mailing list, > >> > I'm dipping my toe back into the mailing list, after the last time > went bad. > >> > If any of you have chance, please have a look. > >> > I'd also appreciate any views on whether I should code to WCAG version > 1 or > >> > version 2 ? > >> > Has any one has worked out the answer to 'until' from > >> > the http://www.w3.org/TR/WAI-WEBCONTENT/#tech-divide-links where the > word > >> > 'until' has its own entry as I use a programming routine that seems to > work > >> > fine with readers, yet am told "until" the readers can handle them, i > am not > >> > allowed to? > >> > I know that there is still a lot of for me to learn on the difference > >> > between a robot site saying it is okay and someone with using a screen > >> > reader, or any other accessibility access (Do shout now, while I am > >> > learning), I ask this time that only those who will give > >> > constructive criticism reply. I do need people who will do the manual > >> > testing against what the robots reply. > >> > Regards, > >> > Phill. > >> > > >> > > >> > > >> > > >> > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phillw at phillw.net Wed Jun 23 01:02:55 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Wed, 23 Jun 2010 02:02:55 +0100 Subject: http://mgjuddltd.co.uk compliance, In-Reply-To: References: Message-ID: The bounces are most likely caused by me using my default email account (vpolink) and not my phillw.net one The link on each part is the same? MGJudd Part No. = F0332 OEM Part No. = 4223 140 1800 The database number for them is 1451 on the database. So, the link is the same. Think of it this way, you require a part and you do not know the original part number, and you get dropped onto the mgjudd site, seems unlikely? Try putting in "ts400 parts illustrated" into google you will find the site there (no, I do not pay for it, I just want to make it okay for people and the google bot seems to like what I am doing). In my case, they will hear the MGJudd part number and the OEM part number, they are the same part and therefore have only one entry on the database. Does that make sense? Regards, Phill. On Wed, Jun 23, 2010 at 1:39 AM, Bob Trevithick wrote: > On Tue, Jun 22, 2010 at 8:20 PM, Phillip Whiteside > wrote: > > stihl filter > > When I search for that, I get a page that shows no errors at all. > because all of the links and link titles match up. > > But when I search for 'chain' I go to this page: > > > http://mgjuddltd.co.uk/search.php?LookFor=chain&MyImpSize=NULL&MyMetSize=NULL > > That one has the errors. > > You keep giving the title of the link as title='Original Equipment > Manufacturers Part Number', but you give different links. > > Think of it this way. Imagine that I have 5 links on my page, each > one entitled "Best place to vacation". One points to Hawaii, one > points to the Gulf of Mexico, one points to Puerto Rico, and so on. > This is what the rule is intended to prevent, I believe. The user > *hears* the same title, but depending on where it is, it takes him to > completely different places. Conversely, if the user saw a bunch of > different titles, but they all pointed to the same place, I think > you'd get the same warning. > > BTW, I got a bounce when I tried to reply-to-all, because I'm not a > member of that mailing list. So I removed it from the cc's on this > note. :) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phillw at phillw.net Wed Jun 23 02:17:24 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Wed, 23 Jun 2010 03:17:24 +0100 Subject: http://mgjuddltd.co.uk compliance, In-Reply-To: References: Message-ID: Hi, Yeah, I can code it so they have 12 digit random characters attached, the generation of the table headings and summaries is done via php interrogating the MySQL database, they will always be the same, however php can do random stuff. $MGJPartNo"; $this_is_silly= rand() echo " $MGJPartNo"; ?> Seems a real stupid way of doing things to me, but if it keeps the robots happy I'll do it provided the screen readers are okay with it. Phill. On Wed, Jun 23, 2010 at 2:28 AM, Bob Trevithick wrote: > On Tue, Jun 22, 2010 at 9:02 PM, Phillip Whiteside > wrote: > > The bounces are most likely caused by me using my default email account > > (vpolink) and not my phillw.net one > > I think the bounce said it was because I sent a note to a mailing list > that I am not a member of. Whoops. :) > > > The link on each part is the same? > > MGJudd Part No. = F0332 > > OEM Part No. = 4223 140 1800 > > The database number for them is 1451 on the database. So, the link is the > > same. > > Oh, I completely understand why you're doing it. It makes perfect > sense. It is, however, a violation of one of the accessibility rules. > That's all I'm saying. :) > > > Think of it this way, you require a part and you do not know the original > > part number, and you get dropped onto the mgjudd site, > > seems unlikely? Try putting in "ts400 parts illustrated" into google you > > will find the site there (no, I do not pay for it, I just want to make it > > okay for people and the google bot seems to like what I am doing). > > I did that, and TV then analyzed the page and found 35 E898 Level 'A' > errors. Well, really it's just 35 instances of the same error. > > > In my case, they will hear the MGJudd part number and the OEM part > number, > > they are the same part and therefore have only one entry on the database. > > Does that make sense? > > I completely understand, and your method makes perfect sense. It just > doesn't validate. If there were a way to make those titles unique, > you'd be all set. Like, perhaps number them, or do anything so you > don't fall into the trap of having different titles, which the screen > reader will pronounce, all leading to the same location. > > I'm just saying what TV says about it. I ran into the same problem > with pages of my own way back when, and it took me a while to > understand what the issue was. It's probably a mere technicality in > this case, which having a screen reader user look at the pages would > tell us. Or it might actually present a problem sometimes but not > others. It would be interesting to see if it's really an issue in > this particular case. > > Not a biggy, in any event, Phill.. so don't let it bum you out. It's > just a minor niggle. A technical violation, which we should be able > to figure out some way around with a little thought. > > Bob > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phillw at phillw.net Wed Jun 23 03:14:38 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Wed, 23 Jun 2010 04:14:38 +0100 Subject: http://mgjuddltd.co.uk compliance, In-Reply-To: References: Message-ID: hay, bob, you know me... quiet.... http://www.accessifyforum.com/viewtopic.php?t=16300 but that seems to be the way it is. I know there is someone on this listing who said that it was it was his loss when people who try, get fed up of negativity and just walk away. Well, I owe it to him and a couple of people to try and not let that happen to me again. There is an old saying "You're either with me, or against me" Some one forgot the "we" part of that, "We can get it to work" I don't know how many people will help, but I will keep trying as long as one person who will do so is there. This is not directed at you Bob, it is a request to others on the mailing list to help out. There is, out of 200+ books on computing in the central library exactly zero books on accessibilty, that makes it really difficult to try and learn this stuff. As you know I'm putting my experience onto the baby forum and when I get through this part of crash and burn from AAA to posssibly A rating I will put what I have learned on there. But, we need volunteers to let us know where our theory of screen readers is at odds with those who use them. More over, there are others who need people to test things out and let them know they are at least trying and help them. For those who feel hard done by, have a read of http://en.wikipedia.org/wiki/Simon_Weston It is not what he can not do, it is what he can do (I choose that as I remember from my youth what happened in that 'skirmish'). Regards, Phill. On Wed, Jun 23, 2010 at 3:30 AM, Bob Trevithick wrote: > Yeah, it does seem silly in this case. Maybe there's something to be > said for not slavishly following the accessibility rules. Get the > sense of what they're getting at, and see if they make sense for what > you're doing. > > In the U.S. I believe the law is that we have to meet Section 508 only > if we receive Federal monies. I think many people feel the > regulations leave quite a bit to be desired. I think it will be a > while before this becomes a science. > > I was wondering if you could number them sequentially down the page, > as 1) , 2) and so on. > > Heading for bed. Suggest you sleep on this before doing something you > think is silly. Maybe there's a way that makes sense. I can't think > of it off-hand. Maybe include something in the database query which > isn't actually used? > "href='display_part.php?PID=$PID¬_used=$not_used' and then just > keep incrementing the $not_used value? That way at least the screen > reader won't have to pronounce all of the nonsense. > > We'll come up with something. > > On Tue, Jun 22, 2010 at 10:17 PM, Phillip Whiteside > wrote: > > Hi, > > Yeah, I can code it so they have 12 digit random characters attached, the > > generation of the table headings and summaries is done via php > interrogating > > the MySQL database, they will always be the same, however php can do > random > > stuff. > > > $this_is_silly= rand() > > echo " $MGJPartNo"; > > $this_is_silly= rand() > > echo " $MGJPartNo"; > > ?> > > Seems a real stupid way of doing things to me, but if it keeps the robots > > happy I'll do it provided the screen readers are okay with it. > > Phill. > > > > > > On Wed, Jun 23, 2010 at 2:28 AM, Bob Trevithick < > bob.trevithick at gmail.com> > > wrote: > >> > >> On Tue, Jun 22, 2010 at 9:02 PM, Phillip Whiteside > >> wrote: > >> > The bounces are most likely caused by me using my default email > account > >> > (vpolink) and not my phillw.net one > >> > >> I think the bounce said it was because I sent a note to a mailing list > >> that I am not a member of. Whoops. :) > >> > >> > The link on each part is the same? > >> > MGJudd Part No. = F0332 > >> > OEM Part No. = 4223 140 1800 > >> > The database number for them is 1451 on the database. So, the link is > >> > the > >> > same. > >> > >> Oh, I completely understand why you're doing it. It makes perfect > >> sense. It is, however, a violation of one of the accessibility rules. > >> That's all I'm saying. :) > >> > >> > Think of it this way, you require a part and you do not know the > >> > original > >> > part number, and you get dropped onto the mgjudd site, > >> > seems unlikely? Try putting in "ts400 parts illustrated" into google > you > >> > will find the site there (no, I do not pay for it, I just want to make > >> > it > >> > okay for people and the google bot seems to like what I am doing). > >> > >> I did that, and TV then analyzed the page and found 35 E898 Level 'A' > >> errors. Well, really it's just 35 instances of the same error. > >> > >> > In my case, they will hear the MGJudd part number and the OEM part > >> > number, > >> > they are the same part and therefore have only one entry on the > >> > database. > >> > Does that make sense? > >> > >> I completely understand, and your method makes perfect sense. It just > >> doesn't validate. If there were a way to make those titles unique, > >> you'd be all set. Like, perhaps number them, or do anything so you > >> don't fall into the trap of having different titles, which the screen > >> reader will pronounce, all leading to the same location. > >> > >> I'm just saying what TV says about it. I ran into the same problem > >> with pages of my own way back when, and it took me a while to > >> understand what the issue was. It's probably a mere technicality in > >> this case, which having a screen reader user look at the pages would > >> tell us. Or it might actually present a problem sometimes but not > >> others. It would be interesting to see if it's really an issue in > >> this particular case. > >> > >> Not a biggy, in any event, Phill.. so don't let it bum you out. It's > >> just a minor niggle. A technical violation, which we should be able > >> to figure out some way around with a little thought. > >> > >> Bob > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony.sales at rncb.ac.uk Wed Jun 23 15:02:59 2010 From: tony.sales at rncb.ac.uk (Anthony Sales) Date: Wed, 23 Jun 2010 16:02:59 +0100 Subject: Vinux 3.0 USB and DVD Editions! Message-ID: On behalf of the Vinux Development Team I am happy to announce that final versions of the USB and DVD Editions of Vinux 3.0 are now available for download from the website: http://vinux.org.uk/downloads - There are three different versions of the USB Edition available - Two of these are simply images of an installed USB Vinux system which can easily be copied to a USB pendrive of an equal or greater size using the 'dd' command in Linux. The third version is a 'Universal' Edition which can be installed to any USB pendrive of 1GB or greater on Linux or Windows. Full instructions are available inside the zip file for Windows users. The DVD Edition is simply the standard version of Vinux 3.0 with all of the optional EasyInstall packages installed by default along with a few bonus packages. Please note that the DVD version contain proprietary multi-media codecs and some applications that are only accessible with magnification, but not with a screen-reader. This version is perhaps suitable for VI users who have sighted family members and would like an OS that all of the family can use. There are some direct download links below: Vinux 3.0 DVD http://sina.fi.ncsu.edu/Vinux-3.0-DVD.iso Vinux 3.0 USB 2G http://sina.fi.ncsu.edu/Vinux-3.0-2GB.img.xz Vinux 3.0 USB 4G http://sina.fi.ncsu.edu/Vinux-3.0-4GB.img.xz Vinux 3.0 USB Windows http://sina.fi.ncsu.edu/Vinux-3.0-USB-Win.zip -- drbongo Dig that crazy beat on the drums: The best is getting better! From pstowe at gmail.com Thu Jun 24 10:40:07 2010 From: pstowe at gmail.com (Penelope Stowe) Date: Thu, 24 Jun 2010 06:40:07 -0400 Subject: Scheduling Our Next Meeting Message-ID: Hiya, Sorry for being so behind this month, I've had some health related stuff come up that has heavily impacted my ability to get things done. Hopefully things have now turned the corner and will start to improve. As it's time for us to think about our next meeting, I'd like to propose meeting June 30 at 21h UTC. Does this work for those interested? Thanks! Penelope From pstowe at gmail.com Thu Jun 24 12:36:55 2010 From: pstowe at gmail.com (Penelope Stowe) Date: Thu, 24 Jun 2010 08:36:55 -0400 Subject: Personas Survey Creation Message-ID: Hiya, Alan Bell and I have been working on the questionnaire that we'll distribute to gather the information to create the accessibility personas. What we have so far is up at http://pad.ubuntu-uk.org/OGCR7tZiNX and we'd really appreciate any feedback and/or additions to it. We're aiming to have the survey ready by June 30th so that's just under a week to get everything done. Please take a look and let us know what you think! I'm trying to keep to open questions to encourage people to give us as many details as possible. Thanks, Penelope From mainstreaming at camara.ie Thu Jun 24 15:57:02 2010 From: mainstreaming at camara.ie (Eleanor Smyth) Date: Thu, 24 Jun 2010 16:57:02 +0100 Subject: Orca/linux accessibility teaching material Message-ID: Hello! Camara (www.camara.ie) refurbishes old computers, sends them out to Africa and sets up learning centres. At the moment we are trying to make our Linux computers more accesible for students that are living with disabilities. After much debate, we decided to stick with the accessibity features already on Linux. The computers, already in Africa have various versions of Ubuntu, this means that Ocra functions to various degrees in the schools. We discovered that the speech on older versions of ocra was very fast and difficult to understand So, we want to update ocra by sending out a C.D with the latest version of orca to the schools in Africa and update orca when refurbishing the computers going out. With that done, we need to train our teachers on how to update orca (for the computers already sent out) and write up a manual on how to use ocra within the classroom. This is where we'll have to call upon some help. Setting up the accessibity features is difficult for someone who has very basic computer skills. Are there any good tutorials (audio and visual) out there that we could use? Any additional info that we should be aware of? All comments/material will be much appreciated. Kind Regards, Eleanor -- Eleanor Smyth Disability Officer Camara E-mail: mainstreaming at camara.ie Camara Education The Digital Hub, 10-13 Thomas Street, Dublin 8. T: 0861217893 www.camara.ie -------------- next part -------------- An HTML attachment was scrubbed... URL: From waywardgeek at gmail.com Thu Jun 24 16:36:43 2010 From: waywardgeek at gmail.com (Bill Cox) Date: Thu, 24 Jun 2010 12:36:43 -0400 Subject: Orca/linux accessibility teaching material In-Reply-To: References: Message-ID: Hi, Eleanor. If you are going to install the newest version of Ubuntu on these machines, you get a pretty decent setup if you enable an "accessible" install. You press space at the first screen to get to a text menu, F5 to open accessibility options, and 3 to select the Orca screen reader. It actually does a bunch of other stuff, too, and makes the machine boot talking. Default accessiblity in Ubuntu Lucid is actually pretty good. I'll also put in a plug for Vinux 3.0, which is basically Ubuntu Lucid with some tweaks to make it work a bit better with Orca, and with a console screen reader. Bill On Thu, Jun 24, 2010 at 11:57 AM, Eleanor Smyth wrote: > Hello! > > Camara (www.camara.ie) refurbishes old computers, sends them out to Africa > and sets up learning centres. At the moment we are trying to make our Linux > computers more accesible for students that are living with disabilities. > After much debate, we decided to stick with the accessibity features already > on Linux. > > The computers, already in Africa have various versions of Ubuntu, this means > that Ocra functions to various degrees in the schools. We discovered that > the speech on older versions of ocra was very fast and difficult to > understand  So, we want to update ocra by sending out a C.D with the latest > version of orca to the schools in Africa and update orca when refurbishing > the computers going out. > > With that done, we need to train our teachers on how to update orca (for the > computers already sent out) and write up a manual on how to use ocra within > the classroom. This is where we'll have to call upon some help. Setting up > the accessibity features is difficult for someone who has very basic > computer skills. > > Are there any good tutorials (audio and visual) out there that we could use? > Any additional info that we should be aware of?  All comments/material will > be much appreciated. > > Kind Regards, > Eleanor > > > > -- > Eleanor Smyth > Disability Officer Camara > E-mail: mainstreaming at camara.ie > > Camara Education > The Digital Hub, 10-13 Thomas Street, Dublin 8. > T: 0861217893 > www.camara.ie > > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > > From alan.bell at theopenlearningcentre.com Thu Jun 24 16:41:10 2010 From: alan.bell at theopenlearningcentre.com (Alan Bell) Date: Thu, 24 Jun 2010 17:41:10 +0100 Subject: Orca/linux accessibility teaching material In-Reply-To: References: Message-ID: <1277397670.3906.2.camel@tributary> sounds like a good topic for a screencast http://screencasts.ubuntu.com I haven't done one of these myself, but it sounds like fun to do. Alan. On Thu, 2010-06-24 at 16:57 +0100, Eleanor Smyth wrote: > Hello! > > Camara (www.camara.ie) refurbishes old computers, sends them out to > Africa and sets up learning centres. At the moment we are trying to > make our Linux computers more accesible for students that are living > with disabilities. After much debate, we decided to stick with the > accessibity features already on Linux. > > The computers, already in Africa have various versions of Ubuntu, this > means that Ocra functions to various degrees in the schools. We > discovered that the speech on older versions of ocra was very fast and > difficult to understand So, we want to update ocra by sending out a > C.D with the latest version of orca to the schools in Africa and > update orca when refurbishing the computers going out. > > With that done, we need to train our teachers on how to update orca > (for the computers already sent out) and write up a manual on how to > use ocra within the classroom. This is where we'll have to call upon > some help. Setting up the accessibity features is difficult for > someone who has very basic computer skills. > > Are there any good tutorials (audio and visual) out there that we > could use? Any additional info that we should be aware of? All > comments/material will be much appreciated. > > Kind Regards, > Eleanor > > > > -- > Eleanor Smyth > Disability Officer Camara > E-mail: mainstreaming at camara.ie > > Camara Education > The Digital Hub, 10-13 Thomas Street, Dublin 8. > T: 0861217893 > www.camara.ie > > From brunogirin at gmail.com Thu Jun 24 19:36:40 2010 From: brunogirin at gmail.com (Bruno Girin) Date: Thu, 24 Jun 2010 20:36:40 +0100 Subject: Personas Survey Creation In-Reply-To: References: Message-ID: <1277408200.1609.12.camel@nuuk> On Thu, 2010-06-24 at 08:36 -0400, Penelope Stowe wrote: > Hiya, > > Alan Bell and I have been working on the questionnaire that we'll > distribute to gather the information to create the accessibility > personas. What we have so far is up at > http://pad.ubuntu-uk.org/OGCR7tZiNX and we'd really appreciate any > feedback and/or additions to it. Hi Penelope, What about starting with the personas introduced by Mark Pilgrim in Dive into Accessibility [1]? Although the book targets web designers, the personas are also valid for desktop use. As a non-disabled software specialist who tries to include accessibility in my projects, I have found the personas in that book very useful to understand challenges faced by disabled users and how I could help alleviate them. Furthermore, this book is published under the GNU Free Documentation License [2] so there should be no problem in using its content. [1] http://diveintoaccessibility.org/ [2] http://diveintoaccessibility.org/terms_of_use.html Bruno From phillw at phillw.net Thu Jun 24 20:17:54 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Thu, 24 Jun 2010 21:17:54 +0100 Subject: Personas Survey Creation In-Reply-To: <1277408200.1609.12.camel@nuuk> References: <1277408200.1609.12.camel@nuuk> Message-ID: Hi Bruno, I'm just having a read of the article you mentioned, there is a dead end link at http://diveintoaccessibility.org/day_6_choosing_a_doctype.html The dead link being at the bottom, A List Apart: Fixing Your Site With The Right DOCTYPE I don't know if you're in contact with the author? Regards, Phill. On Thu, Jun 24, 2010 at 8:36 PM, Bruno Girin wrote: > On Thu, 2010-06-24 at 08:36 -0400, Penelope Stowe wrote: > > Hiya, > > > > Alan Bell and I have been working on the questionnaire that we'll > > distribute to gather the information to create the accessibility > > personas. What we have so far is up at > > http://pad.ubuntu-uk.org/OGCR7tZiNX and we'd really appreciate any > > feedback and/or additions to it. > > Hi Penelope, > > What about starting with the personas introduced by Mark Pilgrim in Dive > into Accessibility [1]? Although the book targets web designers, the > personas are also valid for desktop use. As a non-disabled software > specialist who tries to include accessibility in my projects, I have > found the personas in that book very useful to understand challenges > faced by disabled users and how I could help alleviate them. > Furthermore, this book is published under the GNU Free Documentation > License [2] so there should be no problem in using its content. > > [1] http://diveintoaccessibility.org/ > [2] http://diveintoaccessibility.org/terms_of_use.html > > Bruno > > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -------------- next part -------------- An HTML attachment was scrubbed... URL: From themuso at ubuntu.com Thu Jun 24 22:58:39 2010 From: themuso at ubuntu.com (Luke Yelavich) Date: Fri, 25 Jun 2010 08:58:39 +1000 Subject: Scheduling Our Next Meeting In-Reply-To: References: Message-ID: <20100624225839.GC2214@strigy.yelavich.home> On Thu, Jun 24, 2010 at 08:40:07PM EST, Penelope Stowe wrote: > Hiya, > > Sorry for being so behind this month, I've had some health related > stuff come up that has heavily impacted my ability to get things done. > Hopefully things have now turned the corner and will start to improve. > > As it's time for us to think about our next meeting, I'd like to > propose meeting June 30 at 21h UTC. Does this work for those > interested? I can make this time. Luke From cjk at teamcharliesangels.com Fri Jun 25 00:22:54 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Thu, 24 Jun 2010 18:22:54 -0600 Subject: Scheduling Our Next Meeting In-Reply-To: References: Message-ID: <20100624182254.40f116a5@teamcharliesangels.com> On Thu, 24 Jun 2010 06:40:07 -0400 Penelope Stowe wrote: > Hiya, > > Sorry for being so behind this month, I've had some health related > stuff come up that has heavily impacted my ability to get things done. > Hopefully things have now turned the corner and will start to improve. > > As it's time for us to think about our next meeting, I'd like to > propose meeting June 30 at 21h UTC. Does this work for those > interested? > > Thanks! > Penelope > Sounds good to me. I am in the process of moving, and hope to be back on line by then. -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From mj at mjw.se Fri Jun 25 15:29:39 2010 From: mj at mjw.se (mattias jonsson) Date: Fri, 25 Jun 2010 17:29:39 +0200 Subject: Brltty? Message-ID: <000501cb147b$3a0aa460$d316e255@mj> Can i install ubuntu 10.04 with brltty like in 8.10 and 8.04 From rao.nischal at gmail.com Sat Jun 26 12:14:47 2010 From: rao.nischal at gmail.com (Nischal Rao) Date: Sat, 26 Jun 2010 17:44:47 +0530 Subject: VEDICS Speech Assistant In-Reply-To: References: Message-ID: Hi Felipe, you can find the source code of VEDICS at http://sourceforge.net/projects/vedics/develop On Mon, Jun 21, 2010 at 3:35 PM, wrote: > Dear Sir/Madam, > > I'm doing some research about speech recognition systems specially designed > for accesibility purposes and I would like to get the source code of Vedic > Speech Assitant. Also, I'd be grateful if I could get some addtional > information about this project. > > Thank you very much in advance. > > Yours sincerely, > > Felipe Ramón > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -- regards, Nischal E Rao blogs.sun.com/nischal Join RVCE OSUM at http://osum.sun.com/group/rvceosum -------------- next part -------------- An HTML attachment was scrubbed... URL: From supermalavox at gmail.com Sun Jun 27 03:36:22 2010 From: supermalavox at gmail.com (=?iso-8859-1?Q?Andr=E9_L._Baldo?=) Date: Sun, 27 Jun 2010 00:36:22 -0300 Subject: Introducing myself and asking about an accessible midi composing software Message-ID: Hello, My name is André Baldo, and I am from Brazil. It is a pleasure to be a member of the Ubuntu Accessibility list. Well, here comes my first question: I have just started to use Ubuntu a few days ago and, in general, am liking it, although I am still adapting to it. One thing I haven't found is an accessible midi composing software such as QWS for Windows or some other program that even not being prepared for blind people, has ways to command it via keyboard. Any suggestions? Thanks, André. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabiano at linuxacessivel.org Sun Jun 27 05:36:17 2010 From: fabiano at linuxacessivel.org (Fabiano Garcia Fonseca) Date: Sun, 27 Jun 2010 02:36:17 -0300 Subject: accessible login Message-ID: <4C26E351.5000906@linuxacessivel.org> Hi In an installation of Ubuntu without activation of Orca by F5 key, can I have the login window with Orca talking about? Thanks -- Fabiano garcia Fonseca Linux user #448759 - Ubuntu User #15701 www.linuxacessivel.org e-mail/MSN: fabiano at linuxacessivel.org Skype: fabianonh5 From kinouchou at gmail.com Fri Jun 25 09:54:16 2010 From: kinouchou at gmail.com (kinouchou) Date: Fri, 25 Jun 2010 11:54:16 +0200 Subject: Scheduling Our Next Meeting In-Reply-To: <20100624182254.40f116a5@teamcharliesangels.com> References: <20100624182254.40f116a5@teamcharliesangels.com> Message-ID: Hello, It's ok for me kinouchou 2010/6/25 Charlie Kravetz > On Thu, 24 Jun 2010 06:40:07 -0400 > Penelope Stowe wrote: > > > Hiya, > > > > Sorry for being so behind this month, I've had some health related > > stuff come up that has heavily impacted my ability to get things done. > > Hopefully things have now turned the corner and will start to improve. > > > > As it's time for us to think about our next meeting, I'd like to > > propose meeting June 30 at 21h UTC. Does this work for those > > interested? > > > > Thanks! > > Penelope > > > > Sounds good to me. I am in the process of moving, and hope to be back > on line by then. > > -- > Charlie Kravetz > Linux Registered User Number 425914 [http://counter.li.org/] > Never let anyone steal your DREAM. [http://keepingdreams.com] > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -------------- next part -------------- An HTML attachment was scrubbed... URL: From esj at harvee.org Mon Jun 28 18:39:59 2010 From: esj at harvee.org (Eric S. Johansson) Date: Mon, 28 Jun 2010 14:39:59 -0400 Subject: Scheduling Our Next Meeting In-Reply-To: References: Message-ID: <4C28EC7F.6080706@harvee.org> On 6/24/2010 6:40 AM, Penelope Stowe wrote > As it's time for us to think about our next meeting, I'd like to > propose meeting June 30 at 21h UTC. Does this work for those > interested? > works here, From pstowe at gmail.com Wed Jun 30 14:11:49 2010 From: pstowe at gmail.com (Penelope Stowe) Date: Wed, 30 Jun 2010 10:11:49 -0400 Subject: Personas Survey Creation In-Reply-To: References: Message-ID: If you have any more feedback on the survey please get it in within the next 5 hours or so (so by 19:00 UTC). I'd like to get the questions finalized prior to today's meeting. Feedback can be put into the etherpad as well as e-mailed to the list (or discussed on IRC, etc.) Thanks, Penelope