Ian Matthias

Cars; not faster horses. 

New Use Cases for Microsoft Powerpoint

A few new Use Cases for Microsoft Powerpoint:

  1. Add Animation to Multiple Images without Crashing Powerpoint
  2. Hide / Show all Images for active Powerpoint Slide (i.e. let me see the text without going to Outline View)
  3. Select Image in Animation Bar shows Image in Slide View
  4. Add Image to Slide defaulting Maximum Image Dimensions to less than or equal to Dimensions of Slide

Net productivity increase: ~40%.

Filed under  //   bug   feature   powerpoint   use-case  

Comments [0]

Macy's division of retail space

P161

Making some rash assumptions from the store directory it would imply that 73% of the store is dedicated to Women. Food, Customer Services, Home, Men and Children get to fight over the remainder. Maybe an indication of where e-commerce should also be focussing?

Filed under  //   department-store   e-commerce   macys   retail  

Comments [0]

Good news for those with m-commerce offerings this Christmas

According to http://www.internetretailing.net/2010/11/smartphone-users-will-drive-an-m-commerce-christmas-as-it-saves-them-time-and-money-survey-reveals/ the Mobile Commuter could become an important user, though still he/she is thwarted by the payment process...

Filed under  //   m-commerce   mobile  

Comments [0]

Visa and Bank of America to trial Mobile Payments in New York

Comments [0]

Useful script to add Goto and Loop functionality to Selenium IDE in Firefox

Comments [0]

Reviewing and Annotating Websites (using NotableApp)

Unforgotten_exmoor_notable_usa

A friend sent me the link to this tool: http://www.notableapp.com/, which is a great way for non-technical people to capture their comments and feedback on a website and submit to developers.

Rather than wasting time describing where on the page they are, or struggling with taking screenshots and manipulating them in Powerpoint or similar, a simple Firefox plugin takes the screenshot and the user then uses the webapp to comment on the visuals, code, heading structure and SEO of the page.

Unfortunately it doesn't allow easy import of the issues raised into a bug-tracking system (at least not that I have found so far). However, this might not be desirable as the discussions arising in the collaborative space that NotableApp creates to discuss the webpage might require a different resolution.

I certainly aim to use it on small projects in the meantime and have been testing out its functionality already: https://ianmatthias.notableapp.com/website-feedback/34605/Unforgotten-Exmoor-Homepage.

Filed under  //   annotate   bug-tracking   issue-tracking   review   website  

Comments [2]

Visual cross-browser testing

http://labs.adobe.com/technologies/browserlab/

Useful tool for testing the visuals of your website on different browsers. I'm not entirely certain that IE7 and IE8 are entirely accurate as they do not seem to deal with transparency in the same way as it is being dealt with on a local machine.

Filed under  //   css   html   multiple-browsers   testing  

Comments [0]

Some Findings from Usability Studies

Comments [0]

How to create an Accessible Checkout Progress Bar

http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/#comment-11644

An interesting article on how this could be done. Due to the reasons below I would probably make the following modifications:

1. To satisfy DDA requirements, information that is conveyed by an image (e.g. the progress bar image) also needs to be conveyed by screen-reader accessible text on the page. For step 3 from your example page I would implement it as below; inserting " (selected)" after the step name provided within the <span> tags.

<h3>Step 3</h3>
<ol title="Checkout Progress" id="step3" class="checkout-progress">
    <li>Checkout</li>
    <li>Billing and Shipping</li>
    <li><span>Confirm Your Order (selected)</span></li>
    <li><span>Complete Order</span></li>
</ol>

2. When I last researched the issue, most screen-readers do not come pre-configured to read out the title text of a link. It is entirely possible that this situation has changed, but if this is still the case I would be inclined to further modify the example by placing the "Return to" text inside <li><span>  instead of using title text. I would also be consider using "Back to" and "Forward to", rather than "Return to" as these re-enforce the ordering by indicating the direction through the process that the user would be moving. Further modifying the above example with the steps above and to add a forward link for the final step this would become:

<h3>Step 3</h3>
<ol title="Checkout Progress" id="step3" class="checkout-progress">
    <li>Back to Checkout</li>
    <li>Back to Billing and Shipping</li>
    <li><span>Confirm Your Order (selected)</span></li>
    <li>Forward to Complete Order</li>
</ol>

Filed under  //   accessibility   html   progress-bar  

Comments [0]

Prevent sent-mail email attachments being removed by Horde webmail

Comments [0]