E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 10 (In chronological order)

From: Lucy Greco
Date: Thu, Aug 22 2013 11:27AM
Subject: testing and Firefox versus IE
No previous message | Next message →

Hello:
I was just sent some simple pages to check and found something very
strange. I started the testing and Firefox and was quite concerned
because these pages were just simple text with a few links. However jaws
continually read clickable throughout the page in Firefox and not at all
in IE. From what I can tell there's nothing going on in the source code
to do this. Any other testers out there got an idea. I can't share these
pages as they are internal currently or I would. Thanks Lucy

Lucia Greco
Web Access Analyst
IST-Campus Technology Services
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces

From: Humbert, Joseph A
Date: Thu, Aug 22 2013 11:49AM
Subject: Re: testing and Firefox versus IE
← Previous message | Next message →

Hi Lucy,

There are probably JavaScript event handlers on high level (parent) container elements of the content. This would be found in the JavaScript files in the source not the HTML source. Visual Event (http://www.sprymedia.co.uk/article/visual+event+2) is a bookmarklet that may visually identify the effected regions and indicate where in the source code the offending JavaScript files are located. This tool is not very screen reading software friendly. Manually you could look at all the files attached to the HTML source and search for event handlers (e.g., ".click(function()" for jQuery). Hope this helps. Thankx.

Sincerely,

Joe

Joe Humbert, Accessibility Specialist
UITS Adaptive Technology and Accessibility Centers
Indiana University, Indianapolis and Bloomington
535 W Michigan St. IT210 F
Indianapolis, IN 46202
Office Phone: (317) 274-4378
= EMAIL ADDRESS REMOVED =
http://iuadapts.Indiana.edu/


-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Lucy Greco
Sent: Thursday, August 22, 2013 1:27 PM
To: WebAIM Discussion List
Subject: [WebAIM] testing and Firefox versus IE

Hello:
I was just sent some simple pages to check and found something very strange. I started the testing and Firefox and was quite concerned because these pages were just simple text with a few links. However jaws continually read clickable throughout the page in Firefox and not at all in IE. From what I can tell there's nothing going on in the source code to do this. Any other testers out there got an idea. I can't share these pages as they are internal currently or I would. Thanks Lucy

Lucia Greco
Web Access Analyst
IST-Campus Technology Services
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces

From: Bryan Garaventa
Date: Thu, Aug 22 2013 11:34AM
Subject: Re: testing and Firefox versus IE
← Previous message | Next message →

This happens when there is a click handler on a container element higher up
in the DOM tree.

This often happens within frameworks and libraries that assign placeholder
functions for customization, which is necessary to handle event bubbling.

----- Original Message -----
From: "Lucy Greco" < = EMAIL ADDRESS REMOVED = >
To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
Sent: Thursday, August 22, 2013 10:27 AM
Subject: [WebAIM] testing and Firefox versus IE


> Hello:
> I was just sent some simple pages to check and found something very
> strange. I started the testing and Firefox and was quite concerned
> because these pages were just simple text with a few links. However jaws
> continually read clickable throughout the page in Firefox and not at all
> in IE. From what I can tell there's nothing going on in the source code
> to do this. Any other testers out there got an idea. I can't share these
> pages as they are internal currently or I would. Thanks Lucy
>
> Lucia Greco
> Web Access Analyst
> IST-Campus Technology Services
> University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
> > >

From: Birkir R. Gunnarsson
Date: Thu, Aug 22 2013 12:20PM
Subject: Re: testing and Firefox versus IE
← Previous message | Next message →

Jaws seems to incorrectly interpret any content that sits inside a div
(even when it is just a div with a CSS class assigned to it for layout
purposes) as "clickable" in Firefox.
It does not do this in IE.
I am going to create an issue in the FS beta tester track (if one does
not exist already).
Cheers
-B
Birkir Gunnarsson
Accessibility Subject Matter Expert | Deque Systems

On 8/22/13, Bryan Garaventa < = EMAIL ADDRESS REMOVED = > wrote:
> This happens when there is a click handler on a container element higher up
>
> in the DOM tree.
>
> This often happens within frameworks and libraries that assign placeholder
> functions for customization, which is necessary to handle event bubbling.
>
> ----- Original Message -----
> From: "Lucy Greco" < = EMAIL ADDRESS REMOVED = >
> To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
> Sent: Thursday, August 22, 2013 10:27 AM
> Subject: [WebAIM] testing and Firefox versus IE
>
>
>> Hello:
>> I was just sent some simple pages to check and found something very
>> strange. I started the testing and Firefox and was quite concerned
>> because these pages were just simple text with a few links. However jaws
>> continually read clickable throughout the page in Firefox and not at all
>> in IE. From what I can tell there's nothing going on in the source code
>> to do this. Any other testers out there got an idea. I can't share
>> these
>> pages as they are internal currently or I would. Thanks Lucy
>>
>> Lucia Greco
>> Web Access Analyst
>> IST-Campus Technology Services
>> University of California, Berkeley
>> (510) 289-6008 skype: lucia1-greco
>> http://webaccess.berkeley.edu
>> Follow me on twitter @accessaces
>> >> >> >
> > > >

From: David Farough
Date: Thu, Aug 22 2013 12:23PM
Subject: Re: testing and Firefox versus IE
← Previous message | Next message →

Hi Lucy:
this is a Jaws setting which can be modified by the user.
Unfortunately most users will be unaware of this or where to find the
setting. I do not know why this does not occur with Internet explorer,
but it may be due to different jaws scripts being used for the different
browsers. it might also be due to differences in the information
provided to JAWS by the browser.

You can change the way Jaws handles such information by doing the
following.

1. press Jawskey (either insert or capslock) plus 6 on the top row of
numbers on the keyboard (not 6 on the number pad) to open settings
centre.
2. type Speech in the search box and then arrow down to "speech and
sound schemes"
3. press right arrow to open and then arrow down to modify schemes and
press space.

Here you will be able to view available schemes and modify any number
of settings that will dictate how Jaws responds to different controls
web content etc.

activate the modify scheme button to modify settings in the active
speech and sound scheme.

This opens a multi tab dialogue which provides settings available for
various content types.

For your purposes look at the HTML tab. particularly at "onclick".

Options are:
designate a sound to be played when this gains focus;
speak the attribute and then Jaws says "clickable" or any other text
you prefer;
Ignore to provide no feedback;

This is quite a complex feature and is not easily discoverable. There
is an entire module dedicated to the speech and sounds manager in the
training material provided by Freedom Scientific. It is my experience
that most people are not aware of how this can be used to enhance their
user experience. To obtain more information on this feature , go to the
Jaws help menu and then select training. then select Speech and sounds
manager from the list of files available. If this is not installed on
your machine, it will be downloaded and installed automatically.


David Farough
Application Accessibility Coordinator/coordonateur de l'accessibilité
Information Technology Services Directorate /
Direction des services d'information technologiques
Public Service Commission / Commission de la fonction publique
Email / Courriel: = EMAIL ADDRESS REMOVED =
Tel. / Tél: (613) 992-2779

From: Lucy Greco
Date: Thu, Aug 22 2013 12:28PM
Subject: Re: testing and Firefox versus IE
← Previous message | Next message →

Hello David:
I can't turn it off because I am testing many different sites that
actually need it on. But in this case I need to find a way to tell the devs
why it is happening and how to make it stop. But thanks that was a good
description of how to turn it on and off Lucy

Lucia Greco
Web Access Analyst
IST-Campus Technology Services
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of David Farough
Sent: Thursday, August 22, 2013 11:23 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] testing and Firefox versus IE

Hi Lucy:
this is a Jaws setting which can be modified by the user.
Unfortunately most users will be unaware of this or where to find the
setting. I do not know why this does not occur with Internet explorer,
but it may be due to different jaws scripts being used for the different
browsers. it might also be due to differences in the information
provided to JAWS by the browser.

You can change the way Jaws handles such information by doing the
following.

1. press Jawskey (either insert or capslock) plus 6 on the top row of
numbers on the keyboard (not 6 on the number pad) to open settings
centre.
2. type Speech in the search box and then arrow down to "speech and
sound schemes"
3. press right arrow to open and then arrow down to modify schemes and
press space.

Here you will be able to view available schemes and modify any number
of settings that will dictate how Jaws responds to different controls
web content etc.

activate the modify scheme button to modify settings in the active
speech and sound scheme.

This opens a multi tab dialogue which provides settings available for
various content types.

For your purposes look at the HTML tab. particularly at "onclick".

Options are:
designate a sound to be played when this gains focus;
speak the attribute and then Jaws says "clickable" or any other text
you prefer;
Ignore to provide no feedback;

This is quite a complex feature and is not easily discoverable. There
is an entire module dedicated to the speech and sounds manager in the
training material provided by Freedom Scientific. It is my experience
that most people are not aware of how this can be used to enhance their
user experience. To obtain more information on this feature , go to the
Jaws help menu and then select training. then select Speech and sounds
manager from the list of files available. If this is not installed on
your machine, it will be downloaded and installed automatically.







David Farough
Application Accessibility Coordinator/coordonateur de l'accessibilité
Information Technology Services Directorate /
Direction des services d'information technologiques
Public Service Commission / Commission de la fonction publique
Email / Courriel: = EMAIL ADDRESS REMOVED =
Tel. / Tél: (613) 992-2779

>
This e-mail message is intended for the named recipient(s) and may
contain information that is privileged, confidential and/or exempt from
disclosure under applicable law. Unauthorized disclosure, copying or
re-transmission is prohibited. If you are not a named recipient or not
authorized by the named recipient(s), or if you have received this
e-mail in error, then please notify the sender immediately and delete
the message and any copies.
>
Ce courriel est destiné exclusivement au destinataire mentionné en titre
et peut contenir de l'information privilégiée, confidentielle ou
soustraite à la communication aux termes des lois applicables. Toute
divulgation non autorisée, toute reproduction ou réacheminement est
interdit. Si vous n'êtes pas le destinataire de ce courriel, ou n'êtes
pas autorisé par le destinataire visé, ou encore, si vous l'avez reçu
par erreur, veuillez le mentionner immédiatement à l'expéditeur et
supprimer le courriel et les copies.

From: Lucy Greco
Date: Thu, Aug 22 2013 12:29PM
Subject: Re: testing and Firefox versus IE
← Previous message | Next message →

These are all leads I will follow each of them and get back to you when I
find out what it was happening in this case thanks to all of you

Lucia Greco
Web Access Analyst
IST-Campus Technology Services
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R.
Gunnarsson
Sent: Thursday, August 22, 2013 11:21 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] testing and Firefox versus IE

Jaws seems to incorrectly interpret any content that sits inside a div
(even when it is just a div with a CSS class assigned to it for layout
purposes) as "clickable" in Firefox.
It does not do this in IE.
I am going to create an issue in the FS beta tester track (if one does
not exist already).
Cheers
-B
Birkir Gunnarsson
Accessibility Subject Matter Expert | Deque Systems

On 8/22/13, Bryan Garaventa < = EMAIL ADDRESS REMOVED = > wrote:
> This happens when there is a click handler on a container element higher
up
>
> in the DOM tree.
>
> This often happens within frameworks and libraries that assign
placeholder
> functions for customization, which is necessary to handle event
bubbling.
>
> ----- Original Message -----
> From: "Lucy Greco" < = EMAIL ADDRESS REMOVED = >
> To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
> Sent: Thursday, August 22, 2013 10:27 AM
> Subject: [WebAIM] testing and Firefox versus IE
>
>
>> Hello:
>> I was just sent some simple pages to check and found something very
>> strange. I started the testing and Firefox and was quite concerned
>> because these pages were just simple text with a few links. However
jaws
>> continually read clickable throughout the page in Firefox and not at
all
>> in IE. From what I can tell there's nothing going on in the source
code
>> to do this. Any other testers out there got an idea. I can't share
>> these
>> pages as they are internal currently or I would. Thanks Lucy
>>
>> Lucia Greco
>> Web Access Analyst
>> IST-Campus Technology Services
>> University of California, Berkeley
>> (510) 289-6008 skype: lucia1-greco
>> http://webaccess.berkeley.edu
>> Follow me on twitter @accessaces
>> >> >> >
> > > >

From: Bryan Garaventa
Date: Thu, Aug 22 2013 3:18PM
Subject: Re: testing and Firefox versus IE
← Previous message | Next message →

Have you tested it using the JAWS build released today? I heard that this
was just fixed.

----- Original Message -----
From: "Lucy Greco" < = EMAIL ADDRESS REMOVED = >
To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
Sent: Thursday, August 22, 2013 11:29 AM
Subject: Re: [WebAIM] testing and Firefox versus IE


> These are all leads I will follow each of them and get back to you when I
> find out what it was happening in this case thanks to all of you
>
> Lucia Greco
> Web Access Analyst
> IST-Campus Technology Services
> University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R.
> Gunnarsson
> Sent: Thursday, August 22, 2013 11:21 AM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] testing and Firefox versus IE
>
> Jaws seems to incorrectly interpret any content that sits inside a div
> (even when it is just a div with a CSS class assigned to it for layout
> purposes) as "clickable" in Firefox.
> It does not do this in IE.
> I am going to create an issue in the FS beta tester track (if one does
> not exist already).
> Cheers
> -B
> Birkir Gunnarsson
> Accessibility Subject Matter Expert | Deque Systems
>
> On 8/22/13, Bryan Garaventa < = EMAIL ADDRESS REMOVED = > wrote:
>> This happens when there is a click handler on a container element higher
> up
>>
>> in the DOM tree.
>>
>> This often happens within frameworks and libraries that assign
> placeholder
>> functions for customization, which is necessary to handle event
> bubbling.
>>
>> ----- Original Message -----
>> From: "Lucy Greco" < = EMAIL ADDRESS REMOVED = >
>> To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
>> Sent: Thursday, August 22, 2013 10:27 AM
>> Subject: [WebAIM] testing and Firefox versus IE
>>
>>
>>> Hello:
>>> I was just sent some simple pages to check and found something very
>>> strange. I started the testing and Firefox and was quite concerned
>>> because these pages were just simple text with a few links. However
> jaws
>>> continually read clickable throughout the page in Firefox and not at
> all
>>> in IE. From what I can tell there's nothing going on in the source
> code
>>> to do this. Any other testers out there got an idea. I can't share
>>> these
>>> pages as they are internal currently or I would. Thanks Lucy
>>>
>>> Lucia Greco
>>> Web Access Analyst
>>> IST-Campus Technology Services
>>> University of California, Berkeley
>>> (510) 289-6008 skype: lucia1-greco
>>> http://webaccess.berkeley.edu
>>> Follow me on twitter @accessaces
>>> >>> >>> >>
>> >> >> >>
> > > > > >

From: Michael Moore
Date: Fri, Aug 23 2013 10:22AM
Subject: Re: testing and Firefox versus IE
← Previous message | Next message →

Here is an except from an email that Eric Damery sent to the JAWS users
list:

"Mozilla Firefox
*Addressed a customer reported issue where JAWS was saying "clickable" at
the end of each line while reading.
*Improved navigating tree views on Web pages and announcing the expanded
and collapsed state of items."

The update that you need is JAWS 14.0.6004. I have been running it for
about a day and it seems to be working fine. The previous update seemed a
little buggy to me.


On Thu, Aug 22, 2013 at 4:18 PM, Bryan Garaventa <
= EMAIL ADDRESS REMOVED = > wrote:

> Have you tested it using the JAWS build released today? I heard that this
> was just fixed.
>
> ----- Original Message -----
> From: "Lucy Greco" < = EMAIL ADDRESS REMOVED = >
> To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
> Sent: Thursday, August 22, 2013 11:29 AM
> Subject: Re: [WebAIM] testing and Firefox versus IE
>
>
> > These are all leads I will follow each of them and get back to you when
> I
> > find out what it was happening in this case thanks to all of you
> >
> > Lucia Greco
> > Web Access Analyst
> > IST-Campus Technology Services
> > University of California, Berkeley
> > (510) 289-6008 skype: lucia1-greco
> > http://webaccess.berkeley.edu
> > Follow me on twitter @accessaces
> >
> >
> > -----Original Message-----
> > From: = EMAIL ADDRESS REMOVED =
> > [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R.
> > Gunnarsson
> > Sent: Thursday, August 22, 2013 11:21 AM
> > To: WebAIM Discussion List
> > Subject: Re: [WebAIM] testing and Firefox versus IE
> >
> > Jaws seems to incorrectly interpret any content that sits inside a div
> > (even when it is just a div with a CSS class assigned to it for layout
> > purposes) as "clickable" in Firefox.
> > It does not do this in IE.
> > I am going to create an issue in the FS beta tester track (if one does
> > not exist already).
> > Cheers
> > -B
> > Birkir Gunnarsson
> > Accessibility Subject Matter Expert | Deque Systems
> >
> > On 8/22/13, Bryan Garaventa < = EMAIL ADDRESS REMOVED = > wrote:
> >> This happens when there is a click handler on a container element higher
> > up
> >>
> >> in the DOM tree.
> >>
> >> This often happens within frameworks and libraries that assign
> > placeholder
> >> functions for customization, which is necessary to handle event
> > bubbling.
> >>
> >> ----- Original Message -----
> >> From: "Lucy Greco" < = EMAIL ADDRESS REMOVED = >
> >> To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
> >> Sent: Thursday, August 22, 2013 10:27 AM
> >> Subject: [WebAIM] testing and Firefox versus IE
> >>
> >>
> >>> Hello:
> >>> I was just sent some simple pages to check and found something very
> >>> strange. I started the testing and Firefox and was quite concerned
> >>> because these pages were just simple text with a few links. However
> > jaws
> >>> continually read clickable throughout the page in Firefox and not at
> > all
> >>> in IE. From what I can tell there's nothing going on in the source
> > code
> >>> to do this. Any other testers out there got an idea. I can't share
> >>> these
> >>> pages as they are internal currently or I would. Thanks Lucy
> >>>
> >>> Lucia Greco
> >>> Web Access Analyst
> >>> IST-Campus Technology Services
> >>> University of California, Berkeley
> >>> (510) 289-6008 skype: lucia1-greco
> >>> http://webaccess.berkeley.edu
> >>> Follow me on twitter @accessaces
> >>> > >>> > >>> > >>
> >> > >> > >> > >>
> > > > > > > > > > > > >
> > > >

From: Lucy Greco
Date: Fri, Aug 23 2013 7:04PM
Subject: Re: testing and Firefox versus IE
← Previous message | No next message

Unfortunately I am running j-say and I can't update until late next week
but thanks Lucy

Lucia Greco
Web Access Analyst
IST-Campus Technology Services
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Michael Moore
Sent: Friday, August 23, 2013 9:22 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] testing and Firefox versus IE

Here is an except from an email that Eric Damery sent to the JAWS users
list:

"Mozilla Firefox
*Addressed a customer reported issue where JAWS was saying "clickable" at
the end of each line while reading.
*Improved navigating tree views on Web pages and announcing the expanded
and collapsed state of items."

The update that you need is JAWS 14.0.6004. I have been running it for
about a day and it seems to be working fine. The previous update seemed a
little buggy to me.


On Thu, Aug 22, 2013 at 4:18 PM, Bryan Garaventa <
= EMAIL ADDRESS REMOVED = > wrote:

> Have you tested it using the JAWS build released today? I heard that
> this was just fixed.
>
> ----- Original Message -----
> From: "Lucy Greco" < = EMAIL ADDRESS REMOVED = >
> To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
> Sent: Thursday, August 22, 2013 11:29 AM
> Subject: Re: [WebAIM] testing and Firefox versus IE
>
>
> > These are all leads I will follow each of them and get back to you
> > when
> I
> > find out what it was happening in this case thanks to all of you
> >
> > Lucia Greco
> > Web Access Analyst
> > IST-Campus Technology Services
> > University of California, Berkeley
> > (510) 289-6008 skype: lucia1-greco
> > http://webaccess.berkeley.edu
> > Follow me on twitter @accessaces
> >
> >
> > -----Original Message-----
> > From: = EMAIL ADDRESS REMOVED =
> > [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R.
> > Gunnarsson
> > Sent: Thursday, August 22, 2013 11:21 AM
> > To: WebAIM Discussion List
> > Subject: Re: [WebAIM] testing and Firefox versus IE
> >
> > Jaws seems to incorrectly interpret any content that sits inside a
> > div (even when it is just a div with a CSS class assigned to it for
> > layout
> > purposes) as "clickable" in Firefox.
> > It does not do this in IE.
> > I am going to create an issue in the FS beta tester track (if one
> > does not exist already).
> > Cheers
> > -B
> > Birkir Gunnarsson
> > Accessibility Subject Matter Expert | Deque Systems
> >
> > On 8/22/13, Bryan Garaventa < = EMAIL ADDRESS REMOVED = > wrote:
> >> This happens when there is a click handler on a container element
> >> higher
> > up
> >>
> >> in the DOM tree.
> >>
> >> This often happens within frameworks and libraries that assign
> > placeholder
> >> functions for customization, which is necessary to handle event
> > bubbling.
> >>
> >> ----- Original Message -----
> >> From: "Lucy Greco" < = EMAIL ADDRESS REMOVED = >
> >> To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
> >> Sent: Thursday, August 22, 2013 10:27 AM
> >> Subject: [WebAIM] testing and Firefox versus IE
> >>
> >>
> >>> Hello:
> >>> I was just sent some simple pages to check and found something
> >>> very strange. I started the testing and Firefox and was quite
> >>> concerned because these pages were just simple text with a few
> >>> links. However
> > jaws
> >>> continually read clickable throughout the page in Firefox and not
> >>> at
> > all
> >>> in IE. From what I can tell there's nothing going on in the
> >>> source
> > code
> >>> to do this. Any other testers out there got an idea. I can't
> >>> share these pages as they are internal currently or I would.
> >>> Thanks Lucy
> >>>
> >>> Lucia Greco
> >>> Web Access Analyst
> >>> IST-Campus Technology Services
> >>> University of California, Berkeley
> >>> (510) 289-6008 skype: lucia1-greco http://webaccess.berkeley.edu
> >>> Follow me on twitter @accessaces
> >>> > >>> > >>> list messages to = EMAIL ADDRESS REMOVED =
> >>
> >> > >> > >> list messages to = EMAIL ADDRESS REMOVED =
> >>
> > > > > > list messages to = EMAIL ADDRESS REMOVED =
> > > > > > list messages to = EMAIL ADDRESS REMOVED =
>
> > > list messages to = EMAIL ADDRESS REMOVED =
>
messages to = EMAIL ADDRESS REMOVED =