Does this page look plain and unstyled?

Tools, wizards, articles and tutorials on Web Accessibility for the conscientious web developer

Subscribe to Accessify's RSS Feed   

Best search solution for Accessify?

OK, a little request for ideas here. As mentioned in the previous post from me, I’ve gone and migrated all posts to WordPress. There’s still some work to do (a lot of older posts are mis-titled) but one thing that I’d like to change at this time is the way search works.

For a long time, this site relied on Atomz but the results were frankly rubbish. So I’ve changed it to a scoped Google search for the time being.

Wordpress is database-driven so it would be easy to use that search facility, but it would only be searching against the news posts, not the rest of the site which is not database-driven.

Ideally, I guess what I’m after doesn’t exist - a method for searching database-driven content in Wordpress and also searching the static pages on the server. Am I right in this assumption (in which case I’d be as well to stick with the simple scoped Google search)?

If you have flashes of insight to offer on this topic, please do add a comment below. Thanks!

Comments (9) left to “Best search solution for Accessify?”

  1. Matt Round wrote:

    For a quick’n'easy temporary solution you could use the WordPress search, but add a Google link to the results page (with the query already inserted via PHP) along with explanatory text.

  2. bruce wrote:

    Mind you, I’ve had trouble with the WP search giving 404s on some (seemingly-random) search terms that I know exist ..

  3. Lucy wrote:

    I’d probably have a look at using the straight wordpress search as a simple search, but then have an advanced search option where you can switch between searching all pages, or just posts. Then use word press for the posts search but use Googles Public Service Search option for pages. If you then use Google Site Maps you should find that there’s not the same delay on getting new posts indexed by Google. Hopefully you then get the best of both worlds, although tweaking the interface so it makes sense to users will be the biggest challenge.

    There is one downside though - the way results are displayed in google’s public service search uses the same code as google’s normal results and is really rather rubbish… this, that…

  4. Martin wrote:

    If I were you, I’d put all posts including very old ones in the database in order to be searchable by the WP search.

    Personally, I hate half-measures such as some posts in a database, and some not.

    There are some solutions to your enquiry but they are as elegant as my suggestion that all posts should be database-driven.

    All you gotta do is just make time to migrate all posts to the WP database. It’s all worth it for the search, but up to you :)

  5. SchizoDuckie wrote:

    Have a look at Sphider, it’s in PHP and has the google-look-and-feel.

    The best of all is, it works using a spider in a webinterface, and you can automatically add content to it on-the-fly. There’s also extensive support for not indexing some parts of pages, templates, query stats, spidering logs, etc.

    Runs smoothly on 2 of my sites.

    http://www.cs.ioc.ee/~ando/sphider/

  6. Ian wrote:

    Are you dissatisfied with the Google results?

    Personally, I rarely use site searches, because:
    A) I find the results are often weak or dubious,
    B) site based search engines I feel are relatively slow,
    C) I’m a horrible speller and site searches rarely have decent spellchecking, and
    D) I can more easily expand my searches to the entire web just by removing site: for instance.

    Of course these aren’t true everywhere, but I’ve had enough bad experiences on even well funded and staffed sites, that I rarely even look at site search boxes (one exception being Wikipedia, which I use despite having most of the flaws I’ve listed here–I guess it has to do with placement–often I resort to Google eventually).

    I never understood the desire that publishers (of which I must admit, I am not) had with running and maintaining their own search databases and engines. It seems like a lot of overhead for something that’s really, really hard to do well.

    ~~Ian

  7. Nicole wrote:

    I think the choice to go to Wordpress was a good one, it’s a really strong system and I’m happy that I switched to it. There is a plugin called ‘Search Everything’ ( http://wp-plugins.net/plugin/searcheverything/ ) that you might try, but even that is only going to search all posts, pages (wordpress pages), and comments.

    On the other hand, I see absolutely nothing wrong with using a Google search entirely, so long as you are getting good results.

  8. Ian Lloyd wrote:

    Thanks all. I am actually very happy with the quality of the search results from Google but there are a couple of issues.

    Firstly, I know that Google’s results are not going to be as up-to-date as a search on WordPress database.

    Secondly, while the results work for me, the display of the search results is not perfect - in other words, it looks like a Google search page, it’s not integrated with the rest of the site design.

    Having said that, it does effectively return results whether they are WordPress-powered content (for the news updates) or content stored on the server in static pages (basically everything else).

    Is there any way I can customise the Google search results page any further? (I’m sure I’ve seen a Google search results page feature a site’s icon - but perhaps that’s a premium, paid-for service).

  9. Nicole wrote:

    Google has a page to customize the results page. You can find that here: http://www.google.com/services/free.html

    While that may be sort of what you are looking for, it is somewhat lacking in that the results pages are generated with quite lousy HTML. It might do for the short term though.

    You can generate fully customizable results with the Google API, but for that you’ll need to do a little scripting, and get a Google key for API access ( http://www.google.com/apis/ ).

    There are a couple of examples of embedded search and some example scripts at the following:
    At fiftyfoureleven.com
    At Dankarran.com (I really like the search results of this one, he uses it on his search page for the site.)

    I’m sure there are others floating around, but those two have some full examples given on how to do it.

Post a Comment

(Never published)
 

Site Navigation

Outside reading

Migrating from WCAG 1.0 to WCAG 2.0
Roger Hudson provides a through transition guide from WCAG 1 to WCAG 2
Beyond CAPTCHA: No bots allowed
James Edwards (aka Brothercake) provides a useful run-down of the problems posed by using CAPTCHAs
Jeremy Keith does an excellent write-up of the Accessibility 2.0 conference (which I was unable to attend)
Sharepoint and Web Accessibility
Bruce Lawson describes the disparity between Sharepoint/MOSS developed web sites and the level of accessiblity that the tool offers to users (summary - it really is not good!)
How does a screen reader user really hear your web site?
Interesting post on Beast Blog about how a screen reader user - a real one! Not one of those fake web developer tester types! - uses the tool to read a web page. A few surprises were waiting in store for author Mike Cherim.
Web Accessibility Toolbar now available in simplified Chinese
The Web Accessibility Tools Consortium (WAT-C) release a simplified Chinese version of the Web Accessibility Toolbar.
Web 2.0 vs Web Accessibility
1-day seminar in London, 25th April, brings together experts in the field to discuss/demonstrate the accessibility issues faced by web 2.0.
Leading accessibility technologists form new alliance to fix problems
The Accessibility Interoperability Alliance (AIA), comprising (among others) Adobe, HP, Microsoft, Novell, and from the assistive tech industry Dolphin, GW Micro and HiSoftware forms to work together "to create and harmonize standards for accessible techn
Fieldsets, legends and screen readers
An excellent run-down of how fieldsets and legends can improve accessibility and how the various screen readers cope with this useful markup.
CAPTCHAs explained - WacBlog
Another really good post on the RNIB\'s Web Access Centre blog explaining captchas, why they\'re bad for accessibility and what the alternatives may be.
Making WCAG easier to read
Derek Featherstone has created some fancy style sheets to make reading WCAG documents a little easier on the eye.
Top Tips for the title attribute
Ann McMeekin provides a set of simple tips regarding when - or rather when not to - use the title attribute. \'Cos sometimes you can try *too much* to be helpful
California court tilts towards mandating web accessibility
Outlaw.com reports (on behalf of The Register) on the Target California class action lawsuit, digging a little deeper into what Target have been doing of late to address matters.
Screen Readers and display:none
Juicy Studio, aka Gez Lemon, investigate some quirks whereby screen readers announce content that they should not be. Perhaps this could be used for good rather than evil?
Google Developer Podcast: The status of accessibility on the Web
An interview with Google research scientist TV Rahman (and Hubbell, his seeing-eye dog!). Lots of talk about CAPTCHAs and accessibility, but no sign of a transcript for this interview as yet.

View all Accessify bookmarks on del.icio.us



This page is styled using Cascading Style Sheets (CSS). If you can read this message, the chances are that your browser does not properly support CSS or you have disabled this yourself. The content on this site is perfectly readable without style sheets, though; it just doesn't look quite so fancy.

site statistics

This site is partnered with MIS Web Design and Top4Office for Copiers and Digipro for Photocopiers. Web design by Swindon Internet & PR Services.

How you can help support this site: Learn web design from the creator of this site, or help him by requesting some PR Photography