accessible contact component

[andreasK]

I have to make some accessibilty alterations to the standard contact us page for a client, and I will develop this work into a project and release back to the community.

I am look for suggestions about ways to go about this. I am think of using hCard microformat (developed from Vcard) for the individual's details http://microformats.org/wiki/hcard

Code: Select all

<div class="vcard">
  <img " src="www.google.com/1212.jpg" alt="photo" class="photo"/>
 <a class="url fn" href="www.google.com">First Last</a>
 <div class="org">somecompany</div>
 <div class="adr">
  <div class="street-address">astreet</div>
  <span class="locality">acity</span>, 
  <span class="region">astate</span>
  <span class="postal-code">azip</span>
 </div>
 <div class="tel">0123456789</div>
</div>

For 2nd view (the table of contacts in a category), should this be a table? or maybe an unordered list, with the format as above?

[tonyskyday]

Did you get anywhere with this?

[bongiben]

was wondering if you have done anything with the actual contact form html code, this should also be accessible code
maybe check my other post at http://forum.joomla.org/index.php/topic ... #msg325421 or my sites subs http://www.benscottarts.co.uk form for a nice layout using css (i am not using the correct label tag as currently philaform doesnt validate when using this code)

[absalom]

I'm reforking Accessible Joomla into something like this (with a much wider implementation of microformat structures as well as some other eye candy I need) and initial testing has proven, by and large, successful.

Contact componentry has already been forked (stable) to hCard implementation with multiple category classes. Content and weblinks and a few other bits and pieces still have a few teething problems I'm working to resolve (possible completion sometime this week).

[bongiben]

sounds interesting is there anywhere on the web I can see?

[duvien]

I'm reforking Accessible Joomla into something like this (with a much wider implementation of microformat structures as well as some other eye candy I need) and initial testing has proven, by and large, successful.

Contact componentry has already been forked (stable) to hCard implementation with multiple category classes. Content and weblinks and a few other bits and pieces still have a few teething problems I'm working to resolve (possible completion sometime this week).

This sounds interesting but why refork? can't this be included in Accessible (a8e) Joomla?

Sorry, i'm not trying start a flame but just wanted to know the reason for doing so? wouldn't it be better to join forces since you are all working towards the same goal.

thanks,

[absalom]

This sounds interesting but why refork? can't this be included in Accessible (a8e) Joomla?

Sorry, i'm not trying start a flame but just wanted to know the reason for doing so? wouldn't it be better to join forces since you are all working towards the same goal.

Why ? Because the direction I'm taking it is in the same direction that I've suggested for the core since day 1 as part of Mambo 3PD Standards and Joomla U&A/DAWGs (irrespective of the microformatting - see comments elsewhere about heretics and the core teams not welcoming "code" or ideas from "outside" the core), and since there remain serious limitations on a8e itself to do what I want to do with it, I'd at least prefer to test the overall schema of functionality and how it interacts with everything through soft-launching..

That way, if it breaks, I can at least fix it since I'll know where I broke it. If I know the model works, even if it remains a refork off a8e, everyone can benefit in the long term. The take home message is pretty much: Don't try this at home, kids, it's a little risky.

[duvien]

Well! you have a very good reason and i guess it seems unfortunate this is the only way to go but i hope your efforts will not go un-noticed by the core developers or the community.

You have my support (and i'm sure from most other users too) and let us know how you get on or if you may need some help

thanks,

[absalom]

You have my support (and i'm sure from most other users too) and let us know how you get on or if you may need some help

I have confirmed testing and deployment structure for hCard and hAtom throughout a few components (however, Adblock does cause a bit of hassle in that it's writing into the h-Architecture with it's own junk). hReview may be turning up in places you least expect.

This codebase is fairly stable, but incomplete as to what I want to do.. More news as it comes to hand.

[bongiben]

any news on the release?

[absalom]

Correct microformat dating has caused some unforseen delays as has scoping other componentry needed to migrate (hReviews, etc..).

Basically feature complete apart from the dating issues. Midway through migrating the entire date functionality from WP into J! as a result, to help improve extensibility and ubitiqitousness of the result.

[absalom]

Here's just the com_contact 1.0.11 release as it doesn't require dating in the same way as content does.

[bongiben]

how would you install?

tried writing over current php files for contact component and it came out with errors

is this only for accessible joomla or is it for Joomla! 1.0.10

[absalom]

Accessible J! .11

[AmyStephen]

Lawrence - thanks for your efforts on this for our community! 

[absalom]

The upgrade path to 1.0.12 was quick and painless for the Microformat fork. Alpha Generation 1 release should be available for download mid Jan, after I deploy it on my site.

Edit: dating is now working stably and I've removed the validation code from a8e to be replaced by WP functionality.

Code: Select all

<div class="hentry">
<h3 class="entry-title">Good business practices	</h3>
<div class="credentials">
	<address class="vcard author"> Written by <a class="url fn" href="http://blah">Lawrence</a></address>			
	<abbr class="published" title="2006-02-09T22:55:51">Thursday, 09 February 2006</abbr>
</div>
	<div class="entry-content">
	Good business practices help promote the viability and reputation of an enterprise.? Today's news that a major US discount retailer, <a href="http://www.target.com/gp/homepage.html/602-7193711-3566229" target="_blank">Target</a>, is <a href="http://www.sfgate.com/cgi-bin/article.cgi?file=/c/a/2006/02/08/MNGO7H4VBP128.DTL&type=printable" target="_blank">being sued</a> for lack of accessibility in regards to its site design and construction, should help educate the business world at large to the legal and ethical implications of bad business practices on the web.<br />
</div>
<a href="http://blah_link" class="readon" title="Good business practices">More on "Good business practices"..</a>

[daestrom]

Does anyone know when there will be a new version of Accessible Joomla! using 1.012 available?

Thanks

[absalom]

Probably. It shouldn't take that long - it took me an hour at max to do the upgrade of my .11 fork (Microformats) of a8e to .12 using Winmerge. Haven't heard from Matthijs or Zoran, though.

[daestrom]

Cheers Absalom,

Look forward to using the new version of Accessible J! soon.  Getting annoyed changing all the patch files back to being accessible.  Is there a list of lines of code that are changed with each upgrade?

[absalom]

1.0.12 changed a bucketload of them.. in order to fix the formatting and spelling mistakes (there are still some hanging around, though).

I still have .11 a8e so I could do a Merge sometime tomorrow and submit it to Mathjis as I'm part of the a8e project (iirc).

[daestrom]

OK, thanks a lot.  In the meantime I'll download and check out the current release of the a8e project.

[daestrom]

I have checked out the a8e project and downloaded the current version.  I looked through the html of some components especially com_contact and com_registration.  It still seems that a lot still needs doing with these components.  No headings, non semantic code, etc.  i would like to know how far the project is going to remove stuff I have already removed from my version of .12? 

I'm not trying to start a flame war but I originally started using Mambo after seeing that xMambo was to be integrated into the core over 2 years ago.  Nothing much seems to changed since then.  Yes, a few labels on forms but I've been waiting a long time for something Drupal, Wordpress, Plone etc have been doing for over a year.  Don't get me wrong I love Joomla! and have used it on over 20 sites but changing files every upgrade is just too time consuming.  I have even looked at other CMSs but nothing offers the flexibility that Joomla! does which makes me plain frustrated.

I hope the core team take what has already been done with a8e and incorporate it into the next version.  If there are any accessibility, usability or web standards experts out there that feel the same way please let them know.

Sorry for the rant.

[Jenny]

As this topic had gone way OFF TOPIC the post has been split to here:

http://forum.joomla.org/index.php/topic ... #msg629244

Please get this thread back on to the topic of an accessible contact component.

Thank you.

[Jenny]

As it seems this thread cannot be kept on topic it will be closed.  Off topic posts were removed.

[absalom]

Due to the thread closure on unknown grounds, I now have to start up a new thread just to post the .12 microformatted (i.e. semantic / accessible) contact component..

Please find it attached.