RE: DHTML Style Guide - proposed behavior for Rich Text Editor

I would just like to comment on the following: 

<<I, therefore, suggest that by default all buttons should receive the focus,
but their state should be clearly communicated (disabled, grayed out etc).
The user needs to know if a particular control is inactive so they can
figure out the reason for this, e.g. the user meant to select the text for
bolding but they have not done so, thus the BOLD button is disabled to show
that this action canno be performed.>>
I would like to support this statement with my experience with applications and using ISO 9241-171 as a software accessibility standard. All elements should recieve focus and their status should be communicated. This is the same with a read only field in a desktop app which should be indicated as 'RO' or some other agreed indicator.
If all items are not in the tab order and do not recieve focus how will the user know the extent of the applications functionality?
Sally Cain
Digital Acccessibility Development Officer


NOTICE: The information contained in this email and any attachments is 
confidential and may be privileged.  If you are not the intended 
recipient you should not use, disclose, distribute or copy any of the 
content of it or of any attachment; you are requested to notify the 
sender immediately of your receipt of the email and then to delete it 
and any attachments from your system.

RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants.  However, it 
cannot accept any responsibility for any  such which are transmitted.
We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email and 
any attachments are those of the author and do not necessarily represent
those of RNIB.

RNIB Registered Charity Number: 226227


This message has been scanned for viruses by BlackSpider MailControl -

Received on Wednesday, 20 February 2008 16:44:20 UTC