Page 92 - GIGW2
P. 92

CH 07      Development








                               and people with physical disabilities. Therefore it MUST be ensured that if
                               focus can be moved to a component of the page using a keyboard interface,
                               then focus can be moved away from that component using only a keyboard
                               interface, and, if it is not possible  the user is advised of the method for
                               moving focus away. (Ref. WCAG 2.1.2)

                           h.  It MUST be ensured that the purpose of each link can be determined from
                               the  link  text  alone  or  from  the  link  text  along  with  its  programmatically
                               determined link context e.g. by using title attribute as a tooltip to clarify the
                               purpose of link. (Ref. WCAG 2.4.4)

                           i.   When  any  component  receives  focus,  it  MUST  not  initiate  a  change  of
                               context. Developers must use “activate” rather than “focus” as a trigger for
                               change of context. This ensures that functionality is predictable as visitors
                               navigate their way through a webpage. (Examples of changing context when a
                               component receives focus include forms being submitted automatically when
                               a component receives focus or new windows launched when a component
                               receives focus). (Ref. WCAG 3.2.1)

                           j.   Entering  data  or  selecting  a  form  control  must  have  predictable  effects.
                               Changing  the  setting  of  any  user  interface  component  MUST  not
                               automatically cause a change of context unless the user has been advised of
                               the behaviour before using the component. Unexpected changes of context
                               can be disorienting for users with visual disabilities or cognitive limitations.
                               (Ref. WCAG 3.2.2)

                           k.  Metadata adds semantic information to pages and sites and provides contextual
                               information for people navigating the site, especially those with screen readers
                               who rely on things such as page titles, structured page headings and lists.
                               Metadata  may  also  be  used  by  some  search  engines.  Indian  Government
                               websites MUST provide metadata like, keywords, and description at least on
                               Homepage and all important entry pages.

                           l.   Tables help in organising and presenting data on a webpage. However, many
                               designers  in  the  past  have  been  using  tables  to  make  the  layout  of   Web
                               pages. This has resulted in the Web pages not being accessible to people using
                               assistive technologies such as screen readers. For this reason, Use of Tables
                               for page layout should be avoided. For data tables, proper tags and markup
                               MUST be provided to identify row and column headers and associate data
                               cells and header cells.

                           m.  When users navigate sequentially through content, they should encounter
                               information in an order that is consistent with the meaning of the content




     78
   87   88   89   90   91   92   93   94   95   96   97