Plone Accessibility
maxine davis <[email protected]> Sun, 27 Feb 2005 23:44:31 -0500
| Newsgroups | gmane.comp.web.zope.plone.design |
|---|---|
| Message-ID | <[email protected]> |
The Bobby report generated by my Plone site gives these two Priority 2
errors, that I respectfully ask your feedback on:
1. Create link phrases that make sense when read out of context.
The html character entity codes in the calendar portlet that render as
double backward/forward arrows fetching the previous («) and
next (») month calendar.
Using more meaningful, literal link phrasing such as "Previous Month"
and "Next Month" would obviously be too large for the space.
What else could be done here?
2. Nest headings properly.
Referring to the font effects of the <h5> portlet headings and portal
tabs, which are not preceded by h4, h3, h2 and h1 tags respectively
and therefore would not represent a logical document structure to a
screen reader.
http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/#tech-logical-headings
What do you recommend for this?
3. For the calendar events, the Bobby report returns an error and recommends
"If you must use device-dependent attributes, provide redundant input
mechanisms (i.e., specify two handlers for the same element, both of
which have the same code associated with them):"
How do I add this to the portlet_calendar without breaking the python
code and causing the w3c validator to return an error -- no such
attribute???
<td class="event" tal:condition="day/event"
tal:attributes="onmouseout python: javascriptstring % ('hide', datestring);
onmouseover python: javascriptstring % ('show', datestring);
class python:test(current.year()==year and current.month()==month and
current.day()==int(daynumber), 'todayevent', 'event')">
Thanks!
Maxine
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click