Ramble On

A survey by WebAIM on how users of screen readers interact with web pages is worth a read. It gives a small insight into how screen reader users navigate around pages and some of the problems they face. The survey failed to clarify the term Web 2.0 so the survey hasn’t helped to understand if AJAX based sites disenfranchise partially sighted users but it does confirm some of the advice accessibility experts make. It also reinforces some of the point I tried to make to the Domino developers at Lotusphere about where the new XPage technology fails to meet basic accessibility criteria, namely that screen reader users use the page’s semantics to navigate around the page. A good practice that XPage authoring using the visual interface fails to support.

When html was originally specified it was intended to be a docuument markup language and the tags selected define the page’s content – headings, paragraphs, lists, etc. As web developers we all know this, it’s really basic stuff.

Since headings are more important than paragraphs, a significant percentage of screen reader users use headings to quickly navigate around sections of the page and this confirms the advice accessibility experts have been giving for years. Define a readable document and then style it to look like an application. XPages gets this fundamentally wrong and provides no visual tools to generate standard page markup, a glaring omission that no other editor that I’m aware off fails to include.

All’s not lost. If you want to develop a semantic page it’s just a case of switching to code view and you can add normal markup and it wouldn’t take much for Lotus to add some simple page editing tools.

Hopefully surveys like this help developers see how some simple changes to their pages can make page browsing easier for a small forgotten number of web users

Accessibility, Domino, Web Design, XPages Accessibility, Domino, Web Design, XPages

From my personal perspective the big feature in 8.5 is XPages, but 8.5 is not a one trick pony. There have been a number of other improvements, such as the ID Vault (something not applicable in our institution) and Domino Attachment and Object Service (DAOS).

DAOS

DAOS is described elsewhere. But basically, DAOS allows you to store the attachments in your Domino databases outside of the database, reducing the size of the nsf. 

Big figures are being thrown around; reducing storage size by 40-60%, removal of duplicate attachments and DAOS invisible to Domino apps

DAOS can be enabled per-database or across the entire server and it’s possible to undo the change at a later stage, which is excellent news. Also since it’s implemented at the API level, it’s invisible to the end user or developer.

Reflecting on our system, DAOS  offers:

• Quicker backups. DAOS are stored as files on the file system so can be incrementally backed up.
• NSF are smaller. Since these are loaded into the server’s cache for web delivery, this means more apps can stay resident in memory and so less disk IO.
• We create 4000 modules (databases) per year and carry across teaching resources from previous years. Often resources are uploaded as attachments, and don’t change year on year, so we should see another significant space saving

Other 8.5 features and benefits

• 8.5 contains 400 bug fixes to the nsf
• 50% reduction in CPU for transaction logging
• ID Vault (easier password change)
• Domino configuration tuner for identifying performance issues with your Domino setup. This will be updated as and when, rather than being tied to a Domino release, another positive step from Lotus. 

Developments post 8.5

There will finally be a new Eclipse based lotuscript editor release with 8.5.1

Further ahead the team are investigating how XPages can consume SOAP, REST, and XML (data sources). New controls for XPages such as menu bar, toolbar, outline and general performance improvements.

They are also working on directory independence such as using user info from ldap or active directory to improve single sign-on

Domino, XPages Domino, Domino 8.5, XPages

This is the biggie for us web developers. This is the first session on the technology at this year’s Lotusphere. It’s definitely popular, and hence very warm.

The session was ran by Maureen Layman and a newbie Maire Kehoe and demonstrtedb(live) many of the new XPage features in Designer 8.5. Maire was clearly nevous but did pretty well.

Most of the stuff was basic stuff. I’ve not looked at themes or localisation yet and I wasn’t aware of the server side inline errors (though configuring them didn’t seem to be obvious), so I got something out of the session.

Unfortunately, as expected, nothing was mentioned about accessibility.

Hopefully by the end of the week, i’ll see some good examples of how developers have used XPages.

Domino, Lotusphere, XPages

I thought I’d document over the next few months my baby steps in learning XPages. Although I won’t be using XPages for any development in the short to medium term, I’m going to start to investigate the accessibility implications of each option before developing anything in anger.

My first step – and it really is a first step almost embarrassing step, was to simply add html to my page so that I can develop pages with a semantic structure. Stop laughing at the back. We all have to start somewhere.

The Designer client offers some simple tools to style on-screen text

Don’t use them. The html this toolbar produces uses inline styles rather than standard html and explains why the discussion template’s html seems to be missing any form of structure.

Using the bold face option adds

<span style="font-weight:bold">Bold text</span>

The italic and underline also generate inline styles. So using these options could bloat your code considerably.

The increase and decrease font size option also generates in-line styles:

<span style="font-size:14pt">14 pt text<span>


As you can see, it also uses ‘points’ as the default unit rather than pixels or ems, a unit I’ve avoided because it renders differently across browsers. So another reason to avoid this edit bar.

As far as I can see, there doesn’t appear to be an option to set headings and paragraphs, or to insert rules and lists. So how do you add them?

One option appears to be to use the ‘computed field’ option and to set the ‘content type’ to html and for the ‘value’ to use the javascript return function to return html. For example

return ("<h4>This is the header</h4>")

This seems to be a too long winded for my liking so the other alternative seems to be to switch to ‘source’ view and to manually add the html directly in the source view. I have to admit, I’m surprised that there isn’t an WYSIWYG tools to help you produce a page with any form of semantic structure.

One word of warning. It appears 8.5 continues Domino’s habit of generating BRs for every carriage return.

Domino, XPages Domino 8.5, XPages