E-mail List Archives
Thread: perkins
Number of posts in this thread: 7 (In chronological order)
From: Terzian, Sharon
Date: Fri, Oct 09 2015 8:25AM
Subject: perkins
No previous message | Next message →
Hi
curious about your opinions of Perkin's new accessible website
from my html snooping, I was surprised to not see titles as part of their a href tags
http://www.perkins.org/#
Sharon Terzian
Webmistress/Sherlock Center @ RIC
Adjunct Professor/School of Management @ RIC
http://www.sherlockcenter.org
http://www.dubowitzsyndrome.net
From: Steve Faulkner
Date: Fri, Oct 09 2015 8:40AM
Subject: Re: perkins
← Previous message | Next message →
On 9 October 2015 at 15:25, Terzian, Sharon < = EMAIL ADDRESS REMOVED = > wrote:
> from my html snooping, I was surprised to not see titles as part of their
> a href tags
reasons not to use the title attribute
https://www.paciellogroup.com/blog/2013/01/using-the-html-title-attribute-updated/
--
Regards
SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;
From: deborah.kaplan@suberic.net
Date: Fri, Oct 09 2015 8:47AM
Subject: Re: perkins
← Previous message | Next message →
On Fri, 9 Oct 2015, Terzian, Sharon wrote:
> Hi
> curious about your opinions of Perkin's new accessible website
>
> from my html snooping, I was surprised to not see titles as part of their a href tags
I didn't look at the rest of the site, but this is not surprising at all.
The title attribute does not add functionality to anchor tags. The title attribute is widely misunderstood to be an accessibility feature, even though there are very few cases where it adds accessibility (frames, certain situations and forms, certain situations and tables). The titles on anchor tags are not accessible to people using the keyboard, not accessible to people using speech recognition, only accessible to people using screen readers under certain circumstances, and not accessible to people in mobile.
Great breakdown is here: https://www.paciellogroup.com/blog/2013/01/using-the-html-title-attribute-updated/
Deborah Kaplan
From: Terzian, Sharon
Date: Sat, Oct 10 2015 3:17AM
Subject: Re: perkins
← Previous message | Next message →
A year or so ago I asked for suggestions on how to handle a drop down menu, similar to the one at the top of their page. Someone here led me to the YUI script, which is fine but
not very versatile (color, height, etc) unless you really know javascript
essentially it treats it as an unordered list/line items so the links are coded into the basic html, this seems to do the same thing, but did they rewrite or is there a different script out there now that
allows more flexibility in appearance?
http://www.perkins.org/#
thanks
Sharon Terzian
Webmistress/Sherlock Center @ RIC
Adjunct Professor/School of Management @ RIC
http://www.sherlockcenter.org
http://www.dubowitzsyndrome.net
From: John Northup
Date: Sat, Oct 10 2015 7:03AM
Subject: Re: perkins
← Previous message | Next message →
Hi Sharon,
The unordered list is the way to go. Modern visual browsers can handle drop-downs with HTML and CSS (no JavaScript needed). For flexibility in appearance, just tailor the CSS to your requirements.
The unordered list is semantically correct in that the relationship between the menu items can be inferred purely from the HTML--which makes it more adaptable to an aural or mobile context (as compared to a string of table cells or DIVs). If your menu is very deep, be sure that aural users can navigate across the top-level headings without having to listen through the contents of each.
So, the Sherlock Center site is the one you're working on, and the Perkins site is the one you're modeling your menu after, correct?
John Northup
Accessibility/Front End Specialist
Ford Motor Company (contractor)
work: = EMAIL ADDRESS REMOVED =
On Oct 10, 2015, at 05:17 AM, "Terzian, Sharon" < = EMAIL ADDRESS REMOVED = > wrote:
>
> A year or so ago I asked for suggestions on how to handle a drop down menu, similar to the one at the top of their page. Someone here led me to the YUI script, which is fine but
> not very versatile (color, height, etc) unless you really know javascript
>
> essentially it treats it as an unordered list/line items so the links are coded into the basic html, this seems to do the same thing, but did they rewrite or is there a different script out there now that
> allows more flexibility in appearance?
>
>
> http://www.perkins.org/#
>
> thanks
>
>
> Sharon Terzian
> Webmistress/Sherlock Center @ RIC
> Adjunct Professor/School of Management @ RIC
> http://www.sherlockcenter.org
> http://www.dubowitzsyndrome.net
> > > > > > > >
From: Terzian, Sharon
Date: Sat, Oct 10 2015 7:07AM
Subject: Re: perkins
← Previous message | Next message →
yes I have a new redesign (not up) that incorporated the YUI script for the drop down and the carousel script for the photos...
it's living here: (and SO unfinished!)
http://www.ric.edu/sherlockcenter/test/scrolltest/indexcss2.html
the YUI code doesn't mush up well when it gets smaller, our menus have always been a wrangle in progress
thank you! we want to be fully accessible and it's been trying at times to please 55+ people with the balance of what is pretty and what is best practice
Sharon Terzian
Webmistress/Sherlock Center @ RIC
Adjunct Professor/School of Management @ RIC
http://www.sherlockcenter.org
http://www.dubowitzsyndrome.net
From: WebAIM-Forum [ = EMAIL ADDRESS REMOVED = ] On Behalf Of John Northup [ = EMAIL ADDRESS REMOVED = ]
Sent: Saturday, October 10, 2015 9:03 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] perkins
Hi Sharon,
The unordered list is the way to go. Modern visual browsers can handle drop-downs with HTML and CSS (no JavaScript needed). For flexibility in appearance, just tailor the CSS to your requirements.
The unordered list is semantically correct in that the relationship between the menu items can be inferred purely from the HTML--which makes it more adaptable to an aural or mobile context (as compared to a string of table cells or DIVs). If your menu is very deep, be sure that aural users can navigate across the top-level headings without having to listen through the contents of each.
So, the Sherlock Center site is the one you're working on, and the Perkins site is the one you're modeling your menu after, correct?
John Northup
Accessibility/Front End Specialist
Ford Motor Company (contractor)
work: = EMAIL ADDRESS REMOVED =
On Oct 10, 2015, at 05:17 AM, "Terzian, Sharon" < = EMAIL ADDRESS REMOVED = > wrote:
>
> A year or so ago I asked for suggestions on how to handle a drop down menu, similar to the one at the top of their page. Someone here led me to the YUI script, which is fine but
> not very versatile (color, height, etc) unless you really know javascript
>
> essentially it treats it as an unordered list/line items so the links are coded into the basic html, this seems to do the same thing, but did they rewrite or is there a different script out there now that
> allows more flexibility in appearance?
>
>
> http://www.perkins.org/#
>
> thanks
>
>
> Sharon Terzian
> Webmistress/Sherlock Center @ RIC
> Adjunct Professor/School of Management @ RIC
> http://www.sherlockcenter.org
> http://www.dubowitzsyndrome.net
> > > > > > > >
From: John Northup
Date: Sat, Oct 10 2015 8:37AM
Subject: Re: perkins
← Previous message | No next message
Sharon,
Sounds like fun! (Mostly!) If YUI is only there to power the menus and image carousel, my advice would be to drop YUI, in favor of a pure HTML/CSS menu and light jQuery for the carousel.
Looking at the new site-in-progress, I can also see a few other ways to improve accessibility. Let me know if you're looking for more recommendations (in case 55 voices aren't already enough...)
John Northup
Accessibility/Front End Specialist
Ford Motor Company (contractor)
work: = EMAIL ADDRESS REMOVED =
On Oct 10, 2015, at 09:12 AM, "Terzian, Sharon" < = EMAIL ADDRESS REMOVED = > wrote:
> yes I have a new redesign (not up) that incorporated the YUI script for the drop down and the carousel script for the photos...
>
> it's living here: (and SO unfinished!)
> http://www.ric.edu/sherlockcenter/test/scrolltest/indexcss2.html
>
> the YUI code doesn't mush up well when it gets smaller, our menus have always been a wrangle in progress
>
> thank you! we want to be fully accessible and it's been trying at times to please 55+ people with the balance of what is pretty and what is best practice
>
>
> Sharon Terzian
> Webmistress/Sherlock Center @ RIC
> Adjunct Professor/School of Management @ RIC
> http://www.sherlockcenter.org
> http://www.dubowitzsyndrome.net
> > From: WebAIM-Forum [ = EMAIL ADDRESS REMOVED = ] On Behalf Of John Northup [ = EMAIL ADDRESS REMOVED = ]
> Sent: Saturday, October 10, 2015 9:03 AM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] perkins
>
> Hi Sharon,
>
> The unordered list is the way to go. Modern visual browsers can handle drop-downs with HTML and CSS (no JavaScript needed). For flexibility in appearance, just tailor the CSS to your requirements.
>
> The unordered list is semantically correct in that the relationship between the menu items can be inferred purely from the HTML--which makes it more adaptable to an aural or mobile context (as compared to a string of table cells or DIVs). If your menu is very deep, be sure that aural users can navigate across the top-level headings without having to listen through the contents of each.
>
> So, the Sherlock Center site is the one you're working on, and the Perkins site is the one you're modeling your menu after, correct?
>
> John Northup
> Accessibility/Front End Specialist
> Ford Motor Company (contractor)
> work: = EMAIL ADDRESS REMOVED =
>
> On Oct 10, 2015, at 05:17 AM, "Terzian, Sharon" < = EMAIL ADDRESS REMOVED = > wrote:
>
>>
>> A year or so ago I asked for suggestions on how to handle a drop down menu, similar to the one at the top of their page. Someone here led me to the YUI script, which is fine but
>> not very versatile (color, height, etc) unless you really know javascript
>>
>> essentially it treats it as an unordered list/line items so the links are coded into the basic html, this seems to do the same thing, but did they rewrite or is there a different script out there now that
>> allows more flexibility in appearance?
>>
>>
>> http://www.perkins.org/#
>>
>>
>> thanks
>>
>>
>> Sharon Terzian
>> Webmistress/Sherlock Center @ RIC
>> Adjunct Professor/School of Management @ RIC
>> http://www.sherlockcenter.org
>>
>> http://www.dubowitzsyndrome.net
>>
>> >> >>
>> >>
>> >>
>> >> >>
>> >>
>> >>
> > > > > > > >