Skip to Content

Usually there are huge documents inorder to solve accessibility issues,but sometimes even though everything in the form is fine, from a developer’s point of view, there are some hidden accessibility issues in the adobe form which only a accessibility expert can find out.

       

So i thought why not i share some simple tips and tricks which i got out of my experience with the adobe forms in a one page liner. You need not be an accessibility expert to solve accessibility issues.Just try out these simple tricks,i am sure, you will be relieved from accessiblity issues on your form.

First of all what is accessibility ?

Accessibility is about making sure that mainstream technologies like printers,web browsers, software applications etc can communicate the proper data to assistive technologies.

An assistive technology is a software application or piece of hardware that acts as a bridge or translator between the person with the disability and the mainstream technology that needs to be accessed. For eg: screen reader which speaks the text content of a computer display.

Then what is the precedence of accessibility options on an Adobe form and when  and where it is supposed to be used :

Five possible precedence’s that can  be set to any field are:

1. Custom text  : When Custom Text is set, an appropriate text has to be given in the Custom Screen Reader Text field

2. Tool Tip     :When Tool Tip is set, an appropriate text has to be given in the Tool Tip field

3. Caption      :When we have to set the priority to Caption,please provide an appropriate caption to the field.

4 .Name         :Please don’t use Name for any field

5. None         :When the field label is not supposed to be pronounced.

What are the common accessibility issues which are usually found in an Adobe form ?

1.Tab order

2.Cryptic word pronounced

3.Logical order in which the statements has to be read 4.Logos etc some fields not pronounced on the form etc.

Tips and tricks to solve :

1.Tab order issue :

Maintain the tab order from menu options :view-> tab order.sometimes even this doesn’t work, then do it manually.

this is painful,but it really works!!!

2.Cryptic word pronounced :

  Maintain accessibility tab-> screen precedence for text field etc. 

   If label is not required to be pronounced,for example currency field,then maintain the word ‘currency’in tool tip .

Any abbreviated word in the field label,maintain the full form of the abbreviated word in the tooltip.

  Logo : Dont forget to maintain the Logo in the tool tip section.This is the usual which everyone commits on the form.

  This happens in the static text as well.Maintain none option in the accessibility tab in screen precedence and check if it is wrapped in any subform .Check whether it is properly wrapped within its length of subform.Unknowingly some letters are left out.

One important note : Do not forget to erase the data in the custom text of the field, if it is not required.

3.Logical Sequence Order :

  Sometimes even when the tab order is maintained, the sequence is not pronounced as it is supposed to be.

a)First check the sequence in which order the elements are added in Hierarchy.

b)If its ok, check the Y- co ordinates of both the fields if both are equal for example field1 and field2  and the sequence should be 1->2 instead it is announced 2->1 then reduce alittle bit the Y-co ordinate of field1, since JAWS reads the form from left to right.

c)And check under accessibility tab, the correct option is maintained, since custom text is given preference over tool tip and so on.

d)Even then it doesnt work, try to wrap those elements in a separate subform.

JAWS is one of the widely used screen readers. Log file can be created to get an idea of what is being announced by Jaws

To create Log file:

    Go to MS-Prompt ->change directory to C:\Program Files\Freedom Scientific\JAWS\.log, Press ENTER.

To find the log file, go to the saved directory and open it with Notepad.

In this way, the developer can check his own adobe form and rectify most of the accessibility issues on an Adobe form.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply